The WhatsApp screen connects WhatsApp numbers to your agent, so people can chat with it on WhatsApp. Found in the agent sidebar under Channels β WhatsApp.
Configuration Scope
| |
|---|
| Published Configuration | The WhatsApp accounts used by the published (live) agent. Available once the agent has been published at least once. |
| Draft Configuration (Optional) | Accounts for the draft version of the agent, so you can test before publishing. Available only when the agent has a draft version. |
Saving Changes
Applies to the Meta Cloud, Coster and Qontak screens. A Qlar (Self-hosted) channel shows its own console.
| |
|---|
| Per-card Save | Every card saves only its own fields. There is no Save or Update button for the whole screen, and saving one card never sends what is still being edited in another. |
| Connection & Credentials | Read-only until Edit. While editing, Save keeps the changes and Cancel drops them. The webhook secret's regenerate icon appears only while editing. |
| Session Management | Save and Discard at the bottom of the card. |
| Redirect to Web | Save and Discard at the bottom of the panel. The button reads Save & submit for review when saving submits a template to WhatsApp. |
| Saved Immediately | The Active switch and Reply Mode. |
| Unsaved Changes | A card with edits not saved yet shows Unsaved changes next to its buttons. Leaving the page with unsaved edits asks for confirmation. |
| Live Confirmation | On the Published Configuration tab, every save asks for confirmation, because it applies to the live agent straight away. |
| Channel Header | Active switch, Notifications button, and the β― menu with Delete channelβ¦. |
Protocol and Account Setup
| |
|---|
| Protocol Selection | Meta Cloud, Coster, Qontak or Qlar (Self-hosted), each with its own fields. Qlar (Self-hosted) links a WhatsApp number without provider credentials: choose Public server β recommended (hosted for you, scan a QR code) or Private β your own machine (run the Qlar Connector app). |
| Account Code / Phone Identity | Channel identity is bound to account code/phone value and used as the messenger account reference. |
| Qontak Endpoint Registration | After saving the Channel Integration ID and Access Token, click Set Endpoint to register the webhook with Qontak. It then shows β Endpoint Configured. |
| Provider Hand-off Details | CMS provides webhook/account details intended to be shared with provider-side setup teams when required. |
Credential and Webhook Management
| |
|---|
| Access Token Management | Primary access token is stored and managed as a required integration credential. |
| Protocol-specific Secrets | Meta Cloud and other protocols expose additional credential fields such as App Secret and account identifiers. |
| Webhook Secret Management | Webhook secret is generated and can be regenerated for channel verification workflows. Regenerate it with the refresh icon while editing Connection & Credentials, then Save. |
Session Behavior Controls
| |
|---|
| Ask User to End Session | Channel can prompt users to close inactive conversations through configurable session behavior. |
| Delay Before Ask More | Delay setting controls when the system asks if user still needs assistance. |
| Delay Before End Session | Delay setting controls when system asks final session-end confirmation after inactivity. |
Notification Panel
| |
|---|
| Notification Settings Entry | The Notifications button in the channel header opens the panel. It is greyed out until every required credential is saved (on Qontak, also until the endpoint is set) and while Connection & Credentials is being edited; hovering over it says what is missing. |
| Template Management Tab | Supports notification template listing, creation path, send action, and deletion flow (protocol-dependent). |
| API Integration Tab | Provides authenticated API integration references with key management and multi-language code examples. |
| History Tab | Provides notification delivery history with filtering, pagination, and CSV export. |
Redirect to Web (Bridge Mode)
WhatsApp charges per message. With bridge mode on, the agent does not chat in WhatsApp at all: every private WhatsApp message is answered straight away with a one-time sign-in link, and the conversation continues in the agent's web chat.
For a step-by-step guide, see Redirect to Web Chat.
| |
|---|
| What Happens | Each private message gets one fixed reply with the link. No AI runs, so no AI tokens are used, and nothing is added to a WhatsApp conversation. |
| One-time Link | The link signs the visitor in as their WhatsApp account. It is valid for 30 minutes and works once. |
| Repeat Messages | While a link is still valid, further messages get the same link again, not a new one (unless a quiet period is set, see below). |
| First Message | What the visitor wrote on WhatsApp is carried to the web chat and sent as the first message, so the agent answers it right away. Attachments are not carried over. |
| End-session Messages | Not sent. Ask User to End Session and the other AI-only settings have no effect while bridge mode is on. |
| Groups | Group messages are ignored: no reply, no link. |
| Used or Expired Link | The web page shows "This link is no longer valid. Send us another WhatsApp message to get a new link." |
Settings
| |
|---|
| Reply Mode | Choose AI agent (the agent answers on WhatsApp) or Redirect to web (bridge mode). Only one can be active. Choosing Redirect to web shows the Redirect to Web panel with the settings below in place of the agent settings (Session Management, or on the Qlar connector the Behaviour section; the linked number and the Contact rules stay visible, because they still decide who receives a link). The hidden settings keep their values and come back when you switch back to AI agent. |
| Target URL | Where the link points. Empty means the agent's own web chat. It can also be a page on your site that embeds the agent's chat widget: the widget picks up the sign-in code by itself and, in floating mode, opens its panel. See Embed chat to website. Must start with https:// and have no # part. |
| Message type | Qontak only. Regular message (default) sends the reply message below with the link written out. Utility template (button) sends the same reply message as a WhatsApp template, with the link as a Continue in Web Chat button (Lanjutkan di Web Chat in Indonesian). The button always opens the agent's own web chat. WhatsApp bills a utility template from the first message, while regular replies include 1,000 free messages per number each month. |
| Template language | With the utility template: the language the template is submitted in, Indonesian (default) or English. It also sets the button's label. |
| Reply message | The reply text. Empty uses a built-in text in the agent's language. A custom text must contain {link}, which is replaced with the link. {minutes} is replaced with how many minutes the link has left. With the utility template this is also the template's text: {link} becomes the button, and a line that holds only {link} disappears. The panel previews both. |
| Template versions | WhatsApp templates cannot be edited or deleted, so saving a changed text (or language) submits it as a new version for WhatsApp to review, after a confirmation. The Save button reads Save & submit for review whenever this will happen; a text that matches the version in use or the one under review submits nothing. Switching Reply Mode to Redirect to web can also submit the saved text, and its confirmation says so. The Draft Configuration submits its own templates, separate from Published and not reused on publish. Review usually takes minutes and at most 24 hours. The panel shows the version In use and the New version with their review status. The version in use keeps going out until the new one is approved, then the new one replaces it. Before any version is approved, and if WhatsApp rejects a text or files it as marketing, the regular message is sent, so the channel never goes quiet. To fix a rejected text, reword it and save again. |
| Quiet period (minutes) | 0 to 30, default 0. With 0, every message is answered with the link. Above 0, further messages within that many minutes are not answered, to save message costs; what the visitor types meanwhile is carried to the web chat as a draft. After that, the link is sent again. |
Security
The link is a sign-in pass for the WhatsApp number it was sent to. Anyone who opens it before it is used, and within 30 minutes, is signed in as that number. Ask visitors not to forward it. Only the most recent link for a number works, and each link works once and for this agent only.
Sending Visuals from Voice Calls
With Send to WhatsApp on in Conversation β Voice, a signed-in user in a voice call can have what is on the screen sent to a WhatsApp number, from this channel's number.
| |
|---|
| Protocols | Only Qlar (Self-hosted), on the public or a private server. Meta Cloud, Coster and Qontak can only start a conversation with an approved message template, and are not supported yet. |
| Which Configuration | Users' calls send from the Published Configuration's channel. Preview calls send from the Draft Configuration's channel, or from the Published one when the draft has none. |
| Contact Rules | The channel's contact rules apply: a blacklisted number, or in private mode a number not on the whitelist, receives nothing. |
| Limits | At most 10 per recipient and 30 in total per hour from one channel. |
| Deleting the Channel | While Send to WhatsApp is on, deleting the channel shows a warning first. Deleting the agent's last channel that can send also turns Send to WhatsApp off. |
Related guide: Connect to WhatsApp