Skip to content
Since98
Use cases · Zalo OA and CRM

Zalo OA CRM integration: every Zalo conversation lands in your CRM with an owner

Customers write to your Zalo Official Account, but the deal lives in the CRM, and someone copies one into the other. We connect the two: new followers and conversations become contacts with an assigned owner, the chat history sits in the CRM card, and order or appointment events in the CRM send Zalo notifications on approved templates.

02 — Short answers

Short answers before you plan the integration

What does a Zalo OA to CRM integration do?

Short answer
When someone follows your OA or sends a message, the integration finds or creates the contact in the CRM by the follower's Zalo ID; a phone number is added only if the customer shares it. It assigns an owner by your rules and stores the conversation in the contact card. When a deal or order changes stage in the CRM, it can send a ZNS notification such as an order confirmation or an appointment reminder.
How we do it
We use the official Zalo OA and ZNS APIs and the CRM's API. Your OA plan and API access are confirmed on the audit; we also list the events, fields and assignment rules, and test them on a staging copy of the CRM before switching on.
Limits
Whether staff can reply to Zalo from inside the CRM depends on the CRM; for some we build a small reply panel, for others replies stay in the OA's own tools. ZNS has its own template approval and per-message fees from Zalo.

Where does AI come in?

Short answer
Only where it saves typing: a one-line summary of a long conversation for the CRM card, or extracting the product and quantity from a free-text message into deal fields. Replying to customers with AI is a separate project on the Zalo OA AI integration page.
How we do it
We add these steps after the plain integration works and keep them easy to switch off.
Limits
AI summaries can miss details, so the full conversation always stays in the card.
03 — Situations

What breaks between Zalo and the CRM

01

Sales copy phone numbers and chat screenshots from Zalo into the CRM by hand, or not at all

02

Nobody knows who should answer a new OA message, so it waits or two people answer

03

The CRM shows a deal without the Zalo conversation that explains it

04

Order confirmations and reminders are sent manually, one by one

05

When a salesperson leaves, the customer relationship stays in their personal Zalo

04 — In Vietnam

What is specific to Zalo in Vietnam

  • In Vietnam Zalo is the main messaging app for business conversations, so the OA is often the busiest sales channel
  • Only the Official Account has an official API; personal Zalo accounts cannot be connected safely, and automating them risks the account being blocked
  • ZNS messages go to a customer's phone number on Zalo, need a verified OA and templates approved by Zalo, and are charged per message
  • If you already run a CRM such as HubSpot or Bitrix24, Zalo is added to it, not the other way round; what your CRM allows we confirm on the audit
05 — Demo scenario

How a Zalo inquiry flows into the CRM

Zalo OA → CRM · integration flowDemo
  1. CustomerHello, do you have the oak dining table from your Facebook post in stock? I live near your east-side showroom.
  2. SystemNew OA message. No contact with this Zalo ID: contact created in CRM, source “Zalo OA”, area “East side”. No phone number yet: it is added only if the customer shares it.
  3. SystemAssignment rule: east-side showroom, owner Ms Thao. Conversation saved in the contact card.
  4. TeamMs Thao replies on Zalo, confirms stock and invites the customer to the showroom on Saturday.
  5. SystemDeal created: “Oak dining table”, stage “Visit booked”.
  6. SystemFriday: ZNS reminder sent on the approved “showroom visit” template with the address and time.
  7. TeamAfter the visit Ms Thao moves the deal to “Order”; the order confirmation goes out by ZNS.
Demo scenario of our own build · fictional furniture showroom · not a client conversation
06 — Integrations

What we connect

Zalo Official Account API
New followers and messages, conversation history
ZNS (Zalo Notification Service)
Order confirmations and reminders triggered by CRM events, on approved templates
HubSpotconfirm on the audit
Contacts, deals, owners and timeline; replying from the CRM depends on your plan, confirm on the audit
Bitrix24confirm on the audit
Contacts, deals and open channels; confirm on the audit
Other CRM with a documented APIconfirm on the audit
Same flow if contacts, deals and webhooks are available; confirm on the audit
07 — Hand-off to people

Who owns each conversation

  1. Each new conversation gets one owner by area, product or round-robin, as you decide

  2. If the owner does not reply within the time you set, the conversation is reassigned and the manager is told

  3. Existing customers go to their account owner, not to the new-lead queue

  4. Complaints are tagged and routed to the support lead instead of sales

  5. Customers who block the OA or ask to stop are marked in the CRM and excluded from ZNS

08 — Fit

Who it is for, and who it is not for

A good fit if

  • You have a verified Zalo Official Account with daily conversations
  • You already use a CRM with an API, or are choosing one now
  • Several people answer Zalo and you need clear ownership
  • You want order or appointment notifications without sending them by hand

Not a fit if

  • Your sales run on personal Zalo accounts and you will not move to an OA
  • You get a few Zalo messages a week: a shared spreadsheet is enough
  • You expect free mass messaging on Zalo: ZNS is paid and template-based
09 — Risks and data

Risks, limits and Zalo rules

Risks and limits

  • Zalo changes OA and ZNS rules and prices from time to time, which can require changes to the integration
  • A Zalo ID belongs to one follower of your OA, so the same person writing from another account, or giving a different phone number later, creates a duplicate; we agree a manual merge rule
  • If assignment rules are vague, conversations bounce between people; we agree them in writing before launch

Personal data and rules

  • Phone numbers, names and conversations are personal data under Vietnam's rules: the CRM receives only the fields your process needs
  • ZNS messages are sent only to customers who gave their number for that purpose, and opt-outs are respected
  • Access tokens for Zalo and the CRM are stored on your side or in a secured server, never in shared documents
10 — Price

Price and what it includes

quote

How the price is set:Fixed quote after the AI audit ($900, 2 weeks); the audit fee is credited if you order the build. Zalo's ZNS fees and CRM licenses are paid by you directly

Included
  • OA to CRM sync of contacts and conversations
  • Assignment and reassignment rules
  • ZNS notifications on CRM events
  • Test on a staging copy before launch
See all prices
11 — FAQ

Questions about Zalo OA and CRM

Can you connect our personal Zalo accounts to the CRM?

No. Personal Zalo has no official API, and tools that automate it put the account at risk. We move the conversation to your Official Account and connect that.

Do we need a verified OA?

For ZNS notifications, yes. Message sync needs an OA plan with API access; your OA plan and account status are confirmed on the audit.

Can staff reply to Zalo from inside the CRM?

It depends on the CRM and its plan. Where the CRM supports custom channels we connect replies; otherwise staff reply in Zalo's OA tools and the conversation still syncs into the CRM.

How much do ZNS messages cost?

Zalo sets ZNS prices per message and template type and bills you directly. We design the flow so notifications go only when a CRM event needs them.

Is this an AI project?

Mostly not. It is an integration; AI is added only for summaries or extracting details from messages, and only if it saves your team time.

13

Next step

Describe the situation in a few lines. One of the founders replies and says whether we can help and what the first step would be.

Book an AI audit call
Or write in a messenger: