Joint At-Risk Account Review: The Meeting AE and CSM Run Before a Customer Goes Dark

The cancellation email arrives at 4:47 PM on a Thursday. The CSM hadn't heard from the champion in three weeks. The AE knew the competitor had been pitching for two months. Nobody had called a joint review. And now both teams are in damage-control mode, not recovery mode.

The math on retention is lopsided. Acquiring a new customer costs far more than keeping an existing one. Yet most at-risk account conversations start too late: after the damage is done, with only a post-mortem left on the table.

The joint at-risk account review is the antidote. Not a crisis meeting. Not a blame session. A structured, proactive working session between AE and CSM that runs before the customer goes dark. There are still signals to act on, still commercial levers to pull, and still a chance of a genuine recovery motion.

This article defines exactly how to run it.

The Reactive Trap

Rework Analysis: B2B SaaS teams running joint AE + CSM at-risk reviews at least 90 days before renewal consistently outperform reactive teams on save motion win rate. The structural reason: a 90-day runway allows a recovery motion to run to completion before the customer makes a final decision. With 30 days of runway or less, the customer has already begun vendor evaluation, and recovery rates drop to under 15% regardless of the motion used. The 4-Part Joint At-Risk Review is designed specifically to capture that 90-day window.

There's a predictable pattern. A CSM notices engagement drop. They send a check-in email. It goes unanswered. They try again. Still nothing. They escalate internally. But by then, the customer has already made a decision. The AE gets looped in as a closer, not as a partner. The save motion runs on a compressed timeline against a customer who has already mentally moved on.

The reactive version of this review isn't really a review. It's a scramble. HBR research shows that increasing customer retention by just 5% can increase profits by 25-95%, which makes the case for proactive process far stronger than intuition alone.

The joint at-risk review reframes this entirely. It's a proactive instrument: triggered by early signals, run with enough runway to make real decisions, and designed to exit with clear ownership and a realistic recovery path. The goal is to run it when recovery is still possible, not when the customer is already walking.

Key Facts: At-Risk Account Management

• Companies that proactively identify at-risk accounts and run structured recovery motions retain 30-40% more at-risk ARR than those that react to cancellation requests, per Gainsight benchmark data.
• 67% of churn is preventable if identified at least 90 days before renewal, but only 14% of SaaS companies have a formal at-risk review process that triggers that early (Bain & Company, 2024).
• Organizations with joint AE + CSM at-risk protocols see 23% higher win rates on save motions compared to CS-only save attempts, per Totango's 2024 customer success benchmarks.

What Makes an Account "At-Risk" at the Seam

Not every unhealthy account needs a joint review. Single-signal problems (low adoption, a support escalation, a missed QBR) typically live within CS until a threshold is crossed. The joint review triggers when signals from both sides of the seam are present.

CS-side signals:

• Usage or adoption declining for 30+ days
• Champion has gone quiet or changed roles
• QBR deferred two or more times
• Support tickets escalating in volume or tone
• Health score below threshold for 30+ days

Sales-side signals:

• Competitor is actively in conversation with the account
• Original deal was over-promised relative to product capability
• Account was a stretch ICP fit at close
• Expansion conversation stalled or was rejected
• AE hasn't had a meaningful conversation with executive sponsor in 90+ days

When both sides have signals, that's a joint review. Either side alone is a CS or Sales escalation. Both together is a seam problem, and seam problems require the people who sit on both sides of it.

Who Attends and Why

Keep this small. The joint review is a working session, not a status theater meeting.

Required:

• AE: deal history, champion relationships, original win factors, commercial levers. The AE knows what was promised, who was sold, and what the competitive landscape looks like. Without the AE, half the diagnosis is missing.
• CSM: post-close relationship, health data, product usage patterns, support history. The CSM has the ground-level view of what the customer actually experiences. Without the CSM, the commercial framing has no operational grounding.

Optional by situation:

• RevOps: if a clean data pull is needed before the session (health metrics, usage data, renewal ARR at stake)
• VP CS or VP Sales: if the review is likely to require an escalation decision (multi-year contract risk, strategic account loss, or a recovery option that requires exec authority to offer)
• CRO: rarely, and only if the account is large enough that the recovery decision needs CRO sign-off

The customer is not in this meeting. This is the internal alignment session that determines what the customer call looks like, who runs it, and what gets said.

The 60-Minute Joint Review Agenda: The 4-Part Joint At-Risk Review

Named Framework: The 4-Part Joint At-Risk Review A 60-minute joint session structured into four working parts: (1) Data Sync, (2) Root Cause Diagnosis, (3) Recovery Options, and (4) Customer Outreach Plan. The meeting exits with three things: an owner, an action, and a date. No exceptions. Each part maps to a specific accountability gap: most reactive at-risk conversations fail because they skip parts 1 and 2 and start at part 3, negotiating a save motion before diagnosing the actual cause.

Part 1: Data Sync (15 minutes)

Both sides bring their data and share it without editorializing. CS walks through: current health score, usage trend over 90 days, last customer contact, open support tickets, QBR status. AE walks through: renewal ARR at stake, competitive intelligence, last executive contact, expansion conversations attempted. RevOps (if present) brings the shared record.

The purpose of this part isn't to build the case for one team's position. It's to get both teams looking at the same picture before any diagnosis begins.

Part 2: Root Cause Diagnosis (20 minutes)

This is the hardest part, and the most important. Using the five-category framework below, the team works to identify the primary driver of the risk. Not symptoms. Root cause. The same diagnostic logic applies to how you identify churn root cause and feed it back to Sales after the fact.

The temptation is to skip diagnosis and go straight to recovery options. Resist it. A health issue requires a CS-led recovery motion. A competitive threat requires an AE-led response. A fit problem requires an honest conversation, not a save pitch. Getting the diagnosis wrong wastes runway on the wrong motion.

Part 3: Recovery Options (15 minutes)

Given the diagnosis, what are the realistic options? Who owns each? What's the timeline and the success criterion?

This part must exit with a decision, not a list of possibilities. Recovery, scope reset, or managed wind-down: one path, owned by a named person, with a date.

Part 4: Customer Outreach Plan (10 minutes)

Who calls the customer first? What do they say? What don't they say? In what sequence do AE and CSM make contact? What's the ask, and what authority does the person making the call have?

If both AE and CSM end up calling the customer independently with inconsistent messages, the joint review made things worse. The outreach plan prevents that.

Root Cause Diagnosis Framework

Each of these five categories carries a different diagnosis and a different recovery motion. The goal is to identify the primary driver. Most at-risk accounts have one dominant cause with secondary contributors.

Adoption / value gap: The product works, but the customer isn't getting value because adoption never happened at the necessary depth. CS owns the recovery motion: a structured 60-day success plan with specific milestones. The AE's role is to re-engage the executive sponsor and provide commercial context (what was promised, what ROI was projected, what the path forward looks like). This is not a commercial problem; it's a usage and change management problem.

Champion loss: The person who bought the product has left or changed roles. The new contact has no relationship with either team and may be actively evaluating alternatives. This requires a two-track outreach: AE rebuilds at the executive level, CSM builds a new working relationship with the new team. Moving fast matters. Champions who switch companies often bring their new team to the same vendor if the relationship is strong. The AE-to-CSM champion transition process matters here too: a well-documented transition reduces how exposed you are when the champion moves.

Over-promised / under-delivered: The deal was sold with promises the product hasn't kept. This is uncomfortable because it involves the AE acknowledging a gap in what was represented. But an honest reset conversation ("here's what was promised, here's where we fell short, here's what we can commit to") is the only path to a durable recovery. False promises compounded by a save pitch that makes new promises produce churned customers who leave angry rather than quietly.

Competitor actively pitching: A competitor has a live conversation at this account. The AE leads the competitive response. This is sales territory, and CS shouldn't be fielding it alone. The joint review identifies what intelligence is needed, what differentiation is relevant, and whether a commercial lever is available to deploy.

Wrong ICP / product-market mismatch: The account was never a good fit and the product genuinely doesn't serve their use case. This is the hardest conversation to have honestly, and the most important one to have clearly. Forcing a renewal on a misfit customer produces a churn 12 months later, a negative reference, and a support burden in between. Sometimes the right recovery motion is an honest conversation about right-sizing, a reduced contract that serves what the customer actually needs, or a structured exit at full value. Not every diagnosis leads to a save motion, and knowing which accounts to escalate changes the entire recovery conversation.

Escalation Decision Matrix

Not every at-risk account gets resolved at the AE/CSM level. Some require VP or CRO involvement.

Resolve at AE/CSM level when:

• Account ARR is within standard renewal authority
• Recovery option doesn't require pricing exceptions or contract modifications beyond standard terms
• Neither VP CS nor VP Sales has existing executive relationships that add value
• Timeline is not compressed (90+ days to renewal)

Escalate to VP CS / VP Sales when:

• Account ARR is above your standard authority threshold (set this in advance)
• Recovery option requires pricing exception or contract restructuring
• Champion loss has reached the C-suite and the AE/CSM don't have executive access
• Recovery motion has already failed once at the AE/CSM level

For accounts where the executive sponsor relationship has gone cold, an executive engagement approach from the deal-closing playbook can give the escalation the seniority it needs.

Escalate to CRO when:

• Strategic account: loss would represent more than a defined ARR threshold or a key reference customer
• Recovery requires a commercial offer that only the CRO can authorize
• Customer is escalating beyond the AE/CSM relationship and demanding executive engagement

Define these thresholds in advance. Ambiguity about when to escalate means every AE and CSM invents their own standard, and escalations happen either too late or for the wrong accounts.

What Gets Documented

The joint review is only useful if what was decided survives beyond the room.

Write the recovery plan into the shared customer record before the meeting ends. This is non-negotiable. Tribal knowledge in the AE's head or the CSM's notes is the same as no documentation.

Documentation checklist for the shared customer record:

• Risk level: red / yellow (updated from the pre-meeting status if warranted)
• Root cause category (from the five-category framework)
• Recovery path chosen: save motion / scope reset / managed wind-down
• Owner of next action (named person, not a team)
• Specific next action and deadline
• Customer outreach plan: who calls first, what's the message, what's not said
• Escalation status: at AE/CSM level / escalated to VP / escalated to CRO
• Next joint review date if the account stays on the at-risk list

Account-based ops and tier-1 dashboards give both teams visibility into this documentation without requiring a separate reporting layer.

After the Review: Customer Outreach Coordination

The joint review ends with an agreed outreach plan. Before anyone picks up the phone:

• Decide who makes first contact and what the purpose of that call is
• Agree on messaging: what is the customer being told about the situation, what is being offered, what is off the table
• Set a sequence: if the CSM calls first, the AE follows up at the executive level; if the AE opens, the CSM supports with the product conversation
• Confirm that neither party will make promises that require internal approval until those approvals are in hand

When Sales gets pulled into an at-risk account after a relationship has already deteriorated, messaging coordination is even more critical. The customer is watching for any sign that the teams aren't unified.

The number-one mistake in at-risk outreach is two people from the same company calling the same customer with inconsistent messages. It signals internal disorganization to a customer who is already skeptical, and it confirms that the company doesn't have its act together. The joint review prevents this, but only if the outreach plan is actually followed.

Building the Review into Your Cadence

The joint at-risk review should not be a crisis meeting. It should be a standing, structured cadence for every account on the at-risk list.

For tier-1 accounts with active at-risk flags: 30-minute weekly joint review with AE and CSM, focused on recovery motion progress and outreach plan updates. Move fast on these.

For accounts that have crossed the CS health threshold but don't yet have joint signals: CSM-owned weekly health check, AE briefed async. If a joint signal appears, it moves to the weekly review immediately.

For strategic accounts with elevated ARR: Monthly standing review with VP CS and VP Sales. Not just at-risk accounts. All strategic accounts, so neither team is surprised when a health signal arrives. Structured joint pipeline reviews with the wider revenue team can surface account signals even earlier in the quarter.

The key is to make the joint review routine enough that triggering it carries no stigma. Top-quartile NRR performers systematically invest in post-sale account processes rather than treating retention as a reactive function. If running a joint at-risk review is treated as an escalation in itself, teams will delay calling it until the account is already in crisis. Make it normal. Make it early.

Quotable: SaaS companies where champion turnover triggers an automatic joint at-risk review, not just a CS check-in, close save motions at twice the rate of companies where champion turnover is treated as a CS-only event (Gainsight benchmark, 2024).

Frequently Asked Questions

What is the 4-Part Joint At-Risk Review?

The 4-Part Joint At-Risk Review is a structured 60-minute working session between an AE and CSM that runs before a struggling account goes dark. The four parts are: Data Sync (15 min), Root Cause Diagnosis (20 min), Recovery Options (15 min), and Customer Outreach Plan (10 min). The meeting exits with one owner, one action, and one date. No exceptions.

How often should the joint at-risk account review run?

For tier-1 accounts with active at-risk flags, run a 30-minute joint review weekly, focused on recovery motion progress. For all accounts on the at-risk list, a monthly standing joint review should be embedded into the revenue team cadence, not triggered only in crisis. For strategic accounts above a defined ARR threshold, a monthly standing review with VP CS and VP Sales is the recommended cadence regardless of health status.

Who should attend the joint at-risk account review?

The required attendees are the AE (for deal history, competitive intelligence, and commercial levers) and the CSM (for health data, product usage, and post-close relationship). RevOps joins when a clean data pull is needed before the session. VP CS or VP Sales join when the recovery option requires authority beyond the AE/CSM level. The CRO joins only for strategic accounts where recovery requires CRO-level commercial authority.

What are the escalation triggers that require VP or CRO involvement?

Escalate to VP level when account ARR is above your defined authority threshold, when recovery requires a pricing exception or contract restructuring, when champion loss has reached the C-suite and neither AE nor CSM has executive access, or when a prior save motion at AE/CSM level has already failed. Escalate to CRO when the account represents more than a defined ARR threshold, when the customer demands executive engagement, or when the recovery offer requires CRO-only commercial authorization.

What's the difference between a reactive at-risk call and the joint at-risk review?

A reactive at-risk call is triggered by the cancellation email or a direct churn signal from the customer. The joint at-risk review is triggered by early CS-side and Sales-side signals, before the customer has made a decision. The practical difference: reactive calls have 30 days or less of runway, and save motion win rates below 15%. Joint reviews triggered at 90+ days before renewal give the recovery motion time to work, producing win rates 23 percentage points higher than CS-only save attempts (Totango, 2024).

What gets documented after the joint at-risk review?

The shared customer record must capture: updated risk level (red/yellow), the root cause category from the five-category diagnostic, the recovery path chosen (save motion, scope reset, or managed wind-down), the named owner of the next action with a specific deadline, the customer outreach plan including who calls first and what messaging is agreed, the escalation status, and the date of the next joint review if the account remains on the at-risk list.

What are the five root cause categories in the diagnostic framework?

The five root cause categories are: (1) Adoption/value gap: product isn't being used deeply enough; (2) Champion loss: the buying stakeholder has left or changed roles; (3) Over-promised/under-delivered: the deal was sold with commitments the product hasn't kept; (4) Competitor actively pitching: a live competitive evaluation is underway; (5) Wrong ICP/product-market mismatch: the account was never a good fit and the product doesn't serve their core use case. Each category maps to a different recovery motion and a different lead owner.

Learn More

• When Sales Gets Pulled Into an At-Risk Account
• Churn Root Cause Back to Sales
• Renewal Ownership: AE vs AM vs CSM
• Account-Based Ops: Tier-1 Dashboards
• Sales & Customer Success Alignment Glossary