Tephlo supports WhatsApp Business, Instagram, Messenger, Telegram and an embeddable web widget. All of them answer from the same knowledge base and land in the same escalation queue.
A channel is how a customer reaches you. Every workspace can run more than one, and the channels use the same workspace configuration and conversation tools. Credentials, media support, delivery restrictions and shared-channel policy can differ by channel.
Where the deployment publishes shared sandbox channels, eligible workspaces can use them without connecting their own credentials. Customers send a short routing command — your routing tag — and the shared bot routes the conversation to your workspace. That is what the console’s Demo links page builds its links and QR codes from.
| Shared sandbox | Your own channel | |
|---|---|---|
| Setup needed | A routing tag | Provider credentials, verified |
| Number or bot shown to customers | The platform’s | Yours |
| Customer must send a routing command first | Yes | No |
| Answers from your knowledge base | Yes | Yes |
| Escalates into your queue | Yes | Yes |
| Intended for | Trials, demos, internal testing | Production |
Everything you configure — knowledge, goals, never-say phrases, escalation recipients — applies to both. Moving from the sandbox to your own number changes who the message comes from, not how the assistant behaves.
Instagram and Messenger have no shared sandbox: they always connect your own account or Page.
Connect your number in Integrations → Messaging channels. When available, use the Meta connection flow and follow its completion status. The supported manual path uses credentials for your WhatsApp Business Account: the phone number ID, the WhatsApp Business Account ID and an access token. The console masks saved secrets.
Each channel row shows its current health, lets you re-run the provider check on demand, and keeps an audit history of every credential and configuration change — who changed what, when, and the reason they gave for disconnecting.
Customers send a Direct message to your Instagram account and the assistant replies in the same thread. Connect it in Integrations → Messaging channels, under Your channels: choose Connect Instagram, sign in to Instagram and allow messaging access. The account must be a professional account, business or creator; a personal account is refused with a message saying how to switch it.
Offered choices arrive as quick-reply buttons under the message, and the customer sees a typing indicator while a reply is written. A conversation that starts from a shared post or reel, or from a reply to your story, shows which one. Comments on your posts are not answered: only Direct messages reach the assistant. Sending pictures on Instagram depends on Meta’s media support for this kind of connection; where it is not available, the customer gets the reply in text.
Customers message your Facebook Page in Messenger and the assistant replies in the same conversation. Choose Connect Messenger in the same place, sign in with Facebook and allow access. If you manage several Pages, you pick the one this workspace answers for; your Facebook account needs permission to manage that Page’s messages.
Offered choices arrive as quick-reply buttons, the typing indicator shows while a reply is written, and pictures, video and voice replies can be sent where your workspace has them on. A conversation that starts from an m.me link, an ad or your Page’s message button records the link or ad it came from.
Create a bot with BotFather, then paste the token into the same channel wizard. Tephlo derives the bot identity from the token itself and starts receiving updates, so there is nothing else to type. Verification and auto-disable work exactly as they do for WhatsApp.
Telegram has no 24-hour window, so a workspace on Telegram can be followed up in cases where a WhatsApp conversation cannot.
The same assistant on your own site, from a one-line snippet in Integrations → Web widget. No Meta account, no bot token.
https://your-site.com. https://your-site.com and https://www.your-site.com are different addresses: add both if your site answers on both. The widget cannot be switched on without at least one, and its last one cannot be removed while it is on.</body> tag. If your site sends its own Content-Security-Policy, allow the chat in it with script-src and frame-src for the API address the snippet names.The list of websites is what a visitor’s browser enforces: the chat will not appear on any other site. It is not a password, so the widget also limits how many new conversations one network, and your whole workspace, can start in an hour, and keeps its own share of your message queue so a flood on your website cannot hold back your WhatsApp customers.
Switching the widget off, removing a website or regenerating the key ends the chats open on your site at their next message. If the embed key is ever exposed, regenerate it from the same screen and paste the updated snippet: the old key stops working immediately, so plan the swap.
On your site the chat stays hidden until it is ready, fills the screen on a phone, shows that a reply is on its way, opens links in replies in a new tab, and follows the visitor from page to page. A reply that arrives while the chat is closed shows as a count on the button. The chat speaks English or French, by the visitor’s browser, and works with a keyboard and a screen reader. Visitors each keep their own conversation, and it appears in Conversations beside your other channels.
A visitor can end the chat, which clears it from their device; the conversation stays with you. Ending it shows their chat ID, which is what you search for in the Privacy Center if they ask for their data or for it to be deleted. Smart Updates are not offered on the web chat: a website cannot write to someone who has left it.
Two settings decide who can reach you and how.
/join message to send instead. Each channel is joined separately. Before you switch to private, the page tells you how many customers chatting with you on the shared bot have no code: they are asked to choose an organization at their next message. Revoking a member cuts them off at their next message too.Customers can send more than text. Handling depends on the channel, workspace preferences and the processing capabilities enabled by the platform.
Rapid consecutive messages from one customer can be aggregated into a single turn, so somebody typing three short lines gets one considered answer rather than three overlapping ones.