Skip to content
Guides

Connecting customers to your assistant

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.

The channels

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.

  • WhatsApp Business — your own number, connected through Meta.
  • Instagram — Direct messages to your business or creator account, connected by signing in to Instagram.
  • Messenger — conversations with your Facebook Page, connected by signing in with Facebook.
  • Telegram — your own bot, connected with a token from BotFather.
  • Web chat — a widget on your own website, with no external account at all.

Shared sandbox vs your own credentials

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.

Differences between the shared sandbox channels and channels connected with your own credentials
 Shared sandboxYour own channel
Setup neededA routing tagProvider credentials, verified
Number or bot shown to customersThe platform’sYours
Customer must send a routing command firstYesNo
Answers from your knowledge baseYesYes
Escalates into your queueYesYes
Intended forTrials, demos, internal testingProduction

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.

WhatsApp Business

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.

Complete the connection checks before enabling the channel. Provider verification, webhook readiness and channel health are distinct checks. Follow the status and any remediation shown in Integrations, then test a real inbound and outbound message. A failed verification can disable a connection.

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.

WhatsApp’s 24-hour service window is the platform’s rule, not ours. Outside it, WhatsApp does not permit a free-form message, so any message the assistant would send — including a check-back on a waiting escalation — is re-checked against the window at send time and simply not sent if the window has closed.

Instagram

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.

Messenger

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.

One Instagram account and one Facebook Page per workspace, inside Meta’s 24-hour window. Each counts toward your plan’s messaging-channel allowance, like a WhatsApp number or a Telegram bot. As on WhatsApp, the assistant replies within 24 hours of the customer’s last message, and a later message is re-checked against the window at send time. If Meta withdraws access, for example after a password change or a removed permission, the channel card says so and asks you to reconnect; nothing is sent until you do.

Telegram

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 web chat widget

The same assistant on your own site, from a one-line snippet in Integrations → Web widget. No Meta account, no bot token.

  1. Add your website. Only the exact addresses you list may show the chat, such as 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.
  2. Switch the widget on and copy the snippet. Set an accent colour if you want it to match your site; the text on it turns dark when the colour is light.
  3. Paste the snippet into your page template, before the closing </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.

Routing tag and directory visibility

Two settings decide who can reach you and how.

Routing tagThe short handle that identifies your workspace on the platform's shared channels. It becomes the pre-filled command in every demo link and QR code, and without one the Demo links page has nothing to build from. Your own WhatsApp number, your Instagram account, your Facebook Page, your own Telegram bot and the website widget never use a tag: the channel itself identifies the workspace.
Directory visibilityControls who can discover you on the shared bot and start a conversation there. A private workspace has its demo links suppressed, because a tag alone cannot select it — customers are invited with a join code instead, which is the right setting for an internal pilot. It does not close your own channels: a customer who messages your WhatsApp number, your Instagram account, your Facebook Page, your Telegram bot or your website widget reaches you whatever your visibility says, with no tag and no join code.
Join codesHow chosen customers reach a private workspace on the shared bot, from Settings → Customer access. A code can be for one person or shared by up to 1,000, and can carry a note only your team sees, such as who it is for; a customer who joins with it shows that note in your member list. Each new code comes with a tap-to-join link for every shared WhatsApp number and Telegram bot, and the /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.
Welcome messageThe first thing a new customer sees. It is worth writing properly: it is where you set expectations about what the assistant can and cannot help with.

What arrives on a channel

Customers can send more than text. Handling depends on the channel, workspace preferences and the processing capabilities enabled by the platform.

TextThe ordinary path — answered from your knowledge base and catalog.
A location pinAnswered with your nearest configured branch, store or pickup point, from the locations you maintain in Assistant. If you have configured none, it is acknowledged honestly instead.
A contact cardAcknowledged safely. Nothing in the card is saved, and nobody in it is contacted automatically.
Voice notes, images and documentsTranscription, image understanding, document extraction and PDF OCR have separate controls under Assistant. When processing is unavailable, the configured fallback applies. Outgoing voice is separate from incoming transcription. See media and voice for settings and availability.

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.