Which Channel for an AI Customer Service Bot? A Field Guide
The channel decides more about your agent's behaviour than the model does. Where your customers already are, what each channel is mechanically bad at, and why you should launch one, not four. A two-location yoga studio rolled its AI agent out on three channels in a single week: Instagram DM, web ch
Posted on Oct 16 • Originally published at agentfast-guide.app.workbuddy.host
The channel decides more about your agent's behaviour than the model does. Where your customers already are, what each channel is mechanically bad at, and why you should launch one, not four.
A two-location yoga studio rolled its AI agent out on three channels in a single week: Instagram DM, web chat, and SMS. On Instagram it answered around 300 messages in the first week but could not reliably send a working booking link. On web chat, most conversations went quiet after the first reply and nothing was booked. On SMS it performed beautifully — on about forty messages a week, because almost nobody texts the studio.
Same agent, same facts file, same model. Three different outcomes. That is not a coincidence, and it is the reason I tell every client to choose the channel before the platform. The channel determines message length, latency expectations, what media you can send, whether a conversation even has an identity attached, and what "normal" looks like to the customer. The model determines none of those.
A model behaves the same everywhere. Customers don't. Each channel carries its own unwritten contract:
An agent that writes email-length paragraphs into SMS, or one-line fragments into email, is behaving correctly by its own lights and badly by the channel's. That mismatch — not model quality — is what most "the bot is bad" complaints actually are.
The honest list. Every channel on this table works for something; what matters is whether its weakness matches your tolerance.
WhatsApp. Rich media works well and customers send photos freely, which makes it excellent for things like "send me a picture of the damage." The trap is mechanical: outside the 24-hour customer-service window, a business can only send approved template messages, not free-form replies. Agents and flows built assuming open-ended outreach break the moment a conversation goes quiet for a day. The window shapes your whole escalation design, not just your marketing.
Web chat. The one channel where the visitor is already on your site with intent — and the one where silent abandonment is worst. A customer gets the first answer, closes the tab, and the session is dead. There is usually no identity attached, so you cannot follow up even when the conversation was five seconds from a booking. Treating "the agent replied" as success is the classic web-chat error; the customer leaving mid-conversation is the failure that never shows up in a containment dashboard.
Instagram and Facebook DMs. This is where discovery happens, and the threading is chaos: comments plus DMs, multiple parallel conversations, people writing in fragments with typos and voice notes. The inbox mixes sales enquiries, spam and support, and the agent answers all of it in the same voice. Sessions have no clean beginning or end, which makes measuring anything honest very hard.
Email. Structured, permanent, good for detail-heavy queries and record-keeping. But it is a slow channel by mutual agreement. Real-time agent pricing bolted onto a channel where the customer expects a reply tomorrow is paying a premium for speed nobody wanted. Where email does shine is as the destination for summaries and confirmations from faster channels.
[!NOTE] The WhatsApp 24-hour window is the detail most teams discover in production. If the customer stops replying for a day, the agent can only re-open the conversation with a pre-approved template message. Design your follow-ups around which templates you can get approved, not what you wish you could send.
Multi-channel is where agents go to become unmaintainable. Each added channel multiplies your failure modes: different session handling, different length rules, different tone expectations, separate transcripts, separate testing. One channel done properly beats four done approximately, every time.
The channel is not a delivery detail. It is half of your agent's behaviour, and the half your platform vendor will happily let you discover in production. Choose it first, launch one, and let the transcript log — not enthusiasm — tell you when to add the next.
This guide lives at AgentFast, where you'll also find a free audit tool that checks your own agent's instructions against these failure modes. Posted here with a canonical URL pointing at the original.