Connect to WhatsApp
Link your agent to a WhatsApp Business number so users can chat with it directly from WhatsApp.
Understanding Dual Configuration
Every agent in qlar supports two independent WhatsApp numbers at the same time — one for each version of your agent.
| Tab | Purpose |
|---|---|
| Published Configuration | The number your live users interact with. Tied to the published (production) version of your agent. |
| Draft Configuration | A separate number used for internal testing. Tied to the draft version of your agent, so you can test changes without affecting live users. |
The Draft Configuration is optional. You can leave it unconfigured if you do not need a dedicated test number.
Tip: Using a separate draft number lets you iterate on your agent's behaviour and test new API integrations without any risk of breaking conversations that are already happening on your production number.
Supported Protocols
qlar supports three WhatsApp Business API providers. Choose the one that matches your existing infrastructure or your preferred partner.
| Protocol | Best for |
|---|---|
| Meta Cloud | Teams using Meta's own WhatsApp Business Platform directly. Requires a Meta Developer account and a verified WhatsApp Business number. |
| Coster | Teams using the Coster BSP (Business Solution Provider) for WhatsApp. Requires Coster Account ID, Division ID, and access tokens. |
| Qontak | Teams using Qontak as their WhatsApp Business API provider. The Channel Integration ID is provided by Qontak after you complete registration on their platform. |
Choose Your Protocol
Select the tutorial that matches your provider:
Where to Find the Channel Settings
In all three protocols the starting point is the same:
- Open the CMS dashboard and select your agent.
- In the left sidebar, click Channel.
- Click the WhatsApp tab.
- You will see the Published Configuration tab and the Draft Configuration tab. Configure each independently.
Note: If you have not yet connected any number, you will see a setup wizard asking you to choose a protocol and enter a phone number. After the first save, the wizard is replaced by the full settings form.
Session Management
After connecting your number, scroll down to the Session Management section in the configuration form. These settings are the same for all three protocols and control when qlar considers a conversation session to have ended.
Note for Qontak: The Session Management section only becomes visible after you have successfully clicked Set Endpoint. Complete that step first before configuring session settings.
| Setting | Default | Description |
|---|---|---|
| Ask User to End Session | Enabled | When enabled, qlar asks the user to confirm before closing the session instead of ending it automatically. |
| Delay Before Ask (seconds) | 300 | How many seconds of inactivity before qlar asks if the user needs more help. |
| Delay Before End Session (seconds) | 600 | How many seconds after asking before the session is automatically closed. |
Adjust these values to match your use case, then click Save.