Skip to content
Since98
Insights · AI & Automation

How to connect an AI chatbot to Zalo OA: the setup in order

You connect an AI chatbot to Zalo OA through an app registered on the Zalo developer platform: Zalo sends each new message to your server, the AI drafts a reply, and your server sends it back through the OA. Before any code you need a verified OA, admin access and a clear rule for when a person takes over.

02 — Short answers

Short answer

What do I need before connecting an AI chatbot to Zalo OA?

Short answer
A Zalo Official Account in your company's name with the verification Zalo requires for API access, an admin who can approve a developer app, and a list of the questions the bot should and should not answer.
How we do it
This is the order we follow on an AI audit: accounts and access first, then the question list, then the build.
Limits
Zalo sets the verification and API access rules and can change them. We check the current conditions for your OA type on the audit before promising a launch date.

Can I build a Zalo chatbot without a developer?

Short answer
For fixed buttons and keyword replies, the tools inside Zalo OA or a ready-made chatbot service are often enough. An AI chatbot that reads your price list, books appointments or writes to your CRM needs a server and code that you or a developer maintain.
How we do it
We compare the questions you receive with what a keyword menu can answer; if most need your own data, a custom connection is justified.
Limits
A custom bot has running costs: hosting, AI model usage and someone who updates the answers when your prices or rules change.

How the connection works

A Zalo OA chatbot is a small program on your server that Zalo talks to. When a customer writes to your OA, Zalo sends the message to an address you registered, called a webhook. Your server passes the text to the AI model together with your own data: prices, opening hours, service list or booking slots.

The AI drafts a reply, your server checks it against your rules, and then sends it back through the Zalo OA API. The customer sees the answer in the same chat, under your OA name. Your staff can still open the conversation in the OA inbox and reply by hand.

  • Zalo: delivers messages to your webhook and sends replies from your OA
  • Your server: holds the rules, the data and the access keys
  • AI model: reads the question and drafts the answer
  • Your systems: calendar, CRM or spreadsheet the bot reads from or writes to

Step 1. Check the OA and who owns the access

Start with ownership. The OA should belong to your company, not to a former employee or an agency account. Find out who is the admin and whether the OA has the verification level Zalo asks for API features.

Write down which phone number and personal Zalo account control the OA. Losing that account later can lock you out of the developer app as well.

Verification rules and the API features open to each OA type are set by Zalo. We read the current Zalo documentation for your case instead of relying on memory.

Step 2. Register a developer app and link it to the OA

On the Zalo developer platform you create an app, link it to your OA and request the permissions it needs, for example reading and sending OA messages. The OA admin approves the link.

The app gives you keys. Treat them like passwords: store them on the server, never in a shared document or in the chat with your developer.

Step 3. Set up the webhook and a test path

The webhook is a public HTTPS address on your server that receives events from Zalo: new message, follow, unfollow. Zalo needs to reach it at all times, so it should not run on a laptop.

Before real customers see the bot, test it with staff accounts. Check that the server answers Zalo quickly and that one message never produces two replies.

Step 4. Connect the AI and your data

The bot is only as good as the data it can read. Give it a short, current source: a price sheet, a list of services with durations, a booking calendar. Long PDFs and old brochures produce confident but wrong answers.

Write explicit limits into the rules: what the bot never promises (discounts, medical advice, delivery dates it cannot see), and which words send the chat to a person.

  • One source of truth for prices and hours
  • A list of topics the bot must not answer
  • A short tone guide in Vietnamese and English
  • A log of every reply for review

Step 5. Respect Zalo's messaging rules

An OA cannot message people freely. Replies inside an active conversation are treated differently from messages the OA starts on its own, and notifications by phone number go through ZNS with approved templates and a fee.

Design the bot to answer, not to chase. Reminders and follow-ups that go outside the conversation window are a separate decision with its own cost; see the comparison of OA messages and ZNS.

Rules and fees for OA messages and ZNS change. We confirm the current conditions with the Zalo documentation on the audit.

Step 6. Decide when a person takes over

Every chatbot needs an exit. Typical triggers: the customer asks for a person, the question is about a complaint or a refund, the bot is not sure, or the topic is on the forbidden list.

When the bot hands over, it tells the customer who will answer and roughly when, and it alerts your staff in the channel they actually watch. A hand-off that nobody sees is worse than no bot.

After launch: what to check each week

Read a sample of conversations every week for the first month. Look for questions the bot answered wrongly, questions it should have passed on, and gaps in your price list.

Update the data source rather than adding exceptions to the code. Most fixes are a line in the price sheet or a new rule about what to hand over.

03 — FAQ

Questions readers ask

Is the Zalo developer platform free to use?

Registering an app is part of the platform. Costs come from your OA package, ZNS notifications if you use them, hosting and AI model usage. We list them for your case on the audit.

Can the chatbot use my personal Zalo account instead of an OA?

No. The official API works with Official Accounts. Tools that automate a personal account work outside Zalo's rules and can get the account blocked.

Will customers know they are talking to a bot?

They should. We recommend a short line in the first reply saying that an AI assistant answers and that a person is available on request.

How long does the setup take?

It depends on your OA status, the data the bot needs and the systems it connects to. We give a date after the audit, once access and verification are clear.

04 — Sources

Sources and notes

  1. 01Zalo for DevelopersOfficial documentation for OA API, webhooks and permissions; rules change, check before each project
  2. 02Zalo Official AccountOA management and verification
  3. 03Our AI lead assistant priceOur published prices and terms on this site
05 — Author

Who wrote this

Dmitry DanilovArchitecture · AI · In web since 1998

One of the two founders of Since98. We write about what we set up for clients: what works, what it costs and where the limits are.

About the founders
06 — Articles

Read next

  • AI & Automation · 4 min read

    Zalo OA, ZNS and Bot API

    OA messages, ZNS, Mini Apps and personal Zalo compared: who starts the message, what each needs and where each stops.

  • AI & Automation · 4 min read

    Personal data and AI chatbots

    What personal data an AI chatbot touches, and the consent, storage and deletion decisions to make with a lawyer before launch.

  • AI & Automation · 4 min read

    AI chatbot cost

    What you pay for in an AI chatbot: scope, channels, integrations, hand-off and the monthly running costs.

08

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: