Connect WeChat Customer Service
Authorize an enterprise, assign customer service accounts, and bring customer messages into the YundaDesk Inbox.
Updated 2026-08-18
A white-label chat bubble for your site
Send and receive through your own system
Bring customer email into one inbox
Connect WhatsApp Business to serve customers
Connect Facebook Pages and handle messages
Receive and reply to Instagram DMs
Connect a LINE Official Account
Connect a Telegram bot for customer messages
Pending — subject to TikTok review and authorization
Connect a Zalo Official Account
Receive and reply to comments
Connect official enterprise customer service accounts
Customer contacts, group chats, and agent collaboration
Select customer service accounts
Each selected account becomes an independent channel that is enabled immediately, with AI replies off by default.
Applies only to this Website Widget channel. The channel name and theme color are channel-specific too.
Enter the title, description, and welcome message in one language. They are translated automatically for each visitor and reused afterward.
Copy the code below and paste it into your website to load the chat widget.
Copy it into your website, bot profile, or integration docs.
Copy<script src="https://cdn.yundadesk.com/widget.js" data-yd-key="yd_widget_main" async></script>- Widget Key
- yd_widget_main
- Script URL
- https://cdn.yundadesk.com/widget.js
- Direct link
- https://cdn.yundadesk.com/?widget_key=yd_widget_main
Telegram bot setup guide
Three steps: ① find @BotFather to create a bot and get the token → ② paste the token on the left → ③ save and enable; the system receives new messages automatically.
1. Create a Telegram bot
- In Telegram, search for @BotFather and open the chat.
- Send /newbot to create a new bot.
- Follow the prompts to set a display name and username (ending in _bot).
- Copy the bot token returned by BotFather.
2. Enter the token on the left and enable
- Paste the token into “Bot Token” on the left.
- Click “Save” at the top, then “Enable”.
- Click “Test connection” to verify the bot token works.
3. Test the bot
- Search for the bot username in Telegram and start a chat.
- Send any message and AI / an agent will reply automatically.
- See Telegram Bot API docs.
The channel credential has expired. Please reauthorize and try again.
Connection failedTelegram bot setup guide
Three steps: ① find @BotFather to create a bot and get the token → ② paste the token on the left → ③ save and enable; the system receives new messages automatically.
1. Create a Telegram bot
- In Telegram, search for @BotFather and open the chat.
- Send /newbot to create a new bot.
- Follow the prompts to set a display name and username (ending in _bot).
- Copy the bot token returned by BotFather.
2. Enter the token on the left and enable
- Paste the token into “Bot Token” on the left.
- Click “Save” at the top, then “Enable”.
- Click “Test connection” to verify the bot token works.
3. Test the bot
Callbacks go through YundaDesk fixed secure egress. If your receiver restricts sources, add the egress IPs to its allowlist.
Callbacks go through YundaDesk fixed secure egress. Allowlist these IPs: 203.0.113.10, 203.0.113.11
View allowlist IPsCustom API setup guide
1. Create a Custom API channel
- Enter the channel name and “your system callback URL” on the left.
- After saving, the system generates a connection key and signing key to confirm message ownership and request authenticity.
- (Optional) Add an IP allowlist to restrict sources.
2. Forward customer messages to YundaDesk
- POST messages as JSON to the webhook URL above.
- Include the connection key, timestamp, signature, and idempotency key in the headers.
- A 200 response means received; other statuses are treated as failures and retried.
3. Receive reply pushes
- Once enabled, YundaDesk pushes agent / AI replies to the “your system callback URL” you entered on the left.
- Deduplicate by external message ID for idempotency.
| Event | Time | Status |
|---|---|---|
| message.created | 2026/07/28 14:20 | Delivered |
| message.created | 2026/07/28 14:06 | Timeout · retrying |
| conversation.assigned | 2026/07/28 13:41 | Signature rejected |
Install one YundaDesk plugin to add live chat, AI support, and a secure Widget binding to a WordPress site.
Use the same YundaDesk WordPress plugin; after WooCommerce is detected and authorized read-only, sync store, customer, order, product, and current cart context.
Connect a BigCommerce store, sync customer order context, and show recent orders in the workspace sidebar.
This WordPress site will be linked to the current workspace, then returned to WordPress Admin to complete the PKCE exchange.
- Site
- https://wp-review.yundadesk.com
- Workspace
- YundaDesk Review
- Versions
- YundaDesk 1.0.0 · WordPress 7.0.2
- WooCommerce
- 10.9.4 detected; read-only store access still requires a separate approval after site connection
This confirmation creates only the site binding and public Widget configuration. It does not read WooCommerce store data. Read-only WooCommerce access must be approved separately in WordPress Admin.
| Customer | Contact | Channel / source | Location | Last interaction |
|---|---|---|---|---|
| MMaria Garcia | Web Widget | 05/18 | ||
| LLukas Schneider | Telegram+49 30 123456 | 05/20 | ||
| AAna Silva | 05/22 |
Check whether AI is safe to serve, what it answers from, and what needs you.
3 outreach tasks open
Look it up using the order number.
Last 3 real matches: Web Widget · Custom API — 1 externally delivered, 2 pending verification, 0 failed.| Category | Capability | Status | Current state | Integration path |
|---|---|---|---|---|
| Proactive outreach | Broadcast noticeCreate a broadcast draft for a channel or all reachable customers. | Draft only | Batch delivery is missing, so AI cannot send directly to every customer. | Connect batch delivery; until then, only confirmed drafts are allowed. |
| Proactive outreach | Private customer messagePrepare or send a follow-up to one specific customer. | Not available yet | This plan does not include the capability yet. | This capability is not available yet and requires no setup now. |
| Proactive outreach | Segment outreachFind customers by conditions and draft outreach for that segment. | Needs setup | Customer segment search is missing, so the target audience cannot be located. | Connect customer segment search to enable this capability. |
| Customer data | Customer profile readRead customer profiles to enrich answers, memory, and outreach decisions. | Available | Read customer profiles to enrich answers, memory, and outreach decisions. | Yuna can use this in learning, answering, and outreach decisions. |
↳Yes, Brazil shipping usually takes 7-12 business days.
Human answered·1↳Auto-detect VIP customers · Detect VIP status and prompt agents to follow up first.
Human answered·1·L2 risk↳Opened items can be returned within 30 days if the package is complete.
Human answered·1↳If DHL has not updated for over 72 hours, check the order first, then hand off for compensation review.
You corrected·1·L2 risk| Skill | Status | Use case | Last 7 days | Actions |
|---|---|---|---|---|
| Order tracking lookupWhen a customer asks where an order is, look it up first, then reply in brand voice. | Active | Lookup | Used 12 times92% success | › |
| Auto-detect VIP customersDetect VIP status and prompt agents to follow up first. | Testing | Triage | Not used yet | › |
When a customer asks where an order is, look it up first, then reply in brand voice.
Choose a customer scenario and run a side-effect-free simulation with the production executor.
Simulation never messages customers or performs real external actions.
Shows real customer-conversation calls only; scenario simulations are excluded.
| Dimension | Conversations | Messages | Avg. first response | Resolved | Share |
|---|---|---|---|---|---|
| Web Widget | 712 | 4,128 | 38s | 496 | 60% |
| Telegram | 284 | 1,620 | 45s | 219 | 24% |
| 198 | 980 | 3m 12s | 146 | 17% |
Profile & project
Agent identity
Basic information
Project identity
Team members
| Member | Role | Status & skills | Last sign-in | Last used | Actions |
|---|---|---|---|---|---|
| ACAnna ChenMeanna@yundadesk.testOnline | Admin | ActiveEnglishRefundsMax 12 concurrent | Today, 09:42 | 2 min ago | |
| LWLeo Wangleo@yundadesk.testOnline | Agent | ActiveEnglishAfter-salesMax 6 concurrent | Yesterday, 18:20 | Today, 10:06 | |
| MGMaria Garciamaria@yundadesk.testOffline | Agent | PendingSpanishPre-salesMax 8 concurrent | — | — |
Notifications
Notification permission
Notification settings
Notification scenes
Test notification
Send testSend a test notification to verify everything works.
Send key
Send-key preference for the conversation input, saved per agent.
Proactive outreach
SaveOutreach policy
Anti-spam and confidence
Human review
Subscription & usage
Upgrade planBuy AI CreditPurchase historyContact opsUsage quotas
Entitlement gate
Write actions are allowed based on workspace status, feature flags and quota usage.
Could not establish a secure connection. If the site is HTTP-only, crawl it again with an http:// URL
| Document | Size | Tags | Updated | Status | Actions |
|---|---|---|---|---|---|
| Support knowledge · Notion · 128 docsSource folder · expand to view synced documents | — | — | Last synced 2026/07/29 03:10 | Retrievable | ⋯ |
| Brazil shipping timelinesCompiled 12 FAQ pairs | — | Updated Jun 3, 2026, 4:00 PM | Searchable | ⋯ | |
| EU customs & duties | — | Updated Jun 4, 2026, 2:30 PM | Indexing | ⋯ | |
| 30-day refund policyCompiled 9 FAQ pairs | — | Updated Jun 2, 2026, 8:00 PM | Searchable | ⋯ |
| Document | Size | Tags | Updated | Status | Actions |
|---|---|---|---|---|---|
| Brazil shipping policy | — | Updated Jun 3, 2026, 4:05 PM | Waiting to index | ⋯ | |
| EU customs & duties | — | Updated Jun 4, 2026, 2:30 PM | Indexing | ⋯ | |
| Brazil shipping timelines | — | Updated Jun 3, 2026, 4:00 PM | Searchable | ⋯ | |
| Import restrictions PDFError: The PDF contains no readable text | — | Updated Jun 7, 2026, 4:30 PM | Indexing failed | ⋯ |
| Document | Size | Tags | Updated | Status | Actions |
|---|---|---|---|---|---|
| tgo.ai · 0 pagesProcessed 3 / Discovered 50 pages | — | — | Crawl job running | Crawling | ⋯ |
| tgo.ai · 47 pagesLast sync succeeded · 47 pages | — | — | Last synced Jun 20, 2026, 4:00 PM | Searchable | ⋯ |
| Customer question | Standard answer | Source | Tags | Status | Actions |
|---|---|---|---|---|---|
| Do you ship to Brazil? | Shipping to Brazil usually takes 7-12 business days. | Compiled · Brazil shipping policy | Enabled | ⋯ |
Connect Notion, choose the pages to sync, and import documents automatically.
Connect NotionNotion is not connected yet
agent confirmationCart recovery is ready to reach 1 customer — confirm the flow.
agent confirmationNew FAQ: track packages from the order page after dispatch.
A customer asked about product materials. Review whether it belongs in the learning base.
A Telegram reply was not delivered. Check channel delivery.
An AI reception run failed. You can inspect the answer trail.
What needs my attention today?
Three things: 2 learning suggestions to review and 1 outreach waiting for your confirmation. Yesterday's auto-resolution hit 84%, up 3 points.
Choose whether built-in or external AI handles automatic replies.
Both visitors and agents will see this name
Selected channels are handled by the current AI. Channels not selected here will not use AI replies.
SelectChoose the AI service that replies across all assigned channels.
Maya Sales Advisor
This is the name of the same default AI agent. Visitors and agents see it; switching built-in or external source does not create a second AI.
AI reception source
Built-in and external AI are mutually exclusive. The selected source replies for the channels assigned below.
Use YundaDesk managed growth with YundaDesk AI learning, skill generation, and review.
External AI only handles auto-replies. It does not participate in YundaDesk AI learning or skill generation.
Select WeChat Customer Service under Enterprise IM. It receives messages sent to official enterprise customer service accounts, not regular WeCom employee chats.
After the connection is enabled, messages sent to an official enterprise WeChat Customer Service account enter the YundaDesk Inbox. Agents and AI customer service can reply while the conversation remains eligible under WeCom rules.
WeChat Customer Service is not a regular WeCom employee account. Private chats between employees and external contacts, customer group messages, and internal chats are not included in this channel.
One enterprise can connect to only one workspace#
For the same YundaDesk third-party application, an enterprise can be connected to only one YundaDesk workspace at a time. This is an enterprise-level connection, not a connection for one customer service account.
- The same workspace can reauthorize the same enterprise.
- If another workspace scans the authorization code for that enterprise, it sees only This enterprise is already connected to another workspace. The connection is not transferred, and the original workspace is not disclosed.
- An administrator of the original workspace must complete the enterprise disconnect and data cleanup before another workspace can connect the enterprise.
- If the current workspace is connected to enterprise A, disconnect enterprise A before connecting enterprise B.
Before you begin#
You need:
- YundaDesk workspace administrator access;
- a WeCom administrator who can install third-party applications and manage customer service accounts;
- at least one WeChat Customer Service account created in the WeCom admin console;
- a personal WeChat account for real delivery testing; and
- WeChat Customer Service visible on the current workspace's Channels page and included in the current plan.
Understand the complete flow#
| Stage | Where to perform it | Completion signal |
|---|---|---|
| Create accounts | WeCom admin console | At least one WeChat Customer Service account exists |
| Install the app | YundaDesk → Channels → WeChat Customer Service | Enterprise authorization shows Connected |
| Grant management | WeCom → WeChat Customer Service → Manage conversation messages through the API | The account shows Manageable in YundaDesk |
| Enable accounts | YundaDesk → WeChat Customer Service | Each selected account becomes an independent channel showing Enabled / AI replies off |
| Verify messaging | YundaDesk Inbox + personal WeChat | Customer messages and agent replies are delivered both ways |
The interactive demo above previews the YundaDesk authorization, synchronization, and enablement steps. The screenshots below show the corresponding WeCom admin pages. WeCom may display these pages in Chinese depending on the administrator's locale.
1. Create WeChat Customer Service accounts in WeCom#
Sign in to the WeCom admin console as an administrator, open Application Management, and select WeChat Customer Service. Confirm that the application is enabled and review its visibility scope.

Select Create account, then set the avatar and customer-facing name. An enterprise can create multiple accounts. Each account imported into YundaDesk later becomes an independent channel.

WeCom manages its native bot, native human receptionists, welcome message, and automatic conversation end time. These are not YundaDesk agent settings. If a native WeCom agent takes over a conversation, YundaDesk continues to show synchronized messages but makes that conversation read-only.
2. Authorize the enterprise in YundaDesk#
- Open Channels in YundaDesk.
- Select WeChat Customer Service, then select Authorize in WeCom. YundaDesk opens authorization in a new tab while the original workspace stays open.
- Complete the installation as a WeCom administrator and approve the enterprise, member, and WeChat Customer Service permissions shown on the page. The authorization tab returns to YundaDesk when finished, and the original workspace refreshes account status automatically.

Dedicated support for you is an optional WeCom service-provider contact setting. It does not determine whether customer service messages can enter YundaDesk. After approval, return to YundaDesk and wait until the enterprise authorization shows Connected.
3. Grant account management permission in WeCom#
Enterprise authorization lets YundaDesk discover customer service accounts. YundaDesk can manage and exchange messages only for accounts that the enterprise explicitly assigns to it.
In the WeCom admin console, open Application Management → WeChat Customer Service, scroll to the section for managing conversation messages through the API, and select the option to authorize a third-party application.

Open the action menu for the YundaDesk application and select the option to authorize customer service accounts.

Select the accounts that YundaDesk should manage and confirm. If WeCom allows only one third-party application to manage an account at a time, remove the previous management relationship first.

WeCom menu labels can change. Confirm that you are assigning WeChat Customer Service accounts, not regular members, customer contacts, or customer group permissions.
4. Synchronize, select, and enable accounts#
Return to WeChat Customer Service in YundaDesk and select Sync accounts. Immediately after enterprise authorization—but before API management permission is assigned—an account appears as No management permission.

After granting permission in WeCom, synchronize again. The account changes to Manageable. Select the accounts to connect, then select Enable selected accounts.
Enabling selected accounts:
- creates one independent YundaDesk channel for that WeChat Customer Service account;
- keeps conversation sources separated by account;
- allows messages for the account to enter the shared Inbox; and
- enables each channel immediately so agents can reply while the conversation remains eligible under official rules.
AI replies are off by default, so the page shows both Enabled and AI replies off. To use automatic AI reception, select the channel in the AI customer service reception settings. Channel enablement and AI replies are independent states.
5. Verify a real message round trip#
- In the WeCom admin console, get the entry link or QR code for customer service account A.
- Open it from a personal WeChat account and send a test message with a unique marker.
- In the YundaDesk Inbox, confirm that the new conversation shows the correct WeChat Customer Service account as its source.
- Send a human reply from the Inbox and confirm that it arrives in the personal WeChat account.
- If AI reception is enabled, send another customer message and verify that the AI reply is delivered.
- Repeat the test with account B and confirm that the two account sources do not get mixed.
A Sent state in the admin UI is not proof of final delivery. Verify the message in the customer's WeChat client and watch for a later asynchronous failure state.
Connection boundaries and reply limits#
| Item | Behavior after connection |
|---|---|
| Message entry | Only messages sent to imported WeChat Customer Service accounts are included |
| Customer-facing identity | Replies always use the selected customer service account identity, not an individual YundaDesk agent |
| Multiple accounts | Each customer service account becomes an independent channel and conversation source |
| Regular WeCom private chats | Not available to YundaDesk |
| WeCom native human reception | Messages can remain visible, but YundaDesk becomes read-only after a native agent takes over |
The customer must initiate a WeChat Customer Service conversation. Regular API replies are also subject to these rules:
- replies are allowed only within 48 hours of the customer's latest message;
- at most five replies can be sent in the current reply window;
- a new customer message recalculates the reply window and available count; and
- YundaDesk cannot continue regular sending after a native WeCom agent takes over, the session ends, or the account becomes unavailable.
| Inbox state | Available action |
|---|---|
| Reply available | An agent or AI can send within the remaining allowance |
| Waiting for WeCom native reception | Review messages and wait for the official state to change |
| WeCom native agent is serving | Review synchronized messages in read-only mode |
| Session ended | Wait for the customer to start a new conversation |
| Reply window expired or limit reached | Wait for a new customer message before replying |
Assigning a YundaDesk agent does not change the native WeCom reception state. Customers always see the selected WeChat Customer Service account as the sender.
Supported messages#
YundaDesk can display inbound text, commonly used media, and selected structured cards. Outbound messages support text, images, voice, video, and files. Whether a reply can be sent still depends on the current conversation state, reply window, and official limits.
When the official profile provides a usable WeChat nickname, the Inbox shows it first. Otherwise, YundaDesk uses WeChat customer #identifier as a stable fallback.
Synchronize, reauthorize, or disconnect#
First decide whether you need to act on one customer service account or on the enterprise connection:
| Action | Scope | Releases the enterprise from the workspace |
|---|---|---|
| Sync accounts | Refreshes accounts and management permission without changing channel or AI-reply state | No |
| Reauthorize | Restores an enterprise authorization that cannot be verified in the current workspace | No |
| Unlink one account | Stops that account in YundaDesk while keeping the account in WeCom | No |
| Delete the official account | Deletes that account and its entry points without affecting other accounts in the enterprise | No |
| Disconnect the enterprise | Disables every WeChat Customer Service channel for the enterprise and cleans up connection data | Yes, after cleanup finishes |
Unlink and Delete account on an individual account page are not an enterprise disconnect. Even if every customer service account is deleted, the enterprise remains connected to the current workspace until the enterprise disconnect below is completed.
Disconnect the entire enterprise#
Only a workspace administrator who also has channel-management permission can perform this action.
- Open Channels → WeChat Customer Service and select Disconnect enterprise.
- Enter the enterprise name as prompted and confirm. YundaDesk immediately disables every WeChat Customer Service channel for the enterprise. Messaging, account synchronization, and new account enablement stop.
- Ask an enterprise administrator to open Application Management → Third-party apps → YundaDesk in the WeCom admin console and select Delete app.
- Return to YundaDesk, select I deleted it — check status, and confirm again that the app was deleted.
- If WeCom still reports the app as authorized, the page continues waiting and cleanup does not begin. After removal is confirmed, YundaDesk shows Disconnecting and cleaning up data.
- Wait until the page shows Enterprise connection removed. Only then can this enterprise connect to the current workspace or another workspace.
Before the app is deleted in WeCom, you can select Cancel disconnect. YundaDesk verifies the authorization and restores only channels that were enabled when the disconnect started. Channels that were already disabled stay disabled. A disconnect cannot be cancelled after the WeCom authorization is no longer valid.
When the enterprise revokes access in WeCom#
If an enterprise administrator deletes the YundaDesk app directly in WeCom, YundaDesk disables every WeChat Customer Service channel as soon as it receives the revocation notice and begins cleanup. Until cleanup finishes, the enterprise remains assigned to the current workspace and cannot connect to another workspace.
What each connection state means#
| Page state | Meaning and next step |
|---|---|
| Not connected | This workspace has no enterprise connection and can start authorization |
| Connected | Authorization is valid; you can sync or enable accounts, reauthorize, or start an enterprise disconnect |
| Delete the app in the WeCom admin console | The disconnect has started and all channels are disabled; delete the app as instructed, then check its status |
| Reauthorization required | Authorization cannot be verified and all channels are disabled, but the enterprise remains assigned to this workspace; reauthorize with the same enterprise or start a disconnect |
| Disconnecting and cleaning up data | Revocation is confirmed and cleanup is running; authorization and account enablement are unavailable |
| Enterprise connection removed | Cleanup is complete and the enterprise assignment has been released; authorization can start again |
If cleanup temporarily fails, the page continues to show that cleanup is incomplete and YundaDesk retries safely. It does not report a completed disconnect or release the enterprise to another workspace before cleanup succeeds.
What happens to data after cleanup#
An enterprise disconnect removes or anonymizes identifiable data created through that WeChat Customer Service connection, including customer service account details, WeChat customer identities, channel message content, and WeChat Customer Service attachments. Conversation and aggregate reporting structure may remain without identities or message content so reports stay consistent; message positions show a standard cleaned-data notice.
If the same customer also contacted you through the website, email, or another channel, those other identities and histories are not removed by the WeChat Customer Service enterprise disconnect. Enterprise connection removed means both cleanup and release of the enterprise assignment have completed.
Troubleshooting#
“This enterprise is already connected to another workspace”#
Scanning the authorization code again does not transfer the enterprise. Ask an administrator of the original workspace to complete the enterprise disconnect, then wait for cleanup to finish before trying again. For privacy, the message does not identify the original workspace.
The enterprise disconnect keeps waiting for app deletion#
Confirm that an enterprise administrator deleted YundaDesk under Application Management → Third-party apps. Removing management permission from one customer service account is not enough. After deleting the app, return to YundaDesk and select I deleted it — check status.
The page remains on cleanup#
If cleanup fails, YundaDesk keeps every channel disabled and retries without releasing the enterprise connection early. Refresh the page later. Contact YundaDesk Support if the state does not change for an extended period.
No accounts appear after authorization#
Confirm that at least one WeChat Customer Service account exists in WeCom, then select Sync accounts in YundaDesk. If the list remains empty, check that the enterprise authorization is still valid.
An account has no management permission#
Ask the WeCom administrator to grant the YundaDesk application access to that account, then synchronize again. If another third-party application already manages it, resolve the previous relationship first.
Customer messages do not enter the Inbox#
Confirm that the customer used the account's entry link or QR code rather than sending a private message to a regular WeCom employee. Also confirm that the imported channel is enabled.
The reply composer is read-only#
Read the reason shown in the Inbox. Common causes include native WeCom human reception, an ended session, an expired 48-hour window, or all five replies being used.
A message is sent and later fails#
WeCom can report an asynchronous failure after accepting a send request. Use the final Inbox state and the customer's WeChat client as the source of truth. Reauthorize, wait for a new customer message, or retry a retryable message as instructed by the UI.