YNAB replaced a basic chatbot with Forethought and saw deflection jump from 25% to 70%
YNAB's legacy chatbot relied on rigid menus and decision trees, making it hard for users to get correct answers in their own words. Deflection was stuck at 25%, meaning three out of four users required human intervention, and the system could not scale to support YNAB's growth ambitions.
The legacy chatbot could not understand natural language context — it could not distinguish whether a user meant their bank account or their YNAB account — and if users chose the wrong menu category there was no easy way to backtrack.
After deploying Forethought Solve in October 2024, YNAB's ticket deflection rate rose from 25% to over 70% — a 45% improvement over the legacy chatbot — and monthly chat conversations tripled to about 12,000 without requiring additional headcount.
Show all 5 reported metrics
Frequently asked questions
What did this team achieve with this AI workflow?
After deploying Forethought Solve in October 2024, YNAB's ticket deflection rate rose from 25% to over 70% — a 45% improvement over the legacy chatbot — and monthly chat conversations tripled to about 12,000 without r…
What tools did this team use?
Forethought, Solve Agent, Assist Agent, Discover Agent.
What results were reported?
Ticket deflection rate (post): 70%; Ticket deflection rate (pre): 25%; Improvement over legacy chatbot: 45%; Monthly chat conversation volume increase: 3x (source-reported, not independently verified).
What failed first in this deployment?
The legacy chatbot could not understand natural language context — it could not distinguish whether a user meant their bank account or their YNAB account — and if users chose the wrong menu category there was no easy…
How is this customer support AI workflow structured?
Customer submits chat or email → Agentic AI understands intent → AI asks follow-up if needed → Route to human agent → Assist Agent supports humans → Discover Agent surfaces gaps.