Other messaging apps

What it is

Ten messaging apps share one grid on Integrations → Messaging: Telegram, WhatsApp, Messenger, Instagram, Slack, Discord, LINE, Viber, WeChat, and SMS. They share the same gates, the same connected-app cap, the same status badges, and the same drawer layout. What differs is which credentials each one wants and how much work is left after you press Connect.

This page is the map. Each platform has its own guide with the exact field names and the exact provider screens.

Which app to pick

You rarely get to choose — your customers have already chosen. But if you are deciding where to start:

• Your customers messaged you first. Connect the app they used. Messenger and Instagram if they came from your Facebook Page or your Instagram profile; WhatsApp if they used your business number.
• Your team, not your customers. Slack is the natural fit for an internal knowledge assistant.
• A community rather than an inbox. Discord, where members reach the chatbot with a slash command in a channel.
• A specific market. LINE for Japan, Taiwan, and Thailand. Viber for parts of Eastern Europe, the Balkans, and Southeast Asia. WeChat for mainland China.
• No smartphone app in the picture at all. SMS, through your own Twilio account.
• Easiest first test. Telegram and Viber need one token each and nothing afterwards.

If none of them are available to you yet, the website widget and the public link work on every plan — see Channels overview.

The three patterns after you press Connect

Which app you pick decides how much work happens after you save, and there are only three outcomes.

1. Nothing left to do. Telegram and Viber. Agentency registers the delivery address with the provider for you. Save the token and the channel is live.

2. Paste our callback URL into their dashboard. Slack, Discord, LINE, and SMS. These show Connected immediately and will not deliver a single message until you copy the callback URL from the panel into the provider's own settings. A green badge here does not mean messages can reach you. The drawer says so in a panel titled One last step.

3. Finish a verification handshake. WhatsApp, Messenger, Instagram, and WeChat. These sit at Pending verification and show a callback URL plus a verify token. The provider calls that URL back to prove you control the app. Until that call succeeds, messages arriving on the channel are received and thrown away — the customer sees no reply at all. The panel checks by itself for about five minutes; after that, reload the page.

What every card has in common

• The same four gates. A plan with integrations, messaging enabled for this deployment, an Active chatbot, and a free slot under the cap. See Messaging channels availability.
• One shared cap per chatbot. The Connected channels card above the grid shows it as a connected-out-of-maximum figure. Reaching it disables the remaining cards with the note that you must disconnect one to add another. Reconnecting an app you already have replaces its credentials and does not cost a second slot.
• Credentials are write-only. Everything you paste is stored encrypted and never displayed again. To change a value you reconnect; there is no edit form.
• The same status words. Not connected, Pending verification, Connected, Error, Disconnected.
• The same footer. Test connection re-checks your stored credentials with the provider — it never checks whether you pasted the callback URL. Disconnect stops replies immediately.
• The same message behaviour. Long answers are split into platform-sized messages. Incoming text is trimmed after about 2,000 characters. Every answer spends message credits at your chatbot's live model rate (1X = one credit; see Message credits), exactly like the widget.
• A link to the provider's own documentation. The View official setup guide link in each drawer opens the vendor's current setup page in a new tab.

Where to find it

Open Dashboard → Chatbots → your chatbot → Integrations → Messaging (?tab=messaging).

Steps

1. Open Integrations → Messaging and confirm the grid is not showing Coming soon or an upgrade notice.
2. Activate the chatbot if it is still draft or paused.
3. Decide which app to connect, then open its guide from the list above and follow it. The credential fields are different on every platform, so a generic walkthrough will only get you lost.
4. Finish the post-save step your platform needs — nothing, a pasted callback URL, or a verification handshake.
5. Send a real message from that app and confirm the answer.
6. Check that the thread was recorded in Conversations with the right channel name.

What you will see

One grid, one set of statistics above it — Connected channels, Total messages, Total users — and one drawer style for every platform. Cards you cannot use are visibly disabled and labelled, so you can always see the full catalogue even when your plan or deployment does not allow connecting.

Limits and plan notes

Every app here is plan-gated and availability-dependent, and individual platforms can be unavailable while the rest work. Facebook is labelled Messenger throughout the product. Do not connect an app you cannot administer at the provider: every one of these needs you to create credentials, and four of them need you to change settings in the provider's dashboard after connecting.

Each platform accepts one delivery address at a time, so connecting a bot, Page, or number that is already wired to another tool takes over from it.

Common problems

The card says Connected and nothing arrives.

You are on a platform from pattern 2 and the callback URL has not been pasted, or it does not match what the drawer shows now. Copy it again from the drawer.

The badge will not leave Pending verification.

Pattern 3, and the provider has not completed its call — usually a stale verify token. A fresh one is generated each time you connect, so copy both values again.

Test connection is healthy but customers get nothing.

Test connection only checks your credentials. Delivery depends on the callback URL or the handshake, and on the chatbot being Active.

Messenger and Instagram ask for the same secrets.

They are separate cards and separate connections, even inside one Meta app. Use the token for the asset you actually mean, and expect both to count against the cap.

I have run out of slots.

Disconnect an app you are not using, or spread channels across more than one chatbot.