# Channels: where an agent can answer

> Web page, WhatsApp, Telegram, SMS, embed, and the open agent-web — what each surface does today.

HTML version: https://agentbag.ai/docs/channels — updated 2026-10-05.

An agent is reachable wherever its audience already is. Each channel is a different front door into the same grounded answers — the leaf set and the fences are the same everywhere.

- Web — the `/@<owner>/<agent>` page: anonymous guests ask free; signed-in viewers see what the owner granted them.
- Embed — `embed.js` drops the agent into any site you own, with a launcher and optional voice.
- WhatsApp — a per-agent business number; visitors message it like a contact. Opt-out (`STOP`/`STOP ALL`) is honored per agent and per number.
- Telegram — a `t.me` link per agent; the signup hook provisions on first message.
- SMS — a dedicated E.164 number per agent where provisioned.
- Agent-web / MCP — other agents call yours over signed, scoped envelopes: [connect from an agent](/docs/connect-from-an-agent).

> Channel document ingest — forwarding a file into an agent’s knowledge — works on WhatsApp on an owner’s own provisioned number today. Telegram ingest is structurally inert (not a toggle), and the feature rides a capability that is off by default. Answers on channels are unaffected.