A PRACTICAL GUIDE

Price a chatbot around the actual scope.

Budget for a chatbot or automation pilot for your business in Vietnam. Agree the channels, languages and staff handover first, then separate setup fees from platform and AI usage costs.

Discuss your requirements
FAQ · Sample website

I would like to speak to someone.

Please leave your request for a member of staff.

Hand over to staff
Build / Usage / CareThree separate budget parts
ILLUSTRATIVE STRUCTURE

THE FAQ PILOT SCOPE

Website FAQ chatbot pilot

From3,000,000 VND/ pilot · one time
Estimate your cost →
  • One website FAQ bot, one language and up to 50 approved questions.
  • One source collection and a route for referring questions to a person.
  • Sample-question testing, error review and usage guidance.

Model/API, hosting and operating fees are separate. Zalo OA, multiple channels, CRM and other workflows need a separate quote.

ILLUSTRATIVE ASSUMPTIONS · PER MONTH

From usage to model cost.

This example assumes one model call per answer, averaging 1,000 input tokens and 200 output tokens. These are not actual usage figures or a provider quote.

I is the price per million input tokens; O is the price per million output tokens. Substitute checked rates for the selected model and plan, in the same currency.

1,000 conversations × 4 answers
4,000 calls
4,000 calls × 1,000 input tokens
4 million tokens
4,000 calls × 200 output tokens
0.8 million tokens
Illustrative model cost/month
4 × I + 0.8 × O

This usage cost is separate from the one-time FAQ pilot implementation fee above. Hosting, storage, messaging channels, additional tools and support are excluded.

Long conversation history or retrieved documents can increase input tokens. Retries and additional model steps increase call counts; they are outside these assumptions and must be budgeted for the actual workflow.

Cost depends on the amount and complexity of the work. A smaller scope may reduce the total; we confirm this after reviewing your requirements. Work fees exclude any applicable taxes; domains, hosting, paid tools/APIs and advertising are separate. The final quote confirms scope, total, taxes and timing before work begins.

01 / GUIDE

The scope determines the work.

Channels & access

Identify the website or messaging platform, account ownership and available permissions/APIs. Zalo OA and CRM connections need separate assessment.

Answer sources

Approved material, languages, update ownership and unanswered questions. Cleaning content or supporting multiple document types may be additional work.

Actions & testing

Answering FAQs differs from writing to a CRM, creating orders or processing documents. Each action needs suitable permissions, failure cases and acceptance checks.

02 / GUIDE

Separate three parts of the budget.

One-time implementation

Analysis, setup, agreed integrations, testing and handover. Specify flows, data sources and revision rounds in the proposal.

Platform & usage

Hosting, messaging platforms and AI usage may have separate charges. Check terms and prices when scoping, and agree account ownership and budget limits.

Maintenance & changes

Content updates, error monitoring and new features need an owner. Define support timing, included work and chargeable changes.

03 / GUIDE

Use a pilot to decide what comes next.

A sample question set

Include common questions, alternative wording and out-of-scope requests. The content owner approves expected answers before testing.

Staff handover

Check missing information, requests for a person and system failures. Agree which details are handed over and who receives them.

Criteria for continuing

Record issues and work staff still need to do. Add channels or workflows once the small pilot meets agreed criteria.

FAQ

Before deciding.

Does the FAQ price include a Zalo bot?

No. The FAQ price covers the stated website-chatbot scope. Zalo bots, CRM work and other integrations are assessed separately.

Can every answer be guaranteed correct?

No. Limit the content sources, test the system, handle out-of-scope questions and use human review for consequential work.

LET’S DEFINE THE REQUIREMENTS

Discuss your bot or automation.

Describe the task, the channels you use and the systems it needs to connect to.

Send your requirements