One assistant on every channel: what that actually takes

"Be everywhere your customers are" is good advice sold badly. The channel logos on a vendor's pricing page are the easy half. The half that decides whether this works is invisible: whether all those windows are the same assistant — one set of knowledge, one set of rules, one inbox where a person takes over — or five separate products wearing your logo.

The channel is the cheap part

Every messaging platform is a gate before it is a channel, and the gates are there on purpose.

• WhatsApp needs a WhatsApp Business Account, a registered "from" phone number, and approved message templates for anything you send outside the 24-hour customer service window (WhatsApp Cloud API docs).
• Telegram bots are registered through BotFather for a token, and the platform is blunt about the rest: "Bots can't start conversations with users. A user must either add them to a group or send them a message first" (Telegram).

Read those two lines together and the marketing promise deflates usefully. These are reply channels. They are excellent once a customer writes to you, and they are not a way to reach people who have not.

What has to be shared, or it is not one assistant

Every one of those is a content or policy problem, not a channel problem — which is why adding a channel to a well-built assistant is small, and adding one to a badly built assistant multiplies the mess.

What we serve today, plainly

We would rather be useful than impressive, so here is the honest list. Busymate AI answers on your website — the chat on your pages, or an embed anywhere you can paste a script — and inside your own iOS or Android app, where a small bridge passes your signed-in customer through so the assistant can answer about their account rather than in general terms (in-app support guide). Voice works in all of them: the customer taps a microphone instead of typing, as described on voice support.

Messaging apps as customer inboxes are not switched on. Telegram appears in the product only as a way to alert your teammate that a hand-off is waiting, which is a staff notification, not a customer channel — the difference is spelled out in the hand-off documentation. When that changes, the changelog will say so; a channel that is not live does not belong on a features list.

What we do have is the layer underneath, which is the part that ports: one knowledge base, one escalation policy, and one Inbox where a teammate replies in the same thread (hand-off and inbox).

The channel-readiness check

Before adding any channel, answer these. If you cannot, the channel will not fix it.

Channel readiness — [Business name]

Answers come from:   [website pages], [price list], [FAQ]      one source, not per-channel
Rules are written:   [refusals], [escalation triggers], [tone]  one policy, not per-channel
A person answers in: [the Inbox]                                one place, not per-channel
Hours we promise:    [Mon-Fri 9-18]                             the same on every channel
Identity works:      [signed-in customers recognised? yes/no]
First channel:       [where my customers already message me]
Next channel only when: the above is true and customers ask for it. [CHECK]

Ask your assistant to do the thinking

Ask your AI assistant:
Read my website at https://[your-site]. List the questions customers most likely
ask, mark which ones need my account systems and which are answerable from public
pages, and tell me which single channel would answer most of them today. Then draft
the one escalation policy that should apply on every channel. Mark guesses [CHECK].

Your mate shows the policy before saving it, and the same policy is what any future channel inherits.

Start where the customers already are

For most businesses that is the site itself — the visitor is already reading you, and a page can do more than answer: the actions your site already offers can be exposed as tools an assistant runs with the visitor confirming, through WebMCP and the page tools guide. Machine-readable context helps assistants that arrive from elsewhere find the right pages, which is why we publish our own /llms.txt.

Build the shared layer once and channels stop being decisions and start being switches. Build an assistant from your URL to see what one channel done properly looks like; pricing is metered per business, not per channel, so you are never paying for logos you have not switched on.