Gainsight Journey Orchestrator: Build an Automated Renewal Risk Playbook

What This Builds

You'll configure a Gainsight Journey Orchestrator playbook that automatically triggers a personalized outreach email sequence when an account's health score drops below a threshold — without you manually monitoring each account. Instead of discovering an at-risk account in your Monday health review (by which point 2 weeks may have passed), the system reaches out within 48 hours of the score drop, while you get an alert to follow up personally.

Prerequisites

• Your company uses Gainsight with Journey Orchestrator enabled (enterprise plan feature)
• CS Ops has given you edit access to Journey Orchestrator, or you're working with CS Ops to build this
• Health score model is configured and tracking your accounts
• Time needed: 1–2 hours to build and test; 30 min annual maintenance

The Concept

Journey Orchestrator is Gainsight's automation engine — it's like a "if this, then that" system for customer success. You define a trigger (health score drops below Yellow), a condition (account is in the renewal window), and an action (send a personalized check-in email). Once configured, it runs automatically across your entire portfolio, 24/7, without you doing anything.

Think of it as hiring a junior CSM whose only job is to watch your portfolio's health scores and send the first outreach the moment something drops. You come in every morning, review what the automation triggered, add your personal touch to any escalations, and handle the responses — the system did the monitoring and first contact for you.

Build It Step by Step

Part 1: Plan your playbook before building

Before opening Gainsight, define:

Trigger: When should this playbook activate?

• Health score drops to Yellow (below 65) and account is within 180 days of renewal
• OR: Product usage drops >30% week-over-week for 2 consecutive weeks

Sequence of actions:

• Day 0: CSM receives an internal alert (Slack/email) about the health drop
• Day 2: Automated check-in email sent from CSM to customer champion
• Day 7: If no response: CSM receives a follow-up alert to personally call
• Day 14: If still no response: CSM manager receives an escalation alert

Email content: Write your Day 2 automated email before building. It should:

• Come from the CSM's address (Gainsight can send on your behalf if configured)
• Feel like a personal check-in, not an automated message
• Not mention health scores or internal systems
• Ask one simple question: "How are things going with [product]?"

Example:

Subject: Quick check-in — [Customer Name]

Hi [First Name],

Wanted to pop in and see how things are going with [product]. We're coming up on [renewal period] and I want to make sure we're set up for a strong next year together.

Is there anything you've been wanting to dig into or improve? Happy to set up a call this week if helpful.

[CSM Name]

Part 2: Access Journey Orchestrator

In Gainsight, navigate to Journey Orchestrator (usually under the main navigation — may be labeled "JO" or "Automation"). Click Programs → + New Program.

Name your program: "Renewal Risk — Health Drop Alert" and add a description.

Part 3: Define the trigger (Entry Criteria)

In the program builder, click Entry Criteria:

• Source: Accounts
• Filter 1: Health Score < 65 (Yellow threshold)
• Filter 2: Days to Renewal < 180
• Filter 3: Account Status = "Customer" (not churned, not prospect)

Set Entry frequency: "Daily check" — the program evaluates all accounts daily and enters any that newly meet the criteria.

What you should see: A conditional entry gate that fires when all three conditions are true simultaneously.

Part 4: Build the action sequence

Click Add Action to build your timeline:

Action 1 (Day 0): Internal CSM Alert

• Action type: Call to Action (CTA)
• Assigned to: CSM (the account's owner)
• CTA description: "Health score dropped to Yellow — review account and confirm Day 2 outreach is appropriate"
• Due date: Same day as trigger
• This ensures the CSM sees the alert before the automated email goes out and can delay/cancel if they know something the system doesn't

Action 2 (Day 2): Automated Check-in Email

• Action type: Email
• Template: Your check-in email from Part 1
• Send from: CSM's email address (requires email integration)
• Personalization tokens: {{CustomerName}}, {{CSMName}}, {{ProductName}}

Note: Some companies don't allow Gainsight to send from CSM email addresses for compliance reasons. If yours doesn't, change this to a "Reminder to CSM" CTA to send the email manually.

Action 3 (Day 7): Follow-up Alert (if no response)

• Add a Decision node: "Did the customer reply to the Day 2 email?"
• If No → Action type: CTA → "Customer has not responded to health check-in. Make a personal call this week."
• If Yes → End the playbook (engagement restored)

Action 4 (Day 14): Escalation (if still no response)

• Add another decision: "Has CSM logged a call or meeting in the last 7 days?"
• If No → Action type: Slack/Email notification to CSM Manager → "[Account Name] has been unresponsive for 14 days. Renewal in [X days]. Manual escalation recommended."
• If Yes → End (CSM is engaged)

Part 5: Test with a staging account

Before activating the full program, test it with one known at-risk account:

1. Temporarily lower the health score threshold so a test account enters the playbook
2. Confirm the Day 0 CTA is created correctly
3. Confirm the email drafts look right (check personalization tokens)
4. Do NOT send actual emails in testing — verify the send would work, then cancel

Ask CS Ops to review your program before activating — they can catch configuration errors that would cause spam-sending.

Part 6: Activate and monitor

Once tested, click Activate. The program now runs daily. Each morning, open your Gainsight CTA list to see what the automation triggered overnight. Review:

• New health drop alerts (are these genuine risks or data anomalies?)
• Follow-up prompts (did the customer respond? do you need to call?)
• Escalation notifications (which accounts need manager involvement?)

You're shifting from monitoring the whole portfolio to responding to what the system surfaced. Your job becomes decision-making and relationship work, not surveillance.

Real Example: Mid-Market CS Team

Setup: A CS team of 6 CSMs each managing 50–70 accounts configured a health drop playbook. Threshold: score drops to Yellow within 120 days of renewal.

What happened in Month 1:

• Playbook triggered for 8 accounts across the team
• 5 of 8 replied to the automated check-in email within 48 hours (3 with "we're fine, just quiet," 2 with real concerns)
• 2 escalated to manual calls
• 1 didn't respond → escalated to manager → turned into an executive rescue call

Result: 2 at-risk accounts were saved that the team admits they "probably wouldn't have caught until the renewal window."

What to Do When It Breaks

• Emails aren't sending → Check Gainsight's email integration settings; confirm CSM email addresses are connected; check if company security policy blocks Gainsight email sending
• Too many accounts entering the playbook → Your health score threshold may be too broad. Adjust Entry Criteria to add more filters (e.g., require both health score drop AND usage drop)
• CSMs are getting alert fatigue → Add a "Days Since Last Playbook Entry" filter so the same account can't re-enter more than once per quarter
• False positives (account is fine but score is low) → Add a "CSM Override" exit option in the CTA: "This alert is a false positive — suppress for 30 days."

Variations

• Simpler version: Use ChurnZero's built-in AI playbooks instead of Gainsight JO — ChurnZero has a more guided playbook builder that doesn't require CS Ops configuration
• Extended version: Add a second playbook that triggers when a health score recovers from Yellow to Green → auto-send a congratulatory email and prompt the CSM to explore expansion opportunities

What to Do Next

• This week: Map out your playbook logic on paper before building in Gainsight — the design phase matters more than the configuration
• This month: Build and activate the playbook, then review 4 weeks of results — which triggers were false positives? Tighten the criteria
• Advanced: Chain this playbook to an expansion playbook — when health recovers and adoption is strong, trigger an expansion exploration CTA with AI-suggested expansion email templates

Advanced guide for Customer Success Manager professionals. These techniques use more sophisticated AI features that may require paid subscriptions.