Request source and destination
Choose one source, such as a website form or an authorised channel. Record which event creates a request and which system holds the master record; support for every CRM is not assumed.
CRM automation
CRM automation: from enquiry to follow-up.
Give your team in Vietnam a clear way to receive, assign and follow up enquiries from local and international customers.
Intake
Simulated form
Check duplicates
DEMO-104
Assign
Consulting team
New
DEMO-104Service websiteConsulting team
In progress
Awaiting staff action
Completed
Does not mean a sale
Repeat event ID: keep the existing record.
Scope to agree
- 01Define the data before automating
- 02Assign work and track its status
- 03A connection your team can control
Start with your existing process and one flow worth improving. Identify the source, destination CRM or management board, permitted data and staff roles, including whether a customer’s preferred language affects assignment. Connection feasibility must be checked against the actual systems before implementation is confirmed.
AT A GLANCE
Bring enquiries into your CRM, check duplicates and assign the right person.
- Start with
- Enquiry sources, your CRM and the current workflow.
- Deliverable
- A tested workflow with processing rules and logs.
- Agree first
- Data fields, access and error handling.
Input data
Define the data before automating
Define the source, required fields and how to recognise repeated requests.
Fields and validation rules
Agree required information, formats, allowed values and handling of missing fields. Map each source field to its destination without inferring information the customer has not supplied.
Identify repeated requests
Choose an event identifier or duplicate rule that fits the process. Replaying the same event should not add another record; two different needs from one customer are not automatically duplicates.
INTERACTIVE DEMO · SAMPLE DATA
Try intake, duplicate handling and assignment
Use sample request DEMO-104 to see what happens with valid, repeated or incomplete data.
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.
- Validate
- Deduplicate
- Assign
- Status
What happens
Record count 0- Receive sample request DEMO-104 or try the missing-data check.
CURRENT RESULT
0 records created.
Assignment & status
Assign work and track its status
Assign the right person, track progress and handle connection errors.
Assignment by approved rules
Define the receiving team by service, area or other permitted criteria. Requests without a suitable match go to a clear review queue for staff to decide.
Statuses and confirmation steps
Agree each status, who may change it and the conditions for moving forward. A created record is different from a staff conversation or a sale; reporting should distinguish these milestones.
Connection errors and retries
Record completed operations, failures and uncertain outcomes. Retry only under rules that avoid duplicate work; cases needing verification go to an owner instead of being reported as successful.
Testing & handover
A connection your team can control
Test duplicate requests, missing data and connection failures before launch.
Access and test data
Review the supported API or connection method, permissions and test environment. Use sample data for checks, and agree where real data is stored, how long it is kept and who can access it.
Checks across the complete flow
Test valid requests, missing fields, repeated events, assignment, status changes and destination errors. Reconcile input records with the results before enabling the live process.
Handover and running costs
Hand over field mappings, rules, error-handling guidance and the agreed assets. Implementation is quoted for the defined scope; CRM licences, APIs, hosting and ongoing support are listed separately.
HOW WE WORK
Clarity at every step.
Map the current process
Choose one source, destination, responsible team and the point causing delay or errors.
Approve data and rules
Agree field mappings, duplicate keys, assignment, statuses and access.
Connect and test
Build the approved flow and test success, invalid data, repeated requests and connection failures.
Launch and hand over
Review results within the agreed trial scope and hand over guidance, including how to stop or restore the flow.
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
- Enquiry sources, data fields, duplicate rules, assignment and the integration options of your current CRM.
- 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 we need to replace our current CRM?
Not automatically. We check whether the current system supports a suitable connection. Missing access, APIs or features are documented with options before implementation starts.
Which CRMs have you already integrated?
This page describes the working approach, not a list of live integrations. Send the system name, version or plan and the workflow you need so we can check actual feasibility.
Will CRM automation increase sales?
We do not promise sales or customer counts. Implementation is assessed through intake data, record accuracy, assignment and status handling; commercial results also depend on your offer and follow-up.
Does the demo write to a real system?
No. It uses one sample record in browser memory, needs no personal information and connects to no CRM. Try a valid request, duplicate or missing data, then reset it.
Does the AI price cover CRM automation?
Not automatically. CRM work is quoted separately by sources, destination systems, rules, volume and access. Platform and running costs appear separately; an FAQ pilot price is not an integration quote.
What should we prepare?
Share the system name, current workflow, field list and a redacted example. Explain who receives requests, the statuses you need and the problem you want to solve. Passwords and real customer records are not needed for the initial enquiry.
LET’S DEFINE THE REQUIREMENTS
Start with your enquiry workflow.
Describe your enquiry sources, existing CRM and the steps handled manually. We will help choose one workflow to implement first.