This tutorial walks you through connecting your qlar agent to a WhatsApp Business number using Qontak as your WhatsApp Business API provider.

The example connects Atlas, Kirana Group's operations assistant, to Kirana's WhatsApp Business number 6281200000000, so site supervisors and field staff can ask Atlas about approvals and site safety from their phones.


Before you start

  • Your agent answers well in Preview and has been published at least once. See Preview and Publish Changes.
  • You have read Connect to WhatsApp, which explains the Published and Draft configurations used below.
  • You use Qontak as your WhatsApp Business provider. If you only want to get your agent on WhatsApp quickly, the Quick Start: Public Server needs no provider account.

From Qontak, make sure you have:

  • An active Qontak account.
  • A WhatsApp Business number registered through Qontak.
  • Your Channel Integration ID and Access Token. Qontak provides both after you complete the channel registration on their platform. The Channel Integration ID is a GUID, for example 6d25a1e6-e7b3-4f3e-a6b2-6b530d881c25.

Note: If Qontak has not sent you the Channel Integration ID and Access Token yet, you can still create the configuration now (Step 2) and fill them in later.


Step 1: Open Channel Settings

  1. Open the CMS dashboard and select the agent you want to connect.
  2. In the left sidebar, open Channels β†’ WhatsApp.
  3. Choose which configuration to set up: Published Configuration (for live users) or Draft Configuration (for testing). Click the corresponding tab.

Note: You can configure both tabs independently. Start with Draft to test first, then repeat the steps for Published when ready to go live.


Step 2: Enter the phone number and click Next

If no WhatsApp number has been connected yet, the Connect WhatsApp wizard appears.

  1. In the Protocol dropdown, select Qontak.
  2. In the Phone Number field, enter the number registered with Qontak, starting with the country code. For Kirana that is 6281200000000. For Qontak this field is optional, but filling it in helps you match the configuration to the right number.
  3. Click Next.

Clicking Next creates the configuration right away. There is no separate confirmation. The wizard closes and the configuration screen opens. Its header shows the Active switch, the Notifications button and a β‹― menu, which holds Delete channel. The integration stays inactive in practice until every required field is filled in and the endpoint is set, so continue with the next steps.

Qontak configuration screen after clicking Next: Qontak label, Active switch, a greyed-out Notifications button and a three-dot menu at the top; Connection & Credentials card with an Edit button, Phone Number (registered with Qontak) 6281200000000, an info box saying to contact the Qontak provider with that phone number to get the Channel Integration ID and Access Token, an empty Channel Integration ID field with a GUID example, and under API Credentials an empty Access Token field and a disabled Set Endpoint button with the hint to save the Channel Integration ID and Access Token first

The screen shows one card, Connection & Credentials. It holds Phone Number (registered with Qontak), an info box, the Channel Integration ID field, and under API Credentials the Access Token field and the Set Endpoint button. The card is read-only until you click Edit.

Unlike Meta Cloud and Coster, there is no Webhook Secret and no webhook URL to send. Qontak's webhook is registered with the Set Endpoint button instead. Reply Mode and Session Management appear only after the endpoint is set.


Step 3: Enter the Channel Integration ID and Access Token

The info box says: contact the Qontak provider with the phone number above, and the provider supplies the Channel Integration ID and Access Token.

  1. Click Edit in the top-right of the Connection & Credentials card. The fields become editable, and Cancel and Save appear at the bottom of the card.
  2. Channel Integration ID: enter the GUID provided by Qontak, for example 6d25a1e6-e7b3-4f3e-a6b2-6b530d881c25.
  3. Access Token: enter the access token provided by Qontak.
  4. Click Save at the bottom of the card. The CMS asks Save these changes? On the Published Configuration tab it warns instead that the change is applied to the live agent immediately. Click Yes.
  5. A message confirms Connection and credentials saved. The card goes back to read-only.

Cancel discards what you typed and closes the edit. While you are editing, the card shows Unsaved changes next to its buttons.

Set Endpoint stays disabled until both values are saved, and while the card is being edited. Next to it, the hint reads "Save the Channel Integration ID and Access Token first, then click Set Endpoint."


Step 4: Register the webhook (Set Endpoint)

Set Endpoint registers qlar's webhook address directly with the Qontak platform.

  1. Click Set Endpoint.
  2. The CMS warns that this changes the webhook destination on the Qontak server, so all incoming WhatsApp messages are forwarded to qlar. Click Yes.
  3. Wait for the confirmation message. The button changes to βœ“ Endpoint Configured and the hint reads "Webhook registered. WhatsApp messages are forwarded to Qlar.ai."

Now the Reply Mode and Session Management cards appear.

Warning: Set Endpoint contacts Qontak's API on your behalf. Make sure your Qontak account is active and the Channel Integration ID is correct before clicking it. An incorrect ID makes the registration fail.


Step 5: Choose the reply mode and session settings

  1. Under Reply Mode, keep AI agent so Atlas answers directly on WhatsApp. Redirect to web sends every private message an instant one-time sign-in link to the agent's web chat instead, and no AI runs on WhatsApp. To set it up, including the Qontak-only button template, follow Redirect to Web Chat; WhatsApp in Help lists its settings.
  2. Under Session Management, keep the defaults unless you have a reason to change them: Ask User to End Session on, Delay Before Ask More 300 seconds, Delay Before End Session 600 seconds. See Session Management.
  3. If you changed anything in Session Management, click Save at the bottom of that card and confirm. Its Discard button puts the saved values back.

Each card saves only its own fields, so saving Session Management never sends a half-finished edit in another card.


Step 6: Publish

Saving marks your agent as having unpublished changes, so the Publish button appears at the top of the CMS. Click Publish so the connection is synced to the live version of your agent.

The Notifications button at the top of the screen opens the notification settings for this number. It stays greyed out until the Channel Integration ID and Access Token are saved and the endpoint is set, and while Connection & Credentials is being edited. Hover over it to see what is still missing.


Check the result

To verify the connection is working:

  1. From a personal WhatsApp account, send a test message to your WhatsApp Business number, for example Who has to approve a project worth $2.5 million?
  2. The message should appear in your agent's conversation history in the CMS dashboard.
  3. Your agent should respond automatically, with the same kind of answer it gives in Preview.

Tip: If messages are not arriving, check that the Active switch is on and the button shows βœ“ Endpoint Configured. Confirm that the Channel Integration ID is a valid GUID from Qontak and that your Qontak account has the correct permissions for webhook configuration.


Next steps