What is a good chatbot ROI?
A healthy support chatbot typically returns 3x to 10x its annual cost in deflected labor within the first year. Anything above 100% 12-month ROI means the chatbot pays for itself inside the year. Vendors often quote higher numbers, but a conservative 25-40% deflection rate on tier-1 tickets at a fully-loaded agent cost is the realistic baseline.
How accurate is this calculator?
This calculator uses a simple, transparent model: deflected tickets times handle time times agent cost, minus chatbot subscription. It is meant for directional estimates and quick business cases, not procurement-grade forecasts. Real-world results swing on intent coverage, training data quality, escalation rates, and onboarding effort - run sensitivity analysis with low, medium, and high deflection assumptions.
What deflection rate should I assume?
For a well-tuned chatbot on a knowledge base, 20-40% deflection of inbound tickets is realistic. Top-quartile deployments hit 50-60%. Use 25% as a conservative starting point if you have not piloted yet, 35% if you have a clean help center and clear FAQs, and 50%+ only if you have validated it with a pilot.
How do I calculate fully-loaded agent cost?
Fully-loaded cost includes salary, benefits, taxes, software seats, training, and overhead - typically 1.25x to 1.4x base salary. Divide annual fully-loaded cost by 2,080 hours per year for the hourly rate. A US support agent at $50,000 base usually lands around $30-40 fully-loaded per hour. Use your finance team's loaded rate if you have one.
Should I include chatbot setup and integration costs?
Yes, for year-one ROI. Add one-time setup, integration, and training-data costs to the chatbot subscription line, or amortize them over 12 months. This calculator assumes a flat monthly subscription, so for a more conservative number bump the monthly figure to absorb implementation cost in the first year.