A message to an agent can be a convenient way to check on work while you are away from your desk. It also brings a different problem: the system must distinguish your instructions from messages sent by customers, coworkers or strangers. Connecting a messaging app is the start of that design, not the end.
Start with one safe use case
Choose a task with a clear outcome, such as asking for the status of a project. Decide who may ask, what data the answer may include and which actions require your confirmation. Test in a private conversation with non-sensitive material before allowing a shared room or an external contact.
Check identity and approval
Do not assume that a displayed name proves who sent a message. Understand what identity evidence your messaging service provides and how your agent application handles uncertain or risky requests. Confirm where approval prompts appear and what happens if you do not answer. A connected channel should not silently turn every person in a room into an administrator.
Check delivery, not just configuration
Send a test message in each direction. Verify the response appears in the intended conversation, inspect failed or uncertain delivery states and check whether retries can duplicate an external action. Room support, attachments and confirmation buttons may differ by service.
How this works in APX
APX’s channels guide describes channels, contacts and rooms separately. It documents owner identity checks, approval options for new contacts and sealed contact conversations, as well as specific exceptions such as optional public web search. The guide says Telegram, WhatsApp and Signal identify the originating account; other channels have an additional super-agent check. Read the detailed policy before relying on it for sensitive work.
The Telegram guide and WhatsApp guide explain their different setup requirements. APX supports explicitly listed Telegram groups; its WhatsApp connection reads one-to-one chats and ignores groups. APX’s overview also describes a durable outbox with sent, maybe sent and failed states. A “maybe sent” result deserves inspection before you send again.
Before inviting anyone else
- Confirm which people and rooms can reach the agent.
- Verify how new contacts are approved and which capabilities they receive.
- Review what the agent may disclose and which actions require approval.
- Test a message, a reply and a failure path in your chosen channel.
Sources
More articles
How to let an AI agent work on a site without sharing your password
A practical guide to browser handoffs, sessions and safer sign-in for AI agents.
Why an AI agent cannot use a connected tool: an MCP checklist
Troubleshoot an MCP connection in stages: scope, approval, sign-in, tool discovery and a safe test.
AI agent permissions: how to decide what needs approval
Use a practical permission checklist to give an AI agent useful work without losing sight of consequential actions.