# Website chatbot — comparable quote request

Website: [URL]
Project contact and operating owner: [name/role]
Approved sources and update frequency: [list]
Languages: [list]
Expected conversations per month: [estimate and basis]
Required fallback: [contact link / ticket / staffed live chat]

## Reference scope
A text chatbot answers from approved public sources, points to the supporting source, handles an unanswered question and provides the agreed contact route. Private customer data, write actions, voice, additional channels and a native helpdesk are excluded unless listed here: [details].

Please provide a platform-configuration proposal and/or a custom-development proposal as appropriate. Name the architecture, plan levels, ongoing providers and required accounts. Explain which written requirement justifies custom work.

## Quote separately
1. Setup, including content preparation, widget installation and the included checks.
2. Subscriptions and who pays them, including plan limits and optional add-ons.
3. Model usage, hosting, storage, retrieval and expected overages.
4. Internal work the client must provide.
5. Maintenance tasks, availability, response arrangements and fees.
6. Optional integrations, changes and work outside the base scope.
7. Marketplace fees or taxes if applicable.
8. Handover, exit and migration work.

## Questions for the provider
- Which sources and changes are included? How are conflicts and unanswered questions handled?
- What does the human fallback actually do, and who receives the context?
- If private data is included, how are identity and permissions checked?
- If writes are included, which approval and destination-system checks are required?
- Who controls administrator access and billing? Which code, configurations, exports and documents are handed over under this proposal?
- Can another authorised person deploy, update and recover the service from the delivered instructions?
- Which fixes are included after acceptance, and which are new work?
- How are usage limits, provider errors, monitoring, backups and restoration handled?

## Acceptance and handover
Agree expected answers, fallback behaviour, source changes, device/language checks and recovery evidence before work starts. Use the accompanying acceptance-checklist.csv; add project-specific cases. Keep test results and evidence fields empty until the checks run.

For transactional work, a successful mocked conversation does not prove the destination action occurred. Specify the controlled accounts and records used to verify it.

## Response requested
Return one-off and recurring costs separately, with assumptions, exclusions, delivery dependencies, scope of acceptance, ongoing owner and change procedure. Do not replace this breakdown with an unspecified all-inclusive price.

Prepared with the SmartCreatorHub guide:
https://www.smartcreatorhub.blog/en/build-vs-buy-ai-chatbot