Epos Now saves 60,000 human labor hours per month and achieves 70% automated resolution rate with Ada's AI agent Sidekick
Epos Now's B2B customer support was strained by complexity across dozens of verticals, with customers demanding high-touch, multi-step guidance that legacy IVR and scripted chatbots could not deliver. Support channels operated in silos with different technologies and no unified knowledge base, producing inconsistent customer experiences.
Epos Now's IVR system was pre-configured around scripted routing and failed to deliver the quality of experience they wanted, with customers sometimes ending up with the wrong agent and experiencing longer wait times. Scripting responses across a diverse customer base quickly led to diminishing returns.
source quote
source quote
source quote
source quote
source quote
source quote
Sidekick now automates 70% of support demand across all channels, saves 60,000 human labor hours per month, increased CSAT by 30% on messaging and 15% on voice, and call demand dropped by 22% to 25%, while customer service teams delivered 40% year-over-year revenue growth.
Show all 8 reported metrics
Compare to your context
Tell us your scale, team, and constraints. We'll show what changes at your size, what fails at your scale, and whether this case is a fit, needs adaptation, or won't scale to you. Free demo, no signup.
Frequently asked questions
What did this team achieve with this AI workflow?
Sidekick now automates 70% of support demand across all channels, saves 60,000 human labor hours per month, increased CSAT by 30% on messaging and 15% on voice, and call demand dropped by 22% to 25%, while customer se…
What tools did this team use?
Ada, Sidekick, IVR.
What results were reported?
Human labor hours saved per month: 60,000; CSAT increase on messaging: 30%; CSAT increase on phone: 15%; Automated resolution rate (combined channels): 70% (source-reported, not independently verified).
What failed first in this deployment?
Epos Now's IVR system was pre-configured around scripted routing and failed to deliver the quality of experience they wanted, with customers sometimes ending up with the wrong agent and experiencing longer wait times.
How is this customer support AI workflow structured?
Customer inquiry arrives → Knowledge base retrieval → AI-guided resolution → Pre-handoff case documentation → Human agent review → Team monitors and refines AI.
Related customer support cases
Now compare it to your context
This case is one data point. Whether its pattern fits you depends on your volumes, your stack, and your exception load — that comparison is the step no case study can do for you.