---
title: "One bot, every channel, what multi-channel support actually requires"
description: "Running the same assistant on the web, WhatsApp, Telegram, LINE, Messenger, Instagram, Discord and voice is a setup problem, not eight separate projects. Here is what each channel actually demands."
date: "2026-08-14"
tags: "multi-channel, whatsapp, telegram, architecture"
canonical: "https://www.proxyai.app/blog/multi-channel-ai-chatbot-one-bot-every-channel"
---

> For the complete documentation index, see [llms.txt](https://www.proxyai.app/llms.txt). Request public content pages with `Accept: text/markdown`.

# One bot, every channel, what multi-channel support actually requires

Running the same assistant on the web, WhatsApp, Telegram, LINE, Messenger, Instagram, Discord and voice is a setup problem, not eight separate projects. Here is what each channel actually demands.

14 August 2026·7 min read

**In short:** Running one AI assistant across web chat, [WhatsApp](/services/channels/whatsapp), [Telegram](/services/channels/telegram), [LINE](/services/channels/line), [Messenger](/services/channels/messenger), [Instagram](/services/channels/instagram), [Discord](/services/channels/discord) and [voice calls](/services/channels/voice) is a setup problem, not eight separate projects. The assistant’s instructions, knowledge, handover to a person and billing should be shared; only the connection to each app differs. The hard channel is WhatsApp, which has two incompatible connection routes. The easy ones are Telegram and web chat, each roughly a five-minute setup.

Most teams arrive at multi-channel support the same way. The website gets a chat widget. Then customers start messaging the WhatsApp number on the invoice. Then someone in Bangkok asks why there is no LINE account. Each one gets solved separately, and within a year support is spread across four tools that do not know about each other, with four sets of canned replies drifting out of sync.

The alternative is one assistant configured once, connected to each channel. That is worth doing, but it is worth being honest about what it costs, because the channels are genuinely not equivalent, and anyone who tells you they are has not connected all of them.

## What is actually the same across channels

The parts worth centralising are the parts that have nothing to do with which app the customer uses.

**The bot’s identity and instructions.** Name, tone, what it is allowed to say, what it should refuse. Written once. A tone rewrite that has to be applied in four places will be applied in two.

**The knowledge it answers from.** If your return policy changes, it changes for every channel at the same moment or you have a support problem you cannot see.

**Handover to a person.** Handing a conversation to a person is one queue, not one queue per channel. An agent should not need to know which app a customer used before they can help.

**Spend.** One balance, one usage log. Per-channel billing makes the obvious question, what does this actually cost us, into a reconciliation exercise.

## What is genuinely different

Here is where the work is, and it varies more than the marketing pages of most vendors suggest.

### Web

The easiest, and the only one where you control both ends. Add the chat to your own pages, choose which sites may show it, and add a starter question or two. Nothing to verify, nobody to apply to.

### WhatsApp

The hardest, and the one where the shape of the decision is usually hidden from you. There are two routes and they are not the same product.

The **bridge** route links a number you already use by scanning a QR code, exactly as WhatsApp Web does. It works today, in any country, with no Meta account. It is also unofficial, so WhatsApp can unlink the device at any time, and the phone that owns the number only needs to be opened at least once every 14 days. For a small operation getting started, that is often a fair trade.

The **official Business API** route runs through Meta. Your WhatsApp Business account stays in your own Meta business, and Meta bills the message fees to the card on that account. Slower to set up, and the one to pick when WhatsApp is a channel the business cannot afford to lose.

### Telegram

Genuinely simple. You create the bot inside Telegram, paste one code into ProxyAI, and you are done. Rich formatting and tap-to-reply buttons come free.

### LINE

Two codes copied from a LINE Official Account. Straightforward once you have the account, but the account itself matters commercially if you sell into Japan, Thailand or Taiwan, where LINE is often the primary channel rather than a secondary one.

### Messenger and Instagram

Both run through a Facebook Page and both follow Meta’s messaging rules, most importantly the 24-hour rule: more than 24 hours after a customer’s last message, what you may send them is restricted, whatever your bot would like to say. Instagram can be connected by signing in with Instagram directly, or the longer way through a linked Facebook Page.

### Discord

A different audience shape. Discord support is usually a community, not a queue, and a bot answering in a public channel is answering in front of an audience. That changes what it should be willing to say.

### Voice

Customers can talk to the same bot instead of typing, in two ways. A call button on your web chat starts a call right in the browser, with no phone involved. Optionally, a real phone number rings straight into the bot: you can get a US number from ProxyAI or bring one you already own from Twilio, Vonage, Telnyx or any SIP provider. If your customers already know your number, forward it to the ProxyAI one and they keep dialling what they always have.

It is the same bot on a call as in chat, with your instructions, your documents and your prices, and the transcript lands in the same conversation history. Calls are billed per minute of talk time from your credits, with no separate subscription. One limit to know about: a number from ProxyAI only receives calls, so transferring a live call to a person, or a bot that places calls, needs a number you import.

## The part that decides whether this works

Every channel above is another way into the same conversation. The thing that determines whether one assistant across eight channels is better than eight assistants is whether handover to a person is shared.

A customer who [asks for a human](/services/human-handoff) on Instagram and a customer who asks on WhatsApp should land in the same place, in front of the same agent, with the conversation history attached. If they do not, you have not consolidated anything, you have added an eighth place to check.

The same goes for what the bot knows. A grounded assistant with one document set answers consistently across channels automatically. Eight bots with eight document sets answer consistently right up until someone updates seven of them.

## Where to start

Start with the channel your customers already use, not the one that is easiest to connect. The web widget is the fastest to stand up and the least likely to be where your customers are.

Then add the second channel only once the first one is answering well. Every channel multiplies the cost of a bad instruction set: a bot that is 80% right is a nuisance on one channel and a liability on five.

If you want the mechanics of any single connection, each one has its own guide in the [Help Center](/help/integrations/web-connection), and the [integrations pages](/services) summarise what connecting each involves before you start.

## FAQ

### Which messaging channels can one AI chatbot cover?

A single assistant can answer on web chat, [WhatsApp](/services/channels/whatsapp), [Telegram](/services/channels/telegram), [LINE](/services/channels/line), Facebook [Messenger](/services/channels/messenger), [Instagram](/services/channels/instagram) DMs, [Discord](/services/channels/discord) and [voice calls](/services/channels/voice). Each channel is another way into the same conversation, so the bot’s instructions, documents and handover to a person are set up once rather than per channel.

### Should I run one chatbot across all channels or one per channel?

One assistant across all channels, provided handover to a person and knowledge are genuinely shared. Separate bots per channel means updating instructions and documents in several places, and they answer consistently only until someone updates all but one.

### What is the 24-hour rule on Instagram and Messenger?

Meta restricts what a business may send a customer more than 24 hours after that customer’s last message. It applies to Instagram DMs and Facebook Messenger regardless of which chatbot platform you use, and it limits outbound messages rather than replies within the window.

### Which channel should I connect first?

The channel your customers already use, not the one that is quickest to connect. Add a second channel only once the first is answering well, every additional channel multiplies the cost of a weak instruction set.

### Can the chatbot answer phone calls?

Yes. The same bot can take voice calls in two ways: a call button on your web chat, which runs in the browser with no phone involved, and an optional real phone number that rings into the bot. You can get a US number from ProxyAI or import one you own from Twilio, Vonage, Telnyx or a SIP provider. Calls use the same instructions and documents as chat, and are billed per minute of talk time from your credits.
