Automate risk escalation

A health score tells you a customer is at risk. An escalation process tells your team exactly what to do about it. Without escalation automation, at-risk tickets sit in the pipeline while reps decide how to respond, managers don't know which accounts need attention, and the customer waits.

This article builds on the health score and CS pipeline from the previous articles. The goal is to automate the response chain: when a health score drops, a ticket is created, the rep is prompted to act, communication goes out to the customer, and if the situation isn't resolved within a defined timeframe, it escalates to a manager.

Combined with the CES survey that triggers when tickets close, this creates a closed loop: identify risk, intervene, resolve (or lose), and collect feedback.

Structure the escalation workflow

You already have a workflow that creates an at-risk ticket when a company's health score drops (from the previous article). Now you need to extend the response.

Open your existing CS pipeline ticket-based workflow (or create a new one if you kept the health score workflow separate). The enrollment trigger should capture tickets in the "At risk" stage of your CS pipeline.

Add these actions in sequence:

Immediate task: create a task assigned to the ticket owner with title "At-risk account: review [Company name] within 24 hours". Set priority to high. This ensures the rep sees the ticket and has a clear deadline.

Internal notification: send an internal email or Slack notification (if integrated) to the ticket owner and their manager. Include the company name, health score, and a link to the ticket record.

Customer outreach prompt: add a task for the rep to reach out to the customer within 48 hours. If you have Marketing Hub Professional or Enterprise, you can also trigger an automated check-in email to the primary contact.

Build time-based escalation

If the ticket hasn't moved from "At risk" after a defined period (e.g. 3 business days), it needs to escalate.

Add a delay in your workflow (e.g. 3 days), then add an if/then branch:

Branch condition: Ticket status is still "At risk".

If yes: create a task assigned to the CS manager with title "Escalation: [Company name] has been at risk for 3+ days without action". Optionally, change the ticket status to "Immediate action" to move it forward in the pipeline.

If no (ticket has already moved to a different status): the rep has taken action. No escalation needed.

You can add further escalation tiers. After 7 days with no resolution, send a notification to a director or VP. The point is that at-risk accounts can't sit idle.

Automate communication sequences

For accounts that enter the CS pipeline, you want a structured communication flow, not ad-hoc emails. Build email templates and sequences specifically for at-risk accounts.

Templates to create:

"We noticed a drop in engagement" check-in email. Tone: concerned, not salesy. Ask what's changed and offer a meeting.

"Quick strategy call" meeting request. Give the customer a direct link to book time with their CS rep.

"Here's what we've done" resolution summary. After the situation is addressed, document what changed and what the next steps are.

Sequence structure:

Combine these templates into a sequence: check-in email on day 1, follow-up on day 4 if no reply, call task on day 7, final email on day 10. If the customer replies or books a meeting at any point, they're removed from the sequence automatically.

Enroll contacts from at-risk tickets into this sequence either manually (through the ticket record) or automatically through a workflow action (requires Sales Hub Enterprise).

Close the loop with surveys

When a ticket in the CS pipeline moves to "Closed resolved" or "Closed churned", trigger a CES survey. This collects feedback on the intervention itself: was the experience easy or difficult?

Go to Automations > Surveys. Create a CES survey and associate it with your CS pipeline. Set it to trigger when a ticket moves to either closed status.

The survey data feeds back into your process. If customers consistently rate the intervention as difficult (scores of 1-3), something in your escalation process needs work. If they rate it easy (6-7), the process is doing its job.

For more detailed feedback, consider a custom survey instead of (or in addition to) the CES. You can ask specific questions: "Did your CS rep respond quickly enough?", "Was the resolution satisfactory?", "What could we improve?"

Handle re-enrollment for recurring risk

Health scores fluctuate. A company might recover, score above the threshold, then drop again three months later. Because you enabled re-enrollment on the health score workflow, the company will re-enter the process and a new ticket will be created.

This is correct behaviour: each at-risk episode should be tracked as a separate ticket. It gives you a history of interventions per company and lets you spot patterns (if a company keeps dropping, the underlying issue hasn't been resolved).

Review companies with multiple at-risk tickets. These are your highest churn risk accounts and may need a different approach: a senior rep, a product change, or an honest conversation about fit.

Risk escalation is the action layer on top of your health score. The score detects the problem. The escalation process ensures someone responds, on time, with the right communication.

The full loop: health score drops > ticket created in CS pipeline > rep gets a task and the customer gets outreach > if no action, it escalates to a manager > when resolved, a survey collects feedback > the score updates and the company re-enters the workflow if it drops again.

This isn't a set-and-forget system. Review your escalation timelines, survey results, and churn data monthly. Tighten the process where customers are falling through, and ease off where reps are getting unnecessary alerts.