WhatsApp, Messenger and Instagram
Connect your Meta app so an agent answers customers in their messaging apps.
On this page
Your agent can answer customers on WhatsApp, Facebook Messenger and Instagram direct messages. Their conversations appear in the same Inbox as the website's, where your team can take over.
You connect each channel with your own Meta app, so your number, Page and account stay yours. A WhatsApp number can instead come through your own 360dialog, Twilio or Gupshup account, with no Meta app at all. Both are available on every plan. Owners and admins connect channels in Settings → Messaging channels.
Connect with one click
Where your workspace is offered it, Connect WhatsApp, Connect Facebook Page and Connect Instagram appear above the form. Pick the agent that answers, select one, and sign in to Meta in the window that opens:
- WhatsApp opens Meta's signup: choose or create your business, then your number. ikazebot registers the number and subscribes to its messages. Afterwards, add a payment method in WhatsApp Manager: Meta bills your business directly for the conversations you start.
- Facebook Page asks which Pages to allow. Back in ikazebot, pick the Page to connect.
- Instagram asks you to sign in to your professional (business or creator) account. No Facebook Page is needed.
Nothing is left to do in Meta: there is no app, token, secret or webhook of your own. Instagram's access lasts 60 days and ikazebot renews it automatically. If you remove ikazebot in your Facebook or Instagram settings, its connections pause; connect again to resume.
One-click connect is being rolled out while Meta reviews ikazebot's app. Until your workspace is offered it, use your own Meta app as below.
Connect WhatsApp through your provider
If your WhatsApp number is already with 360dialog, Twilio or Gupshup, connect it with that account's details instead of a Meta app. Select Connect WhatsApp through 360dialog, Twilio or Gupshup, choose the Provider and the agent it is Answered by, type the WhatsApp number with its country code, then paste:
| Provider | Details | Where to find them |
|---|---|---|
| 360dialog | API key (D360-API-KEY) | 360dialog hub → the number → API key |
| Twilio | Account SID and Auth Token | Twilio Console → account dashboard. The number must be a WhatsApp sender on that account. |
| Gupshup | API key and App name | Gupshup → your profile → API key; the app the number belongs to |
ikazebot checks the details with the provider before keeping them, encrypted. It then tells the provider where to send the number's messages, and lists the step as Done, Yours to do or Failed:
- 360dialog and Twilio: ikazebot sets the webhook itself.
- Gupshup has no way for ikazebot to set it, so that step is always yours: copy the connection's Webhook URL and paste it, whole, as the app's callback URL in Gupshup. The address ends with a key that proves a delivery is Gupshup's, because Gupshup does not sign what it sends.
Every delivery is checked: Twilio's against your Auth Token, 360dialog's and Gupshup's against the connection's own key. Run checks works as for Meta: it checks the details with the provider, where the provider sends (Gupshup cannot say), and what arrived lately. To change the API key or Auth Token, use Change details.
Your provider bills you for messages as usual. Templates for the 24-hour window are sent by name and language on 360dialog, as on Meta. On Twilio paste the template's Content SID (HX…), and on Gupshup its template ID.
Before you start
You need:
- A Meta developer app (developers.facebook.com) with the WhatsApp, Messenger or Instagram product added.
- The app secret: App settings → Basic → App secret, 32 characters.
- At least one agent to answer.
What else you need depends on the channel:
| Channel | Token to paste | Token needs |
|---|---|---|
| A permanent access token for a system user, made for your WhatsApp Business account | whatsapp_business_messaging, whatsapp_business_management | |
| Messenger | A token for someone who manages the Page, or the Page access token | pages_messaging |
| A token for someone who manages the Facebook Page your professional Instagram account is linked to | instagram_manage_messages |
You don't need to copy any IDs: ikazebot finds your numbers, Pages and Instagram accounts from the token.
Connect, step by step
- 1Paste the token and app secret
- 2Find, then pick a number, Page or account
- 3ikazebot checks and sets up with Meta
- 4Do any step left to you in Meta
- In Settings → Messaging channels, choose the Channel and the agent it is Answered by, then paste the token and the App secret.
- Select Find my numbers (or Find my Pages, Find my Instagram accounts). ikazebot asks Meta what the token reaches and lists it. Pick one; its name is filled in, and you can change it. If the token reaches nothing, ikazebot says why. You can always choose Type the … ID instead and paste the ID yourself, as before.
- Select Connect. ikazebot checks the token with Meta and stores it encrypted. For Messenger and Instagram it keeps the Page's own token, not yours. It then sets up what Meta allows it to, and lists each step as Done, Yours to do or Failed:
- App subscribed to the WhatsApp Business account or Page, so Meta tells your app about its messages.
- Webhook: for WhatsApp, Meta is told to send that number's messages to ikazebot. For Messenger, your app's Messenger webhook is set, but only if it has none yet. One app has one Messenger webhook, so ikazebot never replaces one that sends somewhere else. Meta sets Instagram webhooks only in its dashboard, so that step is always yours to do.
- For a step that is Yours to do, select Open your app in Meta. Paste the connection's Callback URL and Verify token into the webhook settings, select Verify and save, and subscribe to the
messagesfield. For WhatsApp apps created with the Connect with customers through WhatsApp use case, that is Use cases → Customize → Configuration. For Messenger and Instagram, it is the product's Webhooks settings. - Send a test message to your number, Page or account. The connection changes from Nothing received from Meta yet to showing the last event, and the agent replies.
After fixing something in Meta, select Set up again on the connection to repeat step 3.
Each connection has its own callback address and verify token. Every message Meta sends is checked against your app secret, so nobody else can post fake messages to it.
When nothing arrives
Select Run checks on the connection. ikazebot asks Meta about each part of the setup, in the order to fix them, and says what to do for anything wrong:
- Access token works, and which Meta app it belongs to. It also checks when the token expires and whether it has the permission to send.
- App secret belongs to that app. With the wrong secret, ikazebot refuses everything Meta sends.
- Phone number ID is a registered WhatsApp number.
- App subscribed to the WhatsApp Business account or Page. Without this, Meta sends nothing even when the webhook is set. If it is missing, Subscribe the app does it for you.
- Webhook points to this connection, is active, and is subscribed to
messages. It also warns if another channel's webhook points here, for example the Messenger one on a WhatsApp connection. - What Meta sent lately: the last 20 deliveries from the past 7 days, including refused ones, so a wrong secret or the wrong number does not look like silence.
Each connection also shows the latest delivery and what became of it. To fix a token or secret, use Change details.
Checks only read from Meta. The one exception is Subscribe the app, which changes a setting in Meta. While testing WhatsApp, the phone you message from must be on the test number's recipient list. If every check passes and still nothing arrives, Meta notes that some webhooks are not sent while an app is in Development mode: switch it to Live.
Manage a connection
- Answered by: switch which agent answers.
- Set up again / Run checks / Change details: see above.
- The switch: pause a connection. Paused: nothing is answered until you turn it back on.
- Disconnect: remove it. Its conversations stay in the Inbox.
How it behaves
- Text only. If a customer sends a photo, voice note or file, they get a short "please type your message" reply, and the media is not kept.
- One reply per burst. Several quick messages in a row get one considered answer, not one each.
- Source citations are removed, and long replies are split to fit each app's limit.
- Replies cost credits as in the widget. Each customer may send 10 messages a minute.
- The widget's guardrails are not applied on these channels yet.
Meta's 24-hour window
Meta lets a business reply freely for 24 hours after the customer's last message. Your team's replies from the Inbox are sent within that window; outside it, they are marked failed. A customer writing again reopens the window. On WhatsApp, Meta only accepts approved template messages after the window closes. The same applies through a provider. The Inbox asks for the template's name and language, or for its Content SID or template ID on Twilio and Gupshup.
Related
- Inbox and human takeoverWatch conversations live, take one over, reply, write internal notes and hand back.
- TroubleshootingWhat to check when the widget does not show, an agent cannot answer, training fails or a channel is silent.
- Plans, credits and billingHow credits are spent, where to see usage, and how to buy a plan or more credits.
Something not working as described here? See Troubleshooting.