Five options, side by side
Most confusion comes from treating Zalo as one product. For a business it is several channels with different rules. The table compares them on the questions we ask first.
Zalo channels for business: a working comparison| Option | Who starts the message | What it needs | Typical use | Main limit |
|---|
| OA messages | The customer writes or follows your OA; you reply | A company OA and a developer app with message permissions | Answering questions, bookings, an AI assistant in chat | The OA cannot freely message people who are not in a conversation |
|---|
| ZNS | Your system, triggered by an event | An approved template, the customer's phone number, a paid ZNS setup | Order, delivery and appointment notices | Fixed templates only, a fee per message, no free-form chat |
|---|
| Zalo Mini App | The customer opens the app inside Zalo | A Mini App registered and reviewed by Zalo, and its own build | Booking forms, loyalty cards, simple catalogs | A separate product to build and maintain |
|---|
| Zalo Bot | The user opens or messages the bot | A bot created on Zalo's bot platform and its Bot API | Simple scripted bots and notifications to people who chat with the bot | What it allows for business use, limits and fees: checked in current documentation |
|---|
| Personal Zalo | A salesperson from a phone | Nothing official | Relationship sales | No official API for automation; risk of blocks |
|---|
Zalo sets the rules, fees and API access for each channel and changes them over time. We check the current Zalo documentation for your account on the audit; nothing here is a quote of Zalo's terms.
OA messages: where an AI assistant lives
An AI chatbot on Zalo works through OA messages. The customer writes, Zalo sends the message to your server, and your server replies under the OA name. This is the channel for questions, prices, bookings and hand-off to staff.
The key limit is initiative. An OA reply inside a conversation is treated differently from a message the OA sends on its own. Plan the assistant to answer and to hand over, and treat reminders as a separate decision.
ZNS: notifications by phone number
ZNS (Zalo Notification Service) sends structured messages from your OA to a phone number, even if the person has not written to you. Each template is reviewed by Zalo before use and each message has a fee.
ZNS fits transactional events: an appointment tomorrow, an order shipped, a payment received. It does not fit marketing blasts or open questions. If you want the customer to reply, the template should lead them into the OA chat, where the assistant can answer.
- Good fit: confirmations and reminders tied to a real event
- Poor fit: promotions to a bought phone list
- Needs: consent and a clean phone number in your system
Zalo Mini App: when a chat is not enough
A Mini App is a small web application that opens inside Zalo. It suits tasks with several fields or choices, such as picking a service, a branch and a time slot, or showing a loyalty card.
It is a product, not a setting. Someone builds it, Zalo reviews it, and someone updates it. For most businesses a chat assistant comes first and a Mini App only when the chat starts to feel like a long form.
Zalo Bot: the newer bot platform
Zalo has a bot platform with its own Bot API for creating bots, closer in spirit to Telegram bots than to the OA. It is a separate route from the Official Account.
What it allows for business use, its limits and any fees change over time. We check the current documentation at developers.zalo.me and on the bot platform before choosing it for a project. For an AI assistant that works under your company's name, the OA is still the route we compare it against.
Personal Zalo: the trap
Many sales teams in Vietnam work from personal Zalo accounts. It feels natural to automate them. There is no official API for that, and the tools that do it imitate a person on a phone or in a browser.
The risk is not only a blocked account. Customer conversations stay on employees' phones, and when someone leaves, the history leaves with them. An OA keeps the conversation with the company.
How to choose
Start from the message, not from the technology. Write down the five messages you most need to send or answer, and for each one mark who starts it and whether the customer expects a reply.
- Customer asks, you answer → OA messages, with an AI assistant if the volume justifies it
- Your system reports an event → ZNS template
- Customer fills in several choices → Mini App, or a booking link in chat
- Salesperson keeps a relationship → personal Zalo, without automation, with new leads routed to the OA
What drives the running cost
Each channel has its own cost line. OA packages and ZNS fees go to Zalo; hosting, AI model usage and maintenance go to whoever runs the integration. Our AI lead assistant starts from $2,500 for the build; Zalo's own fees are separate and depend on your volume.
We put every cost line in one table on the AI audit ($900, 2 weeks), so you see the full monthly picture before anything is built.