Before pricing a chatbot, list five questions you want it to answer. If they're all about office hours, directions and contact details, clearer website pages may solve the problem with less maintenance.
If you still need a conversational interface, its cost depends on the sources it reads, the actions it can take and the work needed to keep it accurate.
Start with a useful, narrow purpose
Keep office hours, contact details and quote-request links available outside the chatbot so visitors can reach them directly.
For an agency, route policy-specific questions to an authorized person and the approved service channels. Do not present generated text as a coverage determination or bind insurance through an unreviewed conversational flow.
Separate the cost categories
Ask for a proposal that distinguishes the interface, approved content preparation, integrations, testing and ongoing support. Subscription and usage charges belong in a separate operating estimate. Identify what counts as a billed conversation, resolution or model call in the selected vendor's current terms.
Custom development is quoted by scope. Ask for a separate estimate of monthly usage and maintenance.
Test the content and the fallback
Build a review set containing ordinary questions, ambiguous requests, outdated details and questions the system should hand off. Record the source behind each answer. Test whether the visitor can reach a person when the system cannot help.
Someone must own content updates, access and incident review. If office hours change on the website, the chatbot should not continue answering from a forgotten copy.
Evaluate before expanding
Measure whether the tool helps visitors complete an appropriate task, how often staff must correct it and whether its maintenance is justified.
Our website scope discussion can establish whether this feature is needed at all.
