ConnectWiz for WeChat

Early access

A billion users. One Official Account. Zero expired tokens.

WeChat’s API tokens expire roughly every two hours by design, and its customer-service window is strict. ConnectWiz renews the tokens automatically and enforces the window honestly — in the composer, before you type, not as a rejected send after.

Verified, signed inbound Same inbox, same AI Scope stated, not implied
WeChat — customer conversation
你好!这款外套有没有大码?发货到上海要多久?
Wiz · AI agent
你好!XL码有现货。上海一般3-5个工作日送达 🙂 需要我帮您预留一件吗?
ZH detected Token: auto-renewed Window: 41h left
~2h
WeChat’s access-token lifetime — renewed automatically with a safety margin, forever
48h
The customer-service window — enforced server-side with a live countdown in the composer
0
Escape hatches pretended — WeChat has no template fallback like WhatsApp, and we say so
1
Inbox — WeChat beside WhatsApp, email and everything else

The case for the channel

Why WeChat is the door to China

The front door

For Chinese customers, an Official Account is the business — the channel where questions, orders and trust happen.

Chinese-language AI

Wiz answers in Simplified Chinese from your own content; your team reads and replies through two-way translation without speaking a word of it.

The morning shift in Shanghai

Wiz covers Chinese business hours while your office sleeps; escalations queue with context for your morning.

Connect & security

Engineered like a channel, not bolted on like a plugin

Every WeChat event is cryptographically verified and deduplicated before it can touch a conversation — the boring guarantees that make a bridge trustworthy.

Abstract 3D illustration: a jade chat bubble beside an hourglass with a countdown ring and a self-renewing token orbiting between them

Credentials proven at connect

AppID, AppSecret and the OA token are validated by actually minting an access token — a wrong secret can’t create a channel that dies at first send.

Tokens renew themselves

WeChat’s ~2-hour tokens are brokered per channel with an expiry safety margin and never logged — the classic silent-death failure of WeChat integrations is engineered away.

Handshake and signatures

The console’s GET verification handshake is answered automatically, and every inbound event is signature-checked over WeChat’s sorted-tuple scheme before parsing.

Unicode done right

Outbound uses raw UTF-8 the way WeChat requires — escaped unicode garbles Chinese text, and this integration was built by people who know that.

The inbox

The full inbox treatment, from message one

Routed conversations

WeChat messages land as conversations with department routing, assignment, tags, internal notes with @mentions and full history — on desktop and the agent mobile app.

Wiz answers first

The AI agent answers from your own content in 52 languages, escalates to humans with the thread attached, and hands back with one click — the same brain as every other channel.

One customer record

The WeChat identity joins the same CRM contact as email and every other channel — one person, one history, one consent state.

Two-way translation

Agents read incoming messages in their language on demand and send drafts translated into the customer’s — per message, cached for the next reader.

Business-hours aware

Out-of-hours messages get honest expectations and land at the top of the morning queue; the first-response clock measures humans, not bots.

Text, reliably

Two-way text messaging is the scope today — sent through WeChat’s official API, tracked on the conversation, never silently dropped.

Under the hood

The plumbing that makes "early access" safe to run

The 48-hour window, for real

WeChat allows customer-service replies only within 48 hours of the customer’s message, with no template escape hatch. The server states it, the composer locks at hour 49 with the reason and a countdown, and the API refuses — the UI cannot be bypassed.

Exactly-once by ledger

Idempotency keys on WeChat’s message IDs kill duplicates at the database layer.

Same pipeline as all channels

Routing, AI, blocking and history are the same code path every channel uses — one discipline, not per-channel folklore.

Failures say why

A rejected send is marked failed with the reason — silence is the one failure mode we refuse.

The honest scope

What "early access" means here — in writing

Enabled with you, not at you

The integration is built and verified, but hasn’t yet carried enough live production traffic for an unconditional "live" label — so we enable it per workspace, with our team alongside. That’s what the badge means.

Text today

Media, buttons and rich elements are on the roadmap and deliberately unpromised — a page that sells a composer feature that isn’t there yet costs more trust than it earns.

Optimistic delivery

Sends are confirmed at the API level; per-message delivery receipts aren’t wired on this channel yet, and the thread doesn’t pretend otherwise.

One console step

WeChat has no webhook-registration API, so setting the server URL in the WeChat console is a one-time manual step — recorded honestly as such in the panel.

Roadmap & graduation

What ships next — and what flips the badge

The graduation bar is measurement, not marketing: enough live production traffic to verify the channel end to end. Then the badge comes off and these land, in order.

Media both ways

Images, voice and files are the first graduation item.

Template messages

WeChat’s service templates — after media, honestly sequenced.

Delivery receipts

API-level confirmation today; receipts with graduation.

Standard channel

What it costs

ConnectWiz side

  • WeChat is a standard channel: one of your plan’s included picks, or $9/month as an add-on — the same price during early access
  • Early access adds hands: we enable and watch the channel with you, at no extra cost
  • Conversations count toward your plan’s normal allowance; AI answers draw on your AI credits
See ConnectWiz plans

WeChat side

Your WeChat account, verification and any platform-side terms stay between you and WeChat — ConnectWiz adds no markup and never proxies your account relationship.

WeChat FAQ

Straight answers

More in the full FAQ, or ask us directly.

The integration is built and its inbound path is cryptographically verified, but it hasn’t yet carried enough live production traffic for us to put an unconditional "live" label on it. So we enable it per workspace, with our team alongside — contact us and we’ll switch it on together.

Two-way text conversations with the full inbox treatment: department routing, assignment, tags, history and Wiz AI answers. Media and rich elements are on the early-access roadmap and deliberately not promised before they ship.

With live production traffic: once real workspaces have run the channel through enough volume for the integration’s behavior to be verified end to end, the badge comes off and the roadmap items (media, richer elements, receipts) land one by one. The bar is measurement, not marketing.

Yes. Wiz answers in Chinese from your knowledge base, and your team follows with two-way translation — reading incoming messages in their language and replying in it.

WeChat is a standard channel — $9/month as an add-on or an included plan pick — enabled with our team during early access. Your Official Account relationship and any WeChat-side costs stay yours.

The Official Account your Chinese customers expect.

Request early access and we’ll enable the channel with you — honestly scoped from day one.