← Articles Oct 30, 2026

Customer Success AI Agent Templates: Five Prompts for Renewals and Expansion

Most churn warnings sit in calls nobody rereads before the renewal. These five agent templates surface them while there is still time to act.

Customer Success AI Agent Templates: Five Prompts for Renewals and Expansion

Customer success AI agent templates are reusable instructions that tell an agent when to run, which accounts to read, what to look for, and how to report back. The five below cover the sales-to-CS handoff, renewal risk, champion changes, expansion signals, and QBR prep. Each one is ready to paste, with its trigger, inputs, and what good output looks like.

If your renewal reviews still start with a CSM scrolling through six months of call notes the week before the date, you are not alone. The warning signs were usually there months earlier. They were sitting in calls nobody had time to reread.

Why do account teams miss churn signals until it is too late?

Account teams miss churn signals because the evidence is spread across dozens of calls, email threads, and CRM fields, and nobody reads all of it on a regular cadence. A CSM with a full book reviews the accounts that are loud, not the ones that are quietly drifting.

The cost of that gap is well documented. Research by Frederick Reichheld of Bain, summarized in Harvard Business Review in 2014, found that increasing customer retention rates by 5% increases profits by 25% to 95%. And the signals are often silent until the end. Staircase AI’s State of Customer Churn report, built on more than 100,000 customer communications from mid 2022 to mid 2023, found that 51% of churning customers sent a cancellation notice without warning, and that only 33% of churned accounts were multithreaded compared with 64% of renewing accounts.

An agent does not get tired of reading. Give it a clear scope, criteria, required evidence, and a fixed output, and it reviews every account every week. The same structure powers our sales AI agent templates for open deals. The five below apply it after the contract is signed.

Template 1: How do you automate the sales-to-CS handoff?

What it does. Writes a handoff brief the moment a deal closes, so the account team starts from what the customer was actually promised instead of a two-line CRM note.

When it runs. On a deal stage change to Closed Won.

Instructions.

A deal has just moved to Closed Won. Read every call, email, and CRM
field on this deal. Write a handoff brief for the account team with:
1. The business problem the customer bought to solve, in their words.
2. The success criteria they agreed to, with any dates.
3. Every commitment made during the sales cycle: integrations,
   features, pilot terms, pricing exceptions, and timelines. Quote the
   call or email and give the date for each one.
4. Stakeholders: name, role, and how engaged they were.
5. Risks the sales team already saw, with evidence.
Do not include anything you cannot point to in a call or email. Keep
it under 400 words.

Inputs. Call transcripts and attendees for the whole deal, emails, and CRM fields for stage, amount, and owner.

Good output. A CSM can run the kickoff call without asking the AE a single question. In the deals we see, the commitments that get lost in handoff cluster around data integrations, enabling specific features, and the terms of a trial or pilot, which is why item three asks for a quote and a date on each one.

Template 2: How do you run a weekly renewal risk review?

What it does. Ranks every account renewing in the next 120 days by risk, and shows the evidence behind each rating.

When it runs. Weekly, on Monday morning, before the account team meeting.

Instructions.

Review every account with a renewal date in the next 120 days. For
each one, check the last 90 days of calls and emails for: fewer
meetings than the prior 90 days, negative sentiment about value or
results, a champion or decision maker who has gone quiet or left,
unresolved issues raised more than once, and mentions of budget cuts,
reorgs, or competitors. Rate each account High, Medium, or Low risk.
Return a table of High and Medium accounts only: account, renewal
date, owner, risk, the top reason, and a quote or date that proves it.
Cap the table at 10 rows, highest risk first. Then list what changed
since last week's run.

Inputs. Post-sale call transcripts and attendees, emails, and CRM fields for renewal date and account owner.

Good output. The team meeting opens on the three accounts that need an executive sponsor this week, not on a round of status updates. The “what changed” line matters most, because it shows whether last week’s save plays worked.

Template 3: How do you catch a champion change before it costs the renewal?

What it does. Flags accounts where the person who bought, or the person who uses the product most, has left, changed role, or stopped showing up.

When it runs. Weekly, plus after any customer call where a new attendee appears.

Instructions.

For every live account, compare who attended calls and replied to
emails in the last 60 days with the 60 days before that. Flag any
account where:
- the champion or economic buyer has not appeared in 45 days,
- someone mentions that a key contact is leaving, has left, or has a
  new role,
- only one customer contact has been active in the last 60 days.
For each flag, give the account, the person, the evidence with a
date, and one suggested next step, such as who to introduce next.
Skip accounts with no flags. Cap the list at 8.

Inputs. Call attendees and transcripts, email participants, and the stakeholder or contact roles in your CRM.

Good output. A short list the account owner can act on the same day. The single-contact rule matters most, because an account that depends on one person can end the day that person leaves, and a weekly flag gives the owner time to build a second relationship.

Template 4: How do you find expansion opportunities in customer calls?

What it does. Surfaces upsell and cross-sell signals that customers mention in passing, then hands them to the right owner.

When it runs. After every customer call, with a monthly roll-up.

Instructions.

Read this customer call. Note any expansion signal: new teams or
regions that want access, hiring plans that add users, a problem the
customer described that another product or tier solves, or a request
for a feature on a higher plan. For each signal, quote the line, name
who said it, and say which offer it points to. If there is no clear
signal, return "No expansion signal" and nothing else. Do not count
general praise as a signal.

Inputs. The call transcript and attendees, the account’s current plan or products from the CRM, and a short description of what you sell.

Good output. Most calls return nothing, which is the point. The ones that do come with a quote the account manager can bring into the next conversation. The Expansion Finder agent profile covers more of the signals worth tracking.

Template 5: How do you prepare a QBR with an AI agent?

What it does. Writes a prep brief before each quarterly business review, so the meeting starts with outcomes and open issues, not a slide of usage charts.

When it runs. Weekly on a schedule, for every QBR booked in the next 7 days.

Instructions.

For each account with a QBR in the next 7 days, read the handoff brief,
calls, and emails from the last quarter. Write a one-page brief with:
1. The success criteria agreed at the start, and evidence of progress
   on each one.
2. Wins the customer has mentioned, with quotes.
3. Open issues and promises still outstanding, with dates.
4. Stakeholders who should be in the room but have not attended
   recently.
5. Three questions to ask, tied to the points above.
Flag anything that contradicts the success criteria.

Inputs. The original handoff brief, call transcripts, emails, and the meeting calendar or CRM activity that shows the QBR date.

Good output. The account owner walks in knowing what to celebrate, what to fix, and who is missing. Staircase AI’s report also found that renewing accounts held twice as many QBRs as churned ones, so a brief that makes each one easier to run pays off in more of them happening.

How do you roll these templates out without flooding your team?

Start with the handoff brief. It runs once per deal, the output is easy to judge, and it fixes the information gap every other template depends on. Read the first ten briefs with the AE who closed each deal and tighten the instructions wherever the agent missed a commitment.

Send early runs to an in-app history rather than Slack or email, then route them out once the format is stable. Keep the caps small. A renewal review that lists 40 accounts trains people to skip it, while one that lists eight gets read. If your team is also building agents for closed deals, the win-loss analysis agent templates follow the same rollout.

Then check the data underneath. A renewal risk agent cannot rank accounts without a renewal date in the CRM, and a champion watch cannot work if customer calls are not recorded. Clean inputs come first.

Where Airspeed fits

Every template above runs as written in Airspeed Agents. Airspeed already captures your calls, transcripts, and CRM fields, so the agent starts with the full deal history, including what sales promised, instead of a blank context window. You pick the trigger (a schedule, a finished call, a deal stage change, or a web trigger), paste the instructions, and send the output to Slack, email, or in-app history, either as one shared digest or scoped to each owner’s own accounts. Airspeed does the reading on every account, every week, so your account team spends its time on the customers who need a conversation.

If you want to see these templates running on your own customer calls, book a demo.

Frequently asked questions

How can AI agents help customer success teams?

AI agents read the calls, emails, and CRM records on every account on a schedule, then report what changed. For customer success that means a handoff brief when a deal closes, a weekly list of renewals at risk with the evidence behind each one, alerts when a champion goes quiet or leaves, and a prep brief before each QBR. The agent covers every account, not just the ones a CSM had time to review.

What should a sales-to-customer success handoff include?

A good handoff names the business problem the customer bought to solve, the success criteria they agreed to, every commitment made during the sales cycle (integrations, features, pilot terms, and dates), the stakeholders and their roles, and the risks the sales team already saw. Each point should link back to the call or email where it was said, so the account team does not have to rely on memory.

What are early warning signs of churn in B2B accounts?

The most reliable signs are a drop in engagement, a champion or decision maker leaving or going quiet, negative sentiment on calls, unresolved issues that keep coming back, and budget or reorg news. An account with a single active contact is more exposed than one with several, because one departure can end the relationship.

How far ahead should a renewal risk agent look?

Most teams run a renewal risk review weekly across every account renewing in the next 90 to 120 days. That window leaves enough time to bring in an executive sponsor, fix a product issue, or rebuild a lost relationship before the customer has already decided.

Do customer success agents need a separate tool from sales agents?

Not usually. The same agent setup that reviews open deals can review live accounts, as long as it can read the post-sale calls, emails, and CRM fields such as renewal date and account owner. Keeping both on one platform also means the handoff from sales to customer success carries the full deal history instead of a short summary.

Let Airspeed do the busywork

Airspeed captures every call and writes structured updates straight to Salesforce and HubSpot, automatically.

Get your Halloween giftHalloween gift