Skip to content

Channel Deployment Guide

Detailed guide for connecting your AI employee to Telegram or Lark.

Supported Channels

ChannelStatusBest For
TelegramAvailableInternational users, personal use
Lark (Feishu)AvailableDomestic teams, enterprise use
WeCom (企业微信)AvailableDomestic enterprise users
DingTalk (钉钉)AvailableDomestic teams, no public callback needed
WhatsAppAvailableInternational business users
DiscordComing SoonDeveloper/community scenarios
SlackAvailableEuropean/US enterprise users

Tip: You can connect multiple channels simultaneously. Your AI employee responds across all connected channels. Pro plan supports Telegram + Lark dual-channel access.

Prerequisites

ItemDescription
COCO AccountRegistered and paid/trial active
Channel AccountYour Telegram or Lark platform account
~10 minutesTime to complete deployment

You do NOT need:

  • Any servers or technical infrastructure
  • Any coding skills
  • API keys or developer accounts
  • Any technical knowledge

Estimated time: 5-8 minutes

Step 1: Create a Telegram Bot

Create a Telegram Bot — Complete 4 steps via BotFather
  1. Open Telegram, search for @BotFather (official bot manager)
  2. Send /newbot command
  3. Enter your Bot display name (e.g., My COCO AI)
  4. Enter your Bot username (must end with bot, e.g., my_coco_ai_bot)
  5. BotFather returns a Bot Token (format: 110201543:AAHdqTcvCH1vGWJxfSeofSAs0K5PALDsaw)
  6. Copy and save this Token — you'll need it next

Important: The Bot Token is your bot's unique credential. Do not share it with others.

In @BotFather:

  1. Send /setdescription → Select your Bot → Enter description
    • Suggested: COCO AI Digital Employee - Your Dedicated AI Assistant
  2. Send /setuserpic → Select your Bot → Upload an avatar
    • Recommended: Use COCO logo or your company logo

Step 3: Connect in COCO Dashboard

  1. Log into COCO Dashboard
  2. Go to the channel configuration page, select Telegram
  3. Paste the Bot Token from Step 1
  4. Click Verify and Connect
  5. System automatically validates the Token and completes connection

Step 4: Start Using

  1. In Telegram, search for your Bot username (e.g., @my_coco_ai_bot)
  2. Click Start or send /start
  3. Send any message — AI employee responds immediately
  4. Deployment complete!

Tip: Telegram is the simplest deployment. No admin permissions needed, no extra configuration. Recommended for first-time users.

Telegram FAQ

IssueSolution
Bot not respondingCheck if Token is correct, verify connection status in Dashboard
Slow responsesCheck network connection. Telegram requires stable internet
Want multi-user accessAdd Bot to a Telegram group. All group members can interact with AI
Want to switch BotDisconnect old one in Dashboard, create new Bot and reconnect

Option B: Lark / Feishu Deployment

Estimated time: 8-15 minutes

Note: Adding a self-built app (Bot) in Lark/Feishu requires enterprise admin approval. If you don't want to set up an enterprise Bot right away, you can first create a Lark personal account (international) or Feishu personal account (domestic). You can create and use Bots in your personal workspace without admin approval.

Lark (international) and Feishu (domestic China) have slightly different interfaces. Choose the guide that matches your platform:

Lark Deployment (Recommended for international teams)

Step 1: Access Lark Open Platform

  1. Visit Lark Open Platform
  2. Log in with your Lark account
  3. Click Developer Backend in the top-right corner

Step 2: Create a Custom App

  1. In the Developer Backend, click Create Custom App
  2. Enter app name (e.g., COCO AI Employee) and description
  3. After creation, note down:
    • App ID
    • App Secret

Tip: Enterprise admin permissions are required. If you're not an admin, contact your IT department or use a Lark personal account first.

Step 3: Configure Permissions

In the app management page, go to Permissions & Scopes. Copy the following JSON and import all permissions at once:

json
{
  "scopes": {
    "tenant": [
      "contact:contact.base:readonly",
      "contact:user.base:readonly",
      "im:app_feed_card:write",
      "im:chat",
      "im:chat.announcement:read",
      "im:chat.announcement:write_only",
      "im:chat.chat_pins:read",
      "im:chat.chat_pins:write_only",
      "im:chat.collab_plugins:read",
      "im:chat.collab_plugins:write_only",
      "im:chat.labels",
      "im:chat.managers:write_only",
      "im:chat.members:bot_access",
      "im:chat.members:read",
      "im:chat.members:write_only",
      "im:chat.menu_tree:read",
      "im:chat.menu_tree:write_only",
      "im:chat.moderation:read",
      "im:chat.tabs:read",
      "im:chat.tabs:write_only",
      "im:chat.top_notice:write_only",
      "im:chat.widgets:read",
      "im:chat.widgets:write_only",
      "im:chat:create",
      "im:chat:delete",
      "im:chat:moderation:write_only",
      "im:chat:operate_as_owner",
      "im:chat:read",
      "im:chat:readonly",
      "im:chat:update",
      "im:datasync.feed_card.time_sensitive:write",
      "im:message",
      "im:message.group_at_msg:readonly",
      "im:message.group_msg",
      "im:message.group_msg:readonly",
      "im:message.p2p_msg:readonly",
      "im:message.pins:read",
      "im:message.pins:write_only",
      "im:message.reactions:read",
      "im:message.reactions:write_only",
      "im:message.urgent",
      "im:message.urgent:phone",
      "im:message.urgent:sms",
      "im:message:readonly",
      "im:message:recall",
      "im:message:send_as_bot",
      "im:message:send_multi_depts",
      "im:message:send_sys_msg",
      "im:message:update",
      "im:resource",
      "im:url_preview.update",
      "im:user_agent:read"
    ],
    "user": []
  }
}

Scope overview: The scopes above cover contacts (read), chat management (full), messaging (send/receive/recall/pin/react), group @mention listening, urgent messages, file resources, and feed cards. The im:message:send_multi_depts scope replaces the older im:message:send_multi_users name used in previous versions of the platform. The Feishu (domestic China) version uses a slightly smaller scope set — see the Feishu section for details.

Step 4: Get Verification Token

  1. In app management, go to Events & Callbacks
  2. Click the Encryption Strategy tab
  3. Find the Verification Token at the bottom of the page, click the eye icon to view and copy it

Tip: On the same page you'll also find the Encrypt Key (optional). If you need encrypted communication, record this as well.

Step 5: Connect in COCO Dashboard and Deploy

  1. Log into COCO Dashboard
  2. Go to the channel configuration page, select Lark
  3. Enter the following credentials:
FieldSource
App IDLark Open Platform → Credentials & Basic Info
App SecretLark Open Platform → Credentials & Basic Info
Verification TokenLark Open Platform → Events & Callbacks → Encryption Strategy
Encrypt Key (optional)Lark Open Platform → Events & Callbacks → Encryption Strategy
  1. Click Connect — the system will automatically deploy your AI employee (typically takes 2-3 minutes)
  2. After deployment, the page will display your dedicated Webhook URL — copy this URL (needed in the next step)

Step 6: Configure Event Subscription

  1. Return to the Lark Developer Backend, go to Events & Callbacks
  2. Under "Event Configuration", select Send events to developer server
  3. Paste the Webhook URL from the previous step into the Request URL field
  4. Subscribe to events:
    • im.message.receive_v1 — Receive messages (required)
    • im.chat.member.bot.added_v1 — Bot added to group (optional)
  5. Click Save

Step 7: Create Version and Publish

  1. In the Lark Developer Backend, go to Version Management & Publishing
  2. Click Create Version
  3. Enter version number (e.g., 1.0.0) and update description
  4. Confirm app capabilities and permissions, click Save
  5. In the confirmation dialog, click Confirm Publish

Admin Approval: After publishing a Lark custom app, the enterprise admin must approve it in the Lark Admin Console before the app becomes active. If you're using a personal account, this step is not needed.

Step 8: Enable Bot and Add to Groups

  1. In Lark Open Platform, go to Bot menu, confirm bot functionality is enabled
  2. Open Lark client
  3. Create or enter a group
  4. Group Settings → BotsAdd Bot → Search for your app name
  5. Confirm addition
  6. @mention your bot in the group and send a message
  7. AI employee responds → Deployment complete!

Also works in private chat: Search for your app name in Lark and start a direct conversation.


Feishu Deployment (Recommended for domestic China teams)

WebSocket (Recommended): Simplest setup — only needs App ID and App Secret, no Webhook URL or verification required.

Webhook (Traditional): Feishu pushes events to a Webhook URL — requires Verification Token configuration.

Step 1: Access Feishu Open Platform

  1. Visit Feishu Open Platform
  2. Log in with your Feishu account
  3. Click Developer Backend in the top-right corner

Step 2: Create an Enterprise App

  1. In the Developer Backend, click Create Custom App
  2. Enter app name (e.g., COCO AI Employee) and description, select an app icon
  3. Click Create to finish
  4. After creation, go to Credentials & Basic Info in the left sidebar and note down:
    • App ID
    • App Secret

Tip: Enterprise admin permissions are required. If you're not an admin, contact your IT department or use a Feishu personal account first.

Step 3: Add Bot Capability and Configure Permissions

In the app management page, first add the Bot capability by clicking + Add, then go to Permission Management in the left sidebar.

In the Permission Management page, copy the following JSON and import all permissions at once:

json
{
  "scopes": {
    "tenant": [
      "contact:contact.base:readonly",
      "contact:user.base:readonly",
      "im:app_feed_card:write",
      "im:chat",
      "im:chat.announcement:read",
      "im:chat.announcement:write_only",
      "im:chat.chat_pins:read",
      "im:chat.chat_pins:write_only",
      "im:chat.collab_plugins:read",
      "im:chat.collab_plugins:write_only",
      "im:chat.managers:write_only",
      "im:chat.members:bot_access",
      "im:chat.members:read",
      "im:chat.members:write_only",
      "im:chat.menu_tree:read",
      "im:chat.menu_tree:write_only",
      "im:chat.moderation:read",
      "im:chat.tabs:read",
      "im:chat.tabs:write_only",
      "im:chat.top_notice:write_only",
      "im:chat.widgets:read",
      "im:chat.widgets:write_only",
      "im:chat:create",
      "im:chat:delete",
      "im:chat:moderation:write_only",
      "im:chat:operate_as_owner",
      "im:chat:read",
      "im:chat:readonly",
      "im:chat:update",
      "im:datasync.feed_card.time_sensitive:write",
      "im:message",
      "im:message.group_at_msg:readonly",
      "im:message.group_msg",
      "im:message.p2p_msg:readonly",
      "im:message.pins:read",
      "im:message.pins:write_only",
      "im:message.reactions:read",
      "im:message.reactions:write_only",
      "im:message.urgent",
      "im:message.urgent:phone",
      "im:message.urgent:sms",
      "im:message:readonly",
      "im:message:recall",
      "im:message:send_as_bot",
      "im:message:send_multi_depts",
      "im:message:send_sys_msg",
      "im:message:update",
      "im:resource",
      "im:url_preview.update",
      "im:user_agent:read"
    ],
    "user": []
  }
}

Feishu vs Lark scopes: The Feishu (domestic China) scope set above differs slightly from the Lark (international) version. Two scopes — im:chat.labels and im:message.group_msg:readonly — are not supported on the Feishu China platform and have been removed. All other scopes are identical.

Step 4: Get Verification Token

  1. In app management, go to Events & Callbacks
  2. Click the Encryption Strategy tab
  3. Find the Verification Token at the bottom of the page, click the eye icon to view and copy it

Tip: On the same page you'll also find the Encrypt Key (optional). If you need encrypted communication, record this as well.

Step 5: Connect in COCO Dashboard and Deploy

  1. Log into COCO Dashboard
  2. Go to the channel configuration page, select Feishu
  3. Enter the following credentials:
FieldSource
App IDFeishu Open Platform → Credentials & Basic Info
App SecretFeishu Open Platform → Credentials & Basic Info
Verification TokenFeishu Open Platform → Events & Callbacks → Encryption Strategy
Encrypt Key (optional)Feishu Open Platform → Events & Callbacks → Encryption Strategy
  1. Click Connect — the system will automatically deploy your AI employee (typically takes 2-3 minutes)
  2. After deployment, the page will display your dedicated Webhook URL — copy this URL (needed in the next step)

Step 6: Configure Event Subscription

  1. Return to the Feishu Developer Backend, go to Events & Callbacks
  2. Under "Event Configuration", select Send events to developer server
  3. Paste the Webhook URL from the previous step into the Request URL field
  4. Subscribe to events:
    • im.message.receive_v1 — Receive messages (required)
    • im.chat.member.bot.added_v1 — Bot added to group (optional)
  5. Click Save

Step 7: Create Version and Publish

  1. In the Feishu Developer Backend, go to Version Management & Publishing
  2. Click Create Version
  3. Enter version number (e.g., 1.0.0) and update description
  4. Confirm app capabilities and permissions, click Save
  5. In the confirmation dialog, click Confirm Publish

Admin Approval: After publishing a Feishu custom app, the enterprise admin must approve it in the Feishu Admin Console before the app becomes active. If you're using a personal account, this step is not needed.

Step 8: Enable Bot and Add to Groups

  1. In Feishu Open Platform, go to Bot menu, confirm bot functionality is enabled
  2. Open Feishu client
  3. Create or enter a group
  4. Group Settings → BotsAdd Bot → Search for your app name
  5. Confirm addition
  6. @mention your bot in the group and send a message
  7. AI employee responds → Deployment complete!

Also works in private chat: Search for your app name in Feishu and start a direct conversation.


Option C: WeCom (企业微信) Deployment

Estimated time: 10-15 minutes

Note: WeCom (企业微信) is Tencent's enterprise messaging platform, widely used by Chinese companies. Setting up a self-built application requires enterprise admin access to the WeCom Admin Console.

Five credentials are required:

CredentialDescription
Corp ID (CorpID)Enterprise unique identifier
App SecretApplication credential key
Agent ID (AgentId)Application identifier
TokenCallback verification token
EncodingAESKeyCallback message encryption key (43 characters)

Step 1: Get Your Corp ID (CorpID)

Visit the WeCom Admin Console My Enterprise page. Scroll to the bottom to find the Enterprise ID (企业ID). Copy and save this value.

Get Corp ID

Step 2: Go to App Management and Create an Application

In the left sidebar, go to App Management (应用管理). In the "Self-Built" (自建) section at the bottom, click Create Application (创建应用).

Create Application

Step 3: Set Application Name and Visible Scope

Give your Bot a memorable name (e.g., COCO AI Employee) and set the Visible Scope (可见范围) to select which team members can see and use the Bot.

Set App Name and Visible Scope

Step 4: Get AgentId and Secret, Set Up API Reception

After the application is created, on the application detail page:

  • AgentId — displayed directly on the page
  • Secret — click "View" to obtain

Then in the "Features" section at the bottom, click Receive Messages → Set Up API (接收消息 → 设置API接收).

Get AgentId and Secret

Important: The Secret is only shown once. Save it immediately.

Step 5: Get Token and EncodingAESKey (Do Not Save Yet)

In the "API Message Reception" configuration page:

  • Token — click "Randomly Generate" (随机获取)
  • EncodingAESKey — click "Randomly Generate" (随机获取)
Get Token and EncodingAESKey

Important: Do not save yet — the URL field needs to be filled in Step 7. Keep this page open.

Step 6: Enter Credentials in Dashboard and Connect

In the COCO Dashboard's WeCom channel configuration page, enter all the credentials obtained above. Note the Webhook URL and Server IP displayed on the page, then click Connect and wait for the connection to succeed.

Dashboard Credentials

Step 7: Enter Webhook URL Back in WeCom

After the connection succeeds, copy the Webhook URL from the Dashboard and paste it into the URL field on the "API Message Reception" configuration page you kept open in Step 5. Click Save.

Step 8: Configure Trusted IP

Enter the Server IP from the Dashboard into WeCom's Trusted Enterprise IP (企业可信IP) settings to ensure the server can call WeCom APIs.

Configure Trusted IP

Step 9: Start Chatting

Once configuration is complete:

  1. Search for the Bot name in WeCom and start a conversation
  2. Send any message — your AI employee responds immediately
  3. You can also add the application to a WeCom group for team-wide access
  4. Deployment complete!

Group usage: In a WeCom group chat, @mention your application to interact with the AI employee. All group members within the Visible Scope can use it.

WeCom FAQ

IssueSolution
Cannot save API configurationEnsure you complete the Dashboard connection (Step 6) first — WeCom validates the URL on save
Application not visible to team membersCheck the Visible Scope setting in App Management — make sure all intended users are included
Bot not responding in groupConfirm the application has been added to the group and members are within the Visible Scope
Secret lost or forgottenIn App Management, click Get Secret again — the old Secret is invalidated; reconfigure as needed

Option D: DingTalk (钉钉) Deployment

Estimated time: 8-12 minutes

Note: DingTalk (钉钉) is Alibaba's enterprise collaboration platform, widely used by Chinese companies. DingTalk uses Stream mode (WebSocket long connection), so no public callback URL is needed — deployment is simpler.

Three credentials are required:

CredentialDescription
AppKeyApplication unique identifier
AppSecretApplication credential key
RobotCodeRobot identifier (usually same as AppKey)

Step 1: Access DingTalk Open Platform and Create an Application

Visit the DingTalk Open Platform App Management page and click Create Application.

Create Application

Step 2: Enter Application Name and Description

Enter the Application Name (e.g., COCO AI Employee) and Description, then click Save.

Set App Name

Step 3: Add Robot Capability

After saving, you'll be redirected to the "Add Capabilities" page. Click Add Robot capability.

Add Robot Capability

Step 4: Configure Robot and Select Stream Mode

Open the robot configuration page, fill in the required information, select Stream Mode for message reception, then publish.

Robot ConfigurationSelect Stream Mode

Note: Stream mode uses WebSocket long connections to receive messages — no public callback URL configuration needed, making deployment simpler.

Step 5: Version Management and Publishing

In the left sidebar, select Version Management & Publishing and click Create New Version.

Create New Version

Step 6: Set Application Visible Scope

Enter the version information, select the appropriate Visible Scope (which team members can see and use the Bot), then save and publish.

Set Visible Scope

Step 7: Get AppKey, AppSecret, and RobotCode

In the application detail page under "Credentials & Basic Info":

  • AppKey — application unique identifier
  • AppSecret — click "Show" to view
Get AppKey and AppSecret

On the robot configuration page, find the RobotCode (usually the same as AppKey).

Get RobotCode

Step 8: Enter Credentials in Dashboard

Enter the AppKey, AppSecret, and RobotCode into the COCO Dashboard's DingTalk channel configuration page and click Connect.

Step 9: Start Chatting

Search for the Bot name in DingTalk and start chatting with your AI employee.

Search Bot and Start Chatting

Group usage: In a DingTalk group chat, @mention your Bot to interact with the AI employee.

DingTalk FAQ

IssueSolution
Application not visible to team membersCheck the Visible Scope in version publishing — ensure all intended users are included
Bot not responding in groupConfirm the robot has been added to the group and use @mention to trigger
AppSecret forgottenView or reset in the application credentials page

Option E: Slack Deployment

Estimated time: 8-12 minutes

Note: Slack is widely used by European and US enterprises for team collaboration. Slack uses Socket Mode (WebSocket connection), so no public callback URL is needed — deployment is straightforward.

Two credentials are required:

CredentialFormatDescription
Bot Tokenxoxb-...Bot User OAuth Token, used to call the Slack API
App Tokenxapp-...App-Level Token, used for Socket Mode connection

Step 1: Create a Slack App

  1. Visit Slack App Management and log in
  2. Click Create New App in the top-right corner
  3. Select From scratch in the popup
  4. Enter your App name (e.g., COCO AI Employee) and select the Workspace to install to
  5. Click Create App to finish
Create Slack App

Step 2: Enable Socket Mode and Generate App Token

  1. In the App settings left sidebar, find Socket Mode
  2. Toggle Enable Socket Mode on
  3. When prompted to generate an App-Level Token:
    • Name the Token (e.g., zylos-socket)
    • Add Scope: search and select connections:write
    • Click Generate
  4. Copy and save the generated Token (format: xapp-...)
Enable Socket ModeGenerate App-Level Token

Important: The App Token is displayed only once after generation. Save it immediately. If lost, you'll need to regenerate it.

Step 3: Configure Bot Token Scopes

  1. In the left sidebar, go to OAuth & Permissions
  2. Scroll down to the Scopes section
  3. Under Bot Token Scopes, click Add an OAuth Scope and add the following permissions:
ScopePurpose
app_mentions:readRead @mentions of the bot
channels:historyRead messages in public channels
channels:readView basic channel info
chat:writeSend messages as the bot
files:readRead files shared with the bot
files:writeUpload files
groups:historyRead messages in private channels
groups:readView basic private channel info
im:historyRead direct message history
im:readView basic DM info
im:writeStart direct messages
reactions:readRead emoji reactions
reactions:writeAdd emoji reactions
users:readView user info
Configure Bot Token Scopes

Step 4: Install App to Workspace

  1. Go back to the top of the OAuth & Permissions page
  2. Click Install to Workspace (or Reinstall to Workspace)
  3. Confirm the permissions in the authorization popup, click Allow
  4. After installation, copy and save the Bot User OAuth Token (format: xoxb-...)
Install App to Workspace

Important: Each time you modify Scopes, you must reinstall the App to Workspace. The Token will be regenerated — update your configuration accordingly.

Step 5: Enable Event Subscriptions

  1. In the left sidebar, go to Event Subscriptions
  2. Toggle Enable Events on
  3. Expand Subscribe to bot events, click Add Bot User Event, and add:
EventPurpose
message.imReceive direct messages
message.channelsReceive messages in public channels
message.groupsReceive messages in private channels
app_mentionReceive @mentions
  1. Click Save Changes at the bottom
Enable Event Subscriptions

Step 6: Configure App Home

  1. In the left sidebar, go to App Home
  2. Under Show Tabs:
    • Check Messages Tab
    • Check Allow users to send Slash commands and messages from the messages tab

This enables users to send direct messages to your bot in Slack.

Configure App Home

Step 7: Configure Tokens in COCO Channel

  1. Return to the COCO Dashboard and enter the configuration page for the corresponding Channel
  2. Fill in the following two Tokens:
    • Bot Token (xoxb-...): from Slack App's OAuth & Permissions page
    • App Token (xapp-...): the token generated in Step 2 above
  3. Save the configuration

Step 8: Start Chatting

  1. In Slack, search for your Bot name or find it in the Apps list
  2. Click to start a DM conversation — AI employee responds immediately
  3. To use in a channel, invite the Bot by typing /invite @BotName in the channel
  4. @mention your Bot to trigger responses in the channel
  5. Deployment complete!

Tip: Slack Bot supports both DMs and channel @mentions. You can use it across multiple channels simultaneously.

Slack FAQ

IssueSolution
Bot not respondingVerify both Bot Token and App Token are correct in the Dashboard
Bot not visible in SlackEnsure the App is installed to Workspace (Step 4) and App Home is configured (Step 6)
Bot not responding in channelsThe Bot must be invited to the channel first using /invite @BotName
Token regenerated after scope changeReinstall the App to Workspace after any scope modification, then update tokens in Dashboard
Cannot send DMs to BotConfirm Messages Tab is enabled in App Home settings

Option F: WhatsApp Deployment

Estimated time: ~5 minutes

Note: WhatsApp connects via QR code scanning (linked device), similar to using WhatsApp Web. No API keys, developer accounts, or app configuration are needed — just a phone with WhatsApp installed.

No credentials are required. You only need:

ItemDescription
COCO AI EmployeeAn existing instance in COCO Dashboard
WhatsApp AccountA phone with WhatsApp installed and logged in
~5 minutesTime to complete deployment

Step 1: Create an AI Employee and Enter Configuration Page

  1. Log into COCO Dashboard
  2. Create a new AI employee or select an existing instance
  3. Click Configure → on the employee card to enter the instance detail page
Dashboard Configuration Entry

Step 2: Click WhatsApp "Connect" and Wait for QR Code

  1. In the channel list on the instance detail page, find the WhatsApp card
  2. Click the Connect button
  3. The system will prepare a WhatsApp session in the background — the QR code takes ~30 seconds to generate, please be patient
  4. Once generated, the QR code refreshes automatically every 15 seconds
WhatsApp QR Code

Important: Do not close the page or click repeatedly while waiting — this may trigger duplicate requests.

Step 3: Open WhatsApp on Your Phone → Linked Devices

  1. Open WhatsApp on your phone
  2. Tap Me (profile icon) in the bottom-right corner
  3. In the settings list, tap Linked Devices
WhatsApp Linked Devices
  1. On the "Linked Devices" page, tap the Link a Device button at the bottom
  2. Your phone's camera opens — point it at the QR code displayed on the Dashboard in Step 2
  3. Wait a few seconds for the connection to complete
Link a Device

Tip: If the QR code has expired, the Dashboard will automatically refresh it. Scan the latest QR code displayed.

Step 5: Connection Complete — Start Chatting

  1. After successful scanning, the Dashboard automatically detects the connection — the WhatsApp card shows Connected
  2. You can now send messages to your WhatsApp account, and the AI employee will respond automatically
  3. Share the AI employee's WhatsApp contact with others to let them chat with your AI directly
  4. Deployment complete!

Note: WhatsApp linked devices may disconnect automatically if the phone is offline for an extended period. If disconnected, return to the Dashboard and scan the QR code again to reconnect.

WhatsApp FAQ

IssueSolution
QR code takes a long time to appearThe first generation may take 30-60 seconds — this is normal. Do not close the page
QR code expired before scanningThe QR code auto-refreshes every 15 seconds. Use the latest one displayed
"Already in progress" errorA previous QR request is still running. Wait a moment and it will resolve automatically
WhatsApp disconnected after some timePhone was offline too long. Reconnect by scanning QR code again from the Dashboard
Want to disconnect WhatsAppClick the Disconnect button on the WhatsApp card in the instance detail page