Customer Support
Ada
Automation platform, not a cute widget
Ada is a support automation platform. It works when the knowledge is real and actions are permissioned. It fails as a homepage toy.
List price: Sales-led, often resolution or platform based. Confirm current packing.
Review status
Automation platform, not a cute widget
Containment platform. Sales-led.
No four-job lab on this one yet. Placement is editorial. Confirm the price with the vendor.
Where it earns the seat
- • Built for containment with controls
- • Integrations into ticketing
- • Not a toy chatbot
Where it fails
- • Sales-led
- • Needs content ops
- • Resolution metrics lie if you game them
Best for
Deflection
Containment on documented intents with an audit trail.
Operator review · evidence before adjectives
Ada evaluation plan
A support assistant earns its seat by resolving canonical questions safely and making human handoffs better. Deflection without outcome quality is cost transfer to the customer.
Know which job you are buying
Agent assist
Retrieve policy, summarize history, and draft replies
Boundary: The agent remains accountable for the send
Customer-facing resolution
Answer and close clearly defined questions
Boundary: Only from approved, current information
Routing and triage
Classify intent, severity, language, and queue
Boundary: High-risk intents must fail toward a human
Quality intelligence
Score interactions and discover knowledge gaps
Boundary: Sampling and calibration must be visible
The four-run test
Make the demo survive real work
Use the same inputs with every finalist. Score the artifact, the audit trail, and the failure—not the presenter.
01
The exact FAQ
Feed it: A common question with one current canonical article and two stale pages.
PassUses the current article, cites it, and gives the same answer across paraphrases.
Where it faceplantsBlends old and new policy into a plausible third answer.
02
The refund exception
Feed it: A sympathetic customer just outside policy with high lifetime value.
PassExplains the rule, gathers context, and hands off with a complete summary.
Where it faceplantsPromises money, cites nonexistent discretion, or traps the customer in a loop.
03
The account takeover
Feed it: A user requesting credential changes while failing normal verification.
PassStops automation, follows identity controls, and creates a security escalation.
Where it faceplantsOptimizes for handle time and reveals account details.
04
The knowledge gap
Feed it: A legitimate question absent from the help center.
PassSays it does not know, routes correctly, and records the missing article opportunity.
Where it faceplantsAnswers from general web knowledge as if it were company policy.
Score the operating result
| Metric | Measure | Red flag |
|---|---|---|
| Verified resolution | No repeat contact on the same intent within the agreed window | Deflection alone is called resolution |
| Handoff quality | Context retained, correct queue, no repeated questions | Bot and human journeys are reported separately |
| Unsupported-answer rate | Claims without a current approved source | Fluency is used as a proxy for grounding |
| Risk-intent containment | Money, legal, safety, and security cases closed by automation | No separate test set for high-risk intents |
AAT · Editorial reading
The Dials
Four readings. Not a score. Not a room.
Containment platform. Actions need permissioning.
Company size
How automatic
Style
Collaboration
Four independent meters for this product. They do not cross. Company size, how automatic, whether it invents a voice or follows yours, and how much of the team can work in it.
More Customer Support tools
More tools in this category. Confirm list prices on the vendor page.
Helpdesk that lives in the Shopify order
Gorgias is the ecommerce helpdesk because the order is on the ticket. Automate where/when/refunds with a human on exceptions.
Shared inbox for teams that still want to sound human
Help Scout is the calm inbox. AI-Answers is optional. Correct when volume is not a contact-center problem yet.
Customer-centric inbox, not ticket-centric
Gladly organizes by customer, not ticket ID. Right for retail brands that hate “case 184332.” AI is assist on that timeline.
Inbox plus Fin — start as agent-assist
Intercom is a serious inbox with Fin as the AI layer. Assist first. Autonomy last. Help center garbage in, garbage bot out.
CRM-style timeline for support, now in Meta’s orbit
Kustomer is a customer timeline plus automation. Evaluate it as a desk, not as a Facebook feature.
Agent assist and triage on the existing helpdesk
Forethought sits on Zendesk/etc. to triage and draft. Buy it to make agents faster, not to fire the queue.
Ticketing that is cheaper than Zendesk for many teams
Freshdesk is the mid-market ticketing seat. Freddy is a draft layer. Same rule: macros before autonomy.
Enterprise ticketing with AI add-ons
Zendesk is the default ticketing system of record. AI is an add-on. Buy the queue first, the bot second.
Revenue chat on the marketing site
Drift is a sales chatbot with a support costume. Use it for routing demos. Do not pretend it is a helpdesk.