Manage and match customer references at scale
Identify and act on expansion signals
Set up automated referral programs
Capture proof from conversations with AI
Turn loyal customers into brand champions
Generate reviews and amplify customer voice
AI-native journeys that accelerate time-to-value
Success plans and next-best actions
Streamline the creation of any customer facing document

How to use AI in customer success comes down to evidence. We graded 15 use cases, from onboarding to expansion, on the proof behind each one. One earns an A, nine a B and five a C. The only A was borrowed from support agents.
Base AI's own customer stories sit on the same scale, and every one is a C. Pick two or three use cases, and run each grade differently.
To use AI in customer success, pick two or three use cases where analyst or independent support already exists, such as account briefs, health scores and QBR drafts. Then run one customer-facing use case as a measured experiment with a comparison group. Grade every candidate on its evidence before you buy.
Why grade at all? A July 2026 Gartner analysis of 432 AI use cases in customer service, as reported by CX Dive, found about one in four produced a return. Another one in four lost money. In 42% of cases, support leaders didn't know what value they got.
Customer success may be running the same experiment. For where your team sits overall, see our guide to AI for customer success and its four maturity levels.
Each use case gets one grade, based on the strongest public evidence for the use case itself, not for any product.
A C doesn't mean a use case fails. It means nobody independent has shown in public that it works. Customer stories are a C by default, because the vendor picks the customer and writes the story.
The A comes from an NBER working paper by Brynjolfsson, Li and Raymond, covering an AI assistant rolled out to 5,179 customer support agents. Issues resolved per hour rose 14% on average and 34% for novice and low-skilled agents, with minimal impact on experienced agents.
Those were support agents, not CSMs. So start with newer CSMs or a pooled team, and keep a person sending every reply. The A doesn't transfer to a customer-facing assistant, because it measured a person with an assistant.
Base AI's clearest quiet-account example isn't AI. At Phenom, the story credits analytics dashboards that show which companies have gone quiet. Like every customer story here, it is a C.
In advocacy, two of three use cases have only vendor numbers:
In expansion, signals have analyst backing and automated campaigns do not:
The strongest evidence for AI in customer success is for AI that helps a person. In an independent study of 5,179 support agents (NBER, 2023), those given an AI assistant resolved 14% more issues per hour. Forrester lists preparation work as bringing measurable benefits quickly. No independent controlled study we found measures customer-facing or automated uses in customer success.
Autonomy has little evidence, and one likely reason is that few teams run it. Velaris, which sells a CS platform, surveyed 394 CS professionals for its 2026 report and found: "Only 3% of teams report having deployed AI that can operate with full autonomy".
Here is the uncomfortable part. Prep work saves CSM time, and saved time doesn't reach a customer by itself. You can't avoid customer-facing uses. You can stop treating them as proven.
Bain's December 2025 report is blunt: "Pick two or three processes to deliver the greatest impact." The grade tells you how to run each pick.
Check the data first. A health score built on half your data is a guess, and our scorecard for AI tools for customer success starts there.
A sensible first mix: one B that gives time back, like kickoff briefs, and one C that touches customers, like onboarding nudges, with a holdout. The B buys the time. The C produces the evidence.
Every C here is a program Base AI runs, which is why we graded our own stories as hard as anyone's. On the AI Customer Growth platform, every program comes staffed: an AI teammate decides the next step for each account and takes it. Run it with a holdout, and grade it yourself.
AI can be used at every stage of the customer lifecycle: onboarding workspaces built from the contract, weekly task nudges and kickoff briefs; adoption signals, suggested answers and customer-facing assistants; health scores, quiet-account alerts and QBR drafts; advocate readiness, story mining and reference matching; and upgrade signals, expansion plan drafts and usage-triggered upsell campaigns.
Independent proof is thin. The only measured result with a comparison group comes from customer support: in an NBER study of 5,179 agents, an AI assistant raised issues resolved per hour by 14%, and by 34% for novices, with minimal impact on experienced agents. One Forrester post supports preparation and signal use cases, without published figures. For automated uses such as nudges and upsell campaigns, only vendors publish numbers.
AI agents can take the action after a signal: sending weekly task nudges, building onboarding workspaces from the contract or launching upsell campaigns when usage crosses a threshold. The evidence for these automated uses comes only from vendors. Velaris, which sells a CS platform, surveyed 394 CS professionals and found only 3% of teams report deploying AI with full autonomy.
Start with two or three use cases, as Bain advises in its December 2025 report on customer success. A sensible first mix sits in one lifecycle stage: one analyst-backed use case that gives CSMs time back, such as kickoff briefs, and one customer-facing use case, such as onboarding nudges, run against a holdout group so it produces your own evidence.
AI health scores that combine usage, ticket text and call sentiment have analyst backing as a way to decide which accounts to focus on. The sources behind that backing publish no figures on how well they predict churn. Test one before trusting it: score last year's churned and renewed accounts blind, and check whether the churned ones land in the bottom quartile.
Match the test to the use case's evidence grade. For a use case with independent proof, one before-and-after metric is enough. For one with analyst backing, record the metric for a month before switching it on. For one backed only by vendor claims, hold out a comparison group, pick one customer outcome metric and set a kill date. Name the 90-day number first.
Building and scaling your advocacy program is easy when you can manage campaigns, rewards, track, and report - all within one AI platform.
Book a demoThe AI Customer Growth platform.