ConnectWiz for Zalo

Early access

70 million Vietnamese users. One OA. Zero token babysitting.

Zalo rotates its refresh tokens on every use — the credential dance that quietly kills most integrations. ConnectWiz handles the rotation mid-send, persists the new pair, retries once, and keeps the conversation moving.

Verified, signed inbound Same inbox, same AI Scope stated, not implied
Zalo — customer conversation
Chào shop! Đơn hàng #4419 của mình khi nào giao tới ạ?
Wiz · AI agent
Chào bạn! Đơn #4419 đang trên đường giao, dự kiến đến trước 17h hôm nay 🚚
VI detected Tokens: rotated & saved Signature verified
5
Credentials in the connect — validated by reading your OA profile before anything saves
1
Automatic retry after a mid-send token rotation — the message still leaves
100%
Of rotated tokens persisted — Zalo’s rotating refresh tokens never strand the channel
1
Inbox — Zalo beside WhatsApp, email and everything else

The case for the channel

Why Zalo is Vietnam’s business channel

Where Vietnamese commerce talks

Zalo is Vietnam’s default messenger — for orders, questions and trust, it’s the channel customers check first.

Vietnamese-first AI

Wiz detects and answers in Vietnamese from your content; your team follows with two-way translation, no Vietnamese speakers required.

Cross-border without an office

A Zalo OA answered instantly in Vietnamese removes the language and channel barriers cross-border sellers actually lose customers to.

Connect & security

Engineered like a channel, not bolted on like a plugin

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

Abstract 3D illustration: a blue chat bubble with two interlocking rotating rings suggesting rotating credentials

A real OA connect

App credentials, access and refresh tokens, and the OA secret — five pieces validated by reading your Official Account profile, all but the app ID encrypted at rest.

Rotation, survived

When a send hits an expired token, ConnectWiz refreshes the pair, persists BOTH new tokens, and retries once — the dance most Zalo integrations get wrong, covered by an explicit test.

Signed inbound

Every event is verified with Zalo’s composite signature scheme in constant time — spoofed webhooks bounce at the door.

Quirks, absorbed

Zalo wants its token in a bare header, not a standard bearer — a documented quirk the client handles so you never have to know it existed.

The inbox

The full inbox treatment, from message one

Routed conversations

Zalo 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 Zalo 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 Zalo’s official API, tracked on the conversation, never silently dropped.

Under the hood

The plumbing that makes "early access" safe to run

Exactly-once by ledger

Every event claims an idempotency key before processing — Zalo’s retries die at the database layer.

Same pipeline as all channels

Routing, AI triggering, blocking and history are the same code path every channel uses.

Failures say why

A rejected send marks the message failed with the reason on the thread — never silence.

Text events, deliberately

Only user text events are processed today; other Zalo event types are acknowledged and set aside — stated here, not discovered later.

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

Zalo has no webhook-registration API, so setting the callback URL in the Zalo OA console is a one-time manual step — the panel records it honestly.

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 and files are the first graduation item.

Interactive elements

Zalo’s richer message types follow media — sequenced honestly.

Delivery receipts

API-level confirmation today; receipts with graduation.

Standard channel

What it costs

ConnectWiz side

  • Zalo 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

Zalo side

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

Zalo 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 — detection and generation both. Customers write in Vietnamese and get Vietnamese answers grounded in your knowledge base; agents follow along with two-way translation.

Zalo is a standard channel — $9/month as an add-on or an included plan pick — enabled with our team during early access. Your Zalo OA verification and any Zalo-side terms stay between you and Zalo.

Vietnam’s inbox, wired into yours.

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