A website chatbot budget needs more than the monthly plan price. It also needs room for preparing source content, checking answers, maintaining policies and handling the conversations that still need a person.<\/p>\n
Start with a simple model: first-month cost = setup work + recurring software and operating costs<\/strong>. For later months, remove the one-off setup work and update the usage assumptions with actual data. The worksheet below helps you do that without inventing a return on investment or assuming that every website visitor becomes a billable conversation.<\/p>\n A predictable software bill can still require regular staff time. Keep these costs separate so you can tell whether a change comes from demand, a plan upgrade or the work needed to keep answers current.<\/p>\n RobiFox’s standard service does not include custom development, consulting or content writing unless separately agreed. If you need outside help with those tasks, add the actual quote rather than treating it as part of the subscription. The service terms<\/a> describe that boundary.<\/p>\n A visitor, a message and a billable conversation are different things.<\/strong> Someone can browse without opening chat. A conversation can contain several messages. The same person can return and begin another conversation.<\/p>\n RobiFox’s published pricing uses conversation credits rather than a charge for every message. For standard text chat, one credit covers one conversation. Refusal-only conversations do not consume that credit. If the assistant has already given a chargeable answer, a later refusal or human takeover does not refund the credit already used.<\/p>\n Human messages during live takeover do not consume AI conversation credits, and the pricing page lists live chat as included without a per-agent fee. Your staff’s time still belongs in your operating budget.<\/p>\n Before modelling voice or other optional modes, confirm their credit rules separately. Also confirm when a long or resumed exchange becomes a new conversation. Do not multiply a message count by a conversation price, or assume one customer can only consume one credit in a month.<\/p>\n The following examples were checked against RobiFox’s pricing page<\/a> on 29 October 2026<\/strong>. They are monthly EUR prices excluding VAT. The final tax-inclusive amount is shown at checkout and depends on the billing details. Check the current page and checkout before buying; these are dated reference figures.<\/p>\n On a small screen, scroll the tables sideways to see every column.<\/p>\nSeparate the provider’s bill from your team’s work<\/h2>\n
\n
Understand the billable unit before estimating usage<\/h2>\n
Use current plan limits, not a generic chatbot price range<\/h2>\n