Channel capabilities
This content is not available in your language yet.
This page lists what each channel does today, not what is planned. It was checked against the platform code and documentation on 2026-10-28. A cell says Yes, Partial (with what), No, Not built, or Not confirmed (we have not verified it, so do not rely on it). Where a feature exists only on a test environment, the table says so.
Channels at a glance
Section titled “Channels at a glance”| Channel | Route | State | Who sets it up |
|---|---|---|---|
| Telegram (1:1) | Built-in connector, Telegram Bot API | In production | Workspace users with builder access |
| Telegram groups | Group mode on a Telegram connector | Test environment and pilots; the code is deployed with group mode off | Workspace owner only |
| Web widget | The <vai-avatar> component and the SDK | In production | Whoever embeds it, with a workspace key |
| Phone (inbound and outbound calls) | Voice agent over SIP and LiveKit | Demo: calls in and out work end to end on test numbers; not yet a production service | Wetel staff |
| Omnichannel partner (ConvAI) and WhatsApp through it | The SDK calls (sdkStart, sdkSendMessage) from the partner | In production for partners | The partner |
| Transactional notices only | In production | Wetel | |
| In-app staff chat | Free Chat in the staff app | Test environment | Workspace owner turns it on |
WHATSAPP, SLACK and LARK connector types exist in the API but are not implemented: operating on one returns an error. WhatsApp reaches Wetel today only through a partner platform that runs the WhatsApp side itself.
What each channel supports
Section titled “What each channel supports”| Capability | Telegram 1:1 | Telegram groups | Web widget | Phone | Partner (ConvAI / WhatsApp) | In-app chat | |
|---|---|---|---|---|---|---|---|
| Text, one to one | Yes | Not built (groups only) | Yes | n/a (a spoken conversation) | Yes | No (notices out only) | Yes |
| Group chat | Not built | Yes (Telegram only) | No | No | Partial (Group Brain API: the platform posts, Wetel only decides) | No | No |
| Several AI employees in one group | n/a | Partial: one bot is one agent; bots in a group are not coordinated | No | No | Not built | No | No |
| Voice notes in (speech to text) | Yes (up to 4 MB and 300 s) | Not confirmed | Yes | Yes: each spoken turn is transcribed (demo) | Yes | No | No |
| Voice out | Yes, opt-in per connector | Not confirmed | Yes (speech, lip-synced avatar) | Yes: the agent speaks the reply (demo) | No (the partner plays audio) | No | No |
| Images in | Partial: forwarded to the workflow; the model sees them only if the workflow reads them | Not confirmed | Not confirmed | No | Yes | No | No (text only) |
| Files in and out | Partial: in = PDF or image only, out = Not built | Not confirmed | Not confirmed | No | Partial: attachments in through the partner | No | No |
| Approvals decided from the channel | No (in the app, owner only) | No | No | No | No | Partial: the notice is emailed; the decision is made in the app | Yes (in the app, owner only) |
| Hand-off to a human | Not built | Not built | Not built | Not built | Not confirmed (the partner’s inbox may offer it) | No | Not built |
| Limits | Partial: workspace spend cap and per-run step limits; no per-chat cap | Partial: cooldown, daily reply cap, judge and send budgets, kill switch | Partial: as Telegram 1:1 | Yes: per-call budget and cost shield | Partial: as Telegram 1:1, plus a per-key rate limit | n/a | Partial: per-user monthly cap and workspace cap |
Things worth knowing
Section titled “Things worth knowing”- Approvals live in the app. An AI employee can ask for approval from any channel, but the owner decides in the staff app. Notifications go to the app and by email only.
- No per-conversation cost cap exists. Limits today are the workspace’s monthly spend cap, the step limits of a workflow run, and the extra group and call limits in the table.
- Hand-off to a human is not a built feature. Do not promise it on any channel.
- Group chat is a pilot capability. It is live on a test environment; on production the code is present with group mode switched off.
- Phone is a demo. A caller can ring a test number and talk to a Wetel agent, and Wetel can place an outbound call to a test number; speech to text, the agent and text to speech run on every turn, with a per-call budget. There is no production phone service yet (no customer numbers, no call recording, no carrier agreement), and WhatsApp calls are not built. Do not plan a launch on it until it is announced.
- WhatsApp rules apply to the AI you put on it. WhatsApp’s platform terms restrict general-purpose AI assistants as a primary function, so AI employees on WhatsApp should be business-specific (support, orders, bookings), and unofficial WhatsApp tools carry a real risk of the number being banned. See your WhatsApp provider’s current terms.
For the connector API, see Channels; for group decisions, Group Brain.