Connecting WhatsApp to Chat

Connect your WhatsApp Business number and messages sent to it arrive in your chat inbox. The AI agent answers them first, just as it does on your website, and your team can step in and reply from the inbox. Customers see everything in WhatsApp.

HelpGuides uses your own Meta app and Meta's WhatsApp Cloud API. Meta bills your WhatsApp Business account directly for any messages that cost money. Replies within 24 hours of a customer's message are currently free.

Before you start

1. Create a Meta app with WhatsApp

  1. In Meta for Developers, click Create app and choose the Business type, or the Connect with customers through WhatsApp use case.
  2. Pick your business portfolio when asked. Meta creates a WhatsApp Business account and a free test phone number for you.
  3. Open Use cases, then Customize on the WhatsApp use case.

To try it with the test number first, open Step 1. Try it out and add your own mobile number as a Recipient. Meta sends a code to your WhatsApp to confirm it. The test number can only exchange messages with numbers on this list. To use your real business number, add it under Step 2. Production setup, then Register your WhatsApp phone number.

2. Collect the four details

DetailWhere to find it
Phone number IDNext to the phone number in the WhatsApp use case. It's a long number, not the phone number itself.
WhatsApp Business account IDNext to the phone number ID, sometimes labelled Messaging account ID.
Access tokenFor a quick test, click Generate token. It expires within a day. For everyday use, create a permanent token (see below).
App secretApp settings, then Basic. Click Show next to App secret and copy the 32 letters and numbers.

Creating a permanent access token

  1. In Meta Business settings, open Users, then System users, and add a system user.
  2. Click Assign assets and give it your app and your WhatsApp account, with full control.
  3. Click Generate token, choose your app, set the token to never expire, and tick whatsapp_business_messaging and whatsapp_business_management.
  4. Copy the token straight away. Meta won't show it again.

3. Connect it in HelpGuides

  1. Open your project, then Inbox, then Messenger settings, and choose the WhatsApp tab.
  2. Paste the phone number ID, the WhatsApp Business account ID, the access token and the app secret.
  3. Click Connect.

HelpGuides checks the details with Meta before saving them. With the business account ID, it also subscribes your app to the account's messages for you. The token and app secret are encrypted and never shown again; the tab shows only the token's last four characters.

4. Point Meta's webhook at HelpGuides

Once connected, the WhatsApp tab shows a Callback URL and a Verify token, each with a Copy button.

  1. In the Meta app, open the WhatsApp use case, then Step 2. Production setup, then Configure Webhooks. In some versions of the dashboard this is under Configuration.
  2. Paste the Callback URL and the Verify token, then click Verify and save.
  3. Under Webhook fields, find messages and click Subscribe. Without this, Meta verifies the address but never sends messages.
  4. Publish your app. While a Meta app is unpublished, Meta only sends the sample webhooks from its dashboard, not real messages. Fill in the privacy policy URL, icon and category under App settings, then Basic, and click Publish. Publishing doesn't make anything public, and an app that only uses your own WhatsApp account doesn't need App Review.

Send a WhatsApp message to your number. It appears in the inbox within a few seconds and the AI replies on WhatsApp. Reload the WhatsApp tab and it shows when Meta last called.

How WhatsApp conversations work

Replying from the inbox

WhatsApp conversations show a green WhatsApp mark in the inbox list and header. Reply, take over, assign, snooze and close them as usual. See Using the Chat Inbox.

What isn't available on WhatsApp yet

Troubleshooting

Messages don't arrive in the inbox

Replies show "Not delivered on WhatsApp"

The reason is shown under the message. The usual causes are an expired access token (reconnect with a permanent one) and the 24-hour window. For other chat problems, see Troubleshooting Chat.