Answers from approved content
Your team provides information about services, opening hours, terms and common questions. We organise answers and next-step choices; requests without sufficient information go to a member of staff.
Zalo OA chatbots
Zalo chatbots for answers and enquiries.
Help customers using Zalo in Vietnam find approved answers, explain their needs and reach the right member of your team.
Sample visitorCan the website include an enquiry form?
Answer from approved contentIncluded in the business website scope. Specific requirements need confirmation.
Service website · one language · enquiry form
Staff handoff
A needs summary for the consulting team to review and follow up.
Illustration; no notification is sentScope to agree
- 01A conversation with a clear input and next step
- 02Review your Zalo OA before connecting
- 03Choose the channel your customers use
Start with one question set, agreed reply languages and one enquiry flow. We review your OA, administration rights, content and existing tools before choosing a scripted chatbot or an AI-assisted approach. Answers and staff handoff messages need review in each supported language. A live connection is confirmed separately after that review.
AT A GLANCE
Handle incoming messages, use approved answers and hand enquiries to staff.
- Start with
- Your messaging channel, common questions and the staff handling enquiries.
- Deliverable
- A tested conversation flow and operating guidance.
- Agree first
- Integration access, scope and platform costs.
Enquiries
A conversation with a clear input and next step
Choose the questions and details to handle first.
Capture the needs that matter
Agree what information is needed to handle the request, how customers agree to provide it and where it belongs. Include only questions that serve the defined workflow.
A handoff with context
Define when the bot stops, which team receives the request and the summary to pass on. Staff respond according to your working hours; the bot does not replace decisions that require approval.
INTERACTIVE DEMO · SAMPLE DATA
Try a conversation with a staff handoff
Three fixed steps: ask about the service, capture sample needs and prepare a summary for staff.
This demo uses sample data without a live Zalo or CRM connection. Actions only update the sample in this tab; no data is sent to an external service. Use Reset or reload the page to start again.
- Question
- Sample needs
- Staff handoff
What happens
Completed steps 0/3- Choose the sample question to begin.
CURRENT RESULT
No handoff summary yet.
Platform references: Zalo OA — applications and permissions · Menus and chatbots.
Zalo OA requirements
Review your Zalo OA before connecting
Check the account, permissions and tools before choosing an integration.
Account ownership and access
Identify the OA owner, authorised administrators and tools already in use. Personal passwords are not requested in the enquiry form; required access follows an agreed process.
Built-in flows or a custom connection
Zalo OA offers menu and scripted chatbot tools. For a custom system connection, review the Zalo App, OA OpenAPI permissions, webhook and server environment before confirming the scope.
Messaging conditions and platform costs
Check the features, messaging conditions and plan applying to the OA when implementation starts. Applicable OA plan and paid-feature charges, hosting and AI usage are separate from implementation; unlimited messaging is not assumed.
Choose a channel
Choose the channel your customers use
Choose Zalo, Facebook or Telegram around the channels your customers use.
Zalo OA as the primary channel
Organise conversations on the business OA you already manage. Start with one small flow and test replies and staff handoff before adding more scenarios.
Facebook Messenger as a separate scope
If customers mainly use Facebook, we review Page administration rights and the connection options in your existing tools. Approved content may be reused, while access and implementation need their own checks.
Telegram for a defined workflow
A Telegram bot can be considered where customers or staff already use the channel. Define the purpose, recipients and access separately; one connection is not assumed to work across every platform.
Handover
A flow your team can check and maintain
Test common scenarios and brief the staff responsible.
Test expected and out-of-scope questions
Use approved test data to check answers, missing information, repeated requests and staff handoff. Where AI is involved, assess a sample question set and limit the sources used for answers.
Business control of access and content
Hand over the conversation map, approved content, agreed configuration and update guidance. Identify account owners, credential storage and responsibilities when staff change.
Separate setup, operation and expansion
The quote records channels, flows, languages, connections and acceptance checks. Content maintenance, incident support and new CRM links have separate scopes.
HOW WE WORK
Clarity at every step.
Define the conversation
Choose the question set, needs to capture and points where staff must take over.
Approve content and access
Review answers, handoff, data and account requirements before connecting.
Configure and test
Build in the agreed environment and check errors, out-of-scope questions and repeated requests.
Hand over and review
Provide update guidance, administration access and operating responsibilities. Agree the follow-up work.
PRICED BY SCOPE
A quote for your workflow.
Start with one workflow, then confirm the work and cost before implementation.
Request a scoped quoteWhat determines the cost
- Messaging channels, conversation flows, answer material, staff handover and systems to connect.
- Separate development, integration and testing from platform, hosting, AI usage where applicable and ongoing maintenance fees.
- The FAQ pilot price applies only to its listed scope; Zalo OA or CRM integration is not automatically included.
FAQ
Before we begin.
A few useful answers to help define the right scope.
Do I need a Zalo Official Account?
This service focuses on chatbots for Zalo OA. We review the OA, administration rights and existing tools before confirming implementation. A personal Zalo account is not treated as an equivalent replacement.
Does the chatbot have to use AI?
No. Menus and scripted answers often cover stable information. AI is considered for a specific purpose with approved sources and a staff handoff when there is insufficient evidence.
Can it decide prices or accept orders by itself?
Only within approved rules and permissions. Exceptions, service commitments and actions that change records need defined checks; staff confirmation can remain part of the process.
Does the demo send real Zalo messages?
No. It uses a fixed scenario in browser memory and sends nothing to Zalo or your staff. Reloading or switching language starts it again.
How is the work priced?
By channel, flows, languages, connections and content volume. Implementation is separate from OA plans, paid features, hosting, AI usage and support where needed. A Zalo-connected chatbot does not automatically have the same scope as the FAQ AI pilot.
Can we connect it to a CRM later?
We can assess this once the CRM, access and required data are known. Field mapping, duplicate handling, assignment and error reporting need agreement before a connection is confirmed.
LET’S DEFINE THE REQUIREMENTS
Start with one conversation.
Tell us which channel your customers use, the questions they ask and when staff should take over.