> This page is for version v8.3.0 (default).
> For other versions, use one of these documentation indexes:
> - v8.3.0 (default): https://docs.workflows.com/v-8-3-0/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.workflows.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.workflows.com/_mcp/server.

# Prevent Churn & Address Risk

![Mind Reasoner](/_fern-img/466e07efd0202b28f29ec8dda3be88918c85104c2652efceb8ff717127f861ca.webp)

> **Stop Reacting to Problems**
>
> **The shift:** Create a customer mind. Predict their concerns and needs. Act before issues become crises.
>
> **Result:** Prevent churn and strengthen relationships proactively.

---

## What You Can Predict

#### Churn Risk

**Know before they leave:**

* Current satisfaction level
* Unvoiced concerns and frustrations
* What would trigger them to leave
* What keeps them loyal

Act before they start looking elsewhere.

#### Response to Changes

**Test before announcing:**

* Price changes and increases
* Policy updates
* Product changes
* Service modifications

Know how they'll react before communicating.

#### Communication Impact

**Test messages before sending:**

* How they'll respond to your email
* Which tone and framing works
* What concerns they'll raise
* What information they need

Send communications that strengthen trust.

#### Hidden Concerns

**Uncover unspoken issues:**

* What they're not telling you
* Growing frustrations
* Emerging needs
* Competitive temptations

Address concerns before they escalate.

---

## How to Predict

### 1. Create Customer Mind

Upload past interactions with the customer:

```bash
> "SCENARIO: You need to understand Michael Chen, Director of Operations at RetailCo,
and predict his satisfaction level before your next check-in call.

QUESTION: Create a customer mind for Michael using
/Documents/customer-interactions/retailco-director-ops.vtt"
```

**Training:** 5-15 minutes

### 2. Ask Any Question

**Assess satisfaction:**

```bash
> "SCENARIO: Your Customer Success Manager reaches out to you
(as a Director-level customer on a $75K/year Enterprise plan)
for a quarterly check-in. You've been using the platform for
14 months. They're asking about your experience and satisfaction.

QUESTION: How satisfied are you with our service right now?
What concerns do you have that you haven't shared?"
```

**Test communications:**

```bash
> "SCENARIO: You receive an email from your vendor announcing
a 15% price increase effective next quarter. You're currently
paying $50K/year and your contract renews in 4 months. You didn't
budget for this increase.

QUESTION: How will you respond to this announcement? What concerns
will you raise? Will you renew or start evaluating alternatives?"
```

**Predict churn risk:**

```bash
> "SCENARIO: Your account manager schedules a renewal discussion.
Your annual contract is up for renewal in 90 days. You're paying
$100K/year for the Professional tier and have been a customer for
2 years.

QUESTION: What would make you renew vs. consider switching to a
competitor? What concerns or frustrations would influence your decision?"
```

### 3. Act Proactively

Get predictions. Address concerns before they escalate.

**You'll know:** What they need, how to communicate effectively, how to prevent churn

---

## Real Examples

#### Predict Churn Risk

### Before Check-In Call

**You ask customer mind:**

```bash
> "SCENARIO: Your Customer Success Manager reaches out to you (as Director
of Operations at RetailCo) 6 weeks before your annual renewal. You're on
a $120K/year Enterprise plan and have been a customer for 18 months. They're
doing a health check and asking about satisfaction.

QUESTION: How satisfied are you with our service currently? What concerns
do you have that you haven't voiced yet?"
```

**Customer mind reveals:**

```
SATISFACTION LEVEL: LOW (at risk)

Hidden concerns I have (that I haven't voiced):

1. Response Time Issues
   What's happening: Support tickets taking 48+ hours
   Why I haven't said anything: Don't want to be demanding
   Impact: Losing trust in our reliability
   Risk level: HIGH - actively looking at alternatives

2. Feature Gap
   What's happening: Missing reporting features I need
   Why I haven't said anything: Assumed it was coming
   Impact: Using manual workarounds = wasting time
   Risk level: MEDIUM - frustration building

3. Price-Value Misalignment
   What's happening: Not getting value for what we pay
   Why I haven't said anything: Evaluating alternatives first
   Impact: CFO asking questions about ROI
   Risk level: HIGH - renewal at risk

What would make me leave:
- Another slow support response
- Competitor with the reporting I need
- Better pricing elsewhere

What would make me stay:
- Proactive conversation about support quality
- Roadmap showing reporting features coming
- Acknowledgment and action plan
```

### In Actual Check-In

**What happens:**

* You: "I wanted to check in. How's support response time been for you?"
* Customer: "Actually, that's been a concern..."
* You: *\[addresses the issue proactively with action plan]*

**Result:** Prevented churn by addressing concerns before customer started evaluating competitors.

#### Test Price Increase Communication

### Before Sending Announcement

**You ask customer mind:**

```bash
> "SCENARIO: Your vendor emails you announcing a 15% price increase
taking effect in 90 days. You're currently paying $80K/year for their
Professional plan and your contract auto-renews in 5 months. You've been
a customer for 2 years. This increase wasn't budgeted and your CFO is
already scrutinizing software spend.

QUESTION: How will you respond to this price increase announcement?
What concerns will you raise? Will you accept it, negotiate, or start
evaluating competitors?"
```

**Customer mind predicts:**

```
My likely response: NEGATIVE (could trigger churn evaluation)

Why this is risky for me:
- I didn't budget for this
- Already fighting internally to justify our cost
- CFO is looking for cuts
- Competitors are reaching out

Concerns I'll raise:
1. "What new value are we getting?"
   Real concern: Need ammunition for internal justification

2. "Can we discuss alternatives?"
   Real concern: Need to show I'm negotiating

3. "This wasn't in our agreement"
   Real concern: Feel blindsided

What would prevent churn:
- Advance warning (not surprise)
- Clear value add since last year
- Willingness to discuss timing/options
- Acknowledgment of partnership
```

### Test Your Communication

**You ask:**

```bash
> "SCENARIO: Instead of a generic announcement, your vendor sends you a
personalized email with 60-day advance notice of the price increase. The
email includes a summary of value delivered over the past year and offers
to schedule a call to discuss. You're still on that $80K/year plan with
the CFO watching spend closely.

QUESTION: How will you respond to this approach? Does the personalized
communication and advance notice change your reaction vs. a generic
announcement?"
```

**Customer mind confirms:**

```
BETTER. This approach will work.

Why:
- 60-day notice lets me budget/negotiate
- Value summary gives me internal ammunition
- Offer to discuss = respect
- Won't trigger immediate churn evaluation

My likely response:
"Let's schedule a call to discuss. I'll need to
understand the value increase for our CFO."

You've prevented the defensive reaction.
```

### In Actual Communication

**What happens:**

* Send refined email with advance notice
* Customer: *\[responds as predicted, requests call]*
* Call happens, concerns addressed
* Renewal secured

**Result:** Prevented churn by testing communication approach beforehand.

#### Uncover Hidden Concerns

### Before Quarterly Business Review

**You ask customer mind:**

```bash
> "SCENARIO: Your Customer Success Manager reaches out to schedule your
Quarterly Business Review. You're a VP-level customer on a $150K/year
Enterprise plan, been with the company for 9 months. The CSM wants to
review your experience and discuss your goals for the next quarter.

QUESTION: What concerns or frustrations do you have about our service
that you haven't told us about yet? What's working well vs. what needs
improvement?"
```

**Customer mind reveals:**

```
HIDDEN FRUSTRATIONS:

1. Implementation Support Lacking
   What happened: Felt abandoned after kickoff
   Why I didn't say: Didn't want to complain
   Impact: Team adoption suffering
   What I need: Ongoing implementation guidance

2. Account Manager Turnover
   What happened: 3rd AM in 6 months
   Why I didn't say: Seems like your internal issue
   Impact: No relationship continuity
   What I need: Stability and someone who knows us

3. Feature Requests Ignored
   What happened: Submitted 5 requests, no response
   Why I didn't say: Assume you're too big to care
   Impact: Feel like we don't matter
   What I need: Acknowledgment and transparency

Risk level: MEDIUM
- Not actively leaving yet
- But relationship weakening
- One more issue could trigger evaluation
```

### In QBR

**What happens:**

* You: "I wanted to address implementation support. How can we help your team adoption?"
* Customer: "Actually, that's been challenging..." *\[opens up]*
* You: *\[provides implementation support plan]*
* You: "And I know you've had AM turnover. I'm committed to stability."
* Customer: *\[feels heard and valued]*

**Result:** Strengthened relationship by addressing hidden concerns proactively.

---

## Common Scenarios

**Price Increase Communication**: Predict how they'll respond to the increase, budget constraints, what justification they need internally. Retain customers through price changes by communicating effectively.

**Renewal Risk Assessment**: Predict current satisfaction level, likelihood to renew vs. evaluate alternatives, hidden concerns. Higher renewal rates by preventing churn before it starts.

**Support Quality Check**: Predict how they perceive support quality, unresolved frustrations, response time concerns. Improve support quality proactively based on customer perspective.

**Product Change Impact**: Predict how they'll respond to product changes, features they rely on, workflow disruption concerns. Smooth product transitions without damaging satisfaction.

---

## Implementation

#### MCP (No Code)

**Use Mind Reasoner through Claude Code**

No coding. Just natural conversation in Claude.

**You:**

```bash
> Create a customer mind for Sarah Williams, VP Product at FinanceApp,
using /Documents/customer-calls/financeapp-vp-product.vtt
```

**Mind Reasoner:**

```
✓ Training customer mind... (~10 min)
```

**You:**

```bash
> SCENARIO: You're about to send Sarah Williams (VP Product at FinanceApp,
currently paying $95K/year on Professional tier) an email announcing a 20%
price increase taking effect in Q2. Her contract renews in 6 months and she's
been a customer for 2 years. Her CFO has been asking all departments to reduce
software spend.

QUESTION: How will Sarah respond to this price increase announcement? What
concerns will she raise? Will she renew, negotiate, or start shopping for
alternatives?
```

**Mind Reasoner:**

```
Based on Sarah's communication patterns:

RISK LEVEL: HIGH (could trigger churn evaluation)

Her likely response:

1. Budget Shock: "This wasn't budgeted"
   Context: She's already fighting for budget internally
   Risk: CFO will question the spend
   What she needs: Advance notice + value justification

2. Competitive Evaluation: "We'll need to evaluate alternatives"
   Context: Not a bluff - she's under pressure
   Risk: Once she starts looking, hard to recover
   What she needs: Understanding and flexibility

3. Value Justification: "What's changed to warrant this?"
   Context: Needs ammunition for internal approval
   Risk: Can't defend spend without clear ROI
   What she needs: Specific value delivered since last year

Predicted outcome if announced without preparation:
- Will start competitor evaluation
- Renewal at serious risk

Recommendation:
- Proactive 1:1 call before announcement
- 90-day advance notice minimum
- Clear ROI deck for her CFO
- Offer flexible timing options
```

**You:**

```bash
> SCENARIO: Instead of sending a generic price increase email, you personally
call Sarah to discuss the increase before sending anything official. You offer
90-day advance notice, present an ROI analysis showing value delivered, and
offer flexible timing options for implementation. She's still facing that CFO
pressure to cut costs.

QUESTION: Will this proactive, personalized approach prevent a defensive
reaction? How will Sarah respond to being called first vs. just getting an
email announcement?
```

**Mind Reasoner:**

```
YES. This approach will work better.

Why:
- Proactive call shows respect
- Advance notice = time to navigate internally
- ROI deck = tools she needs
- Flexibility = partnership, not edict

Her likely response:
"I appreciate the heads up. Let me take this ROI
analysis to our CFO. Can we discuss timing options?"

You've converted a churn risk into a partnership conversation.
```

[MCP Tools Reference →](/mcp-tools)

#### Direct API

**Build customer prediction into your CS workflow**

```javascript
const API_BASE = 'https://api.reasoner.com/api/mindsim';

// Create customer mind and train
// (See API Quick Start for full workflow)

// Assess churn risk
const churnRisk = await fetch(`${API_BASE}/simulate`, {
  method: 'POST',
  headers: {
    'Authorization': `Bearer ${API_KEY}`,
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    mindId: customerMindId,
    scenario: {
      message: "SCENARIO: Your Customer Success Manager reaches out to you (as a customer on a $100K/year Enterprise plan) 3 months before renewal. You've been using the platform for 18 months. They're checking in on satisfaction and asking about your renewal plans.\n\nQUESTION: How satisfied are you with our service? What concerns do you have? What would make you renew vs. consider switching to a competitor?"
    }
  })
}).then(r => r.json());

console.log('Churn risk assessment:', churnRisk.message);

// Test communication
const commTest = await fetch(`${API_BASE}/simulate`, {
  method: 'POST',
  headers: {
    'Authorization': `Bearer ${API_KEY}`,
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    mindId: customerMindId,
    scenario: {
      message: "SCENARIO: Your vendor sends you an email announcing a 15% price increase taking effect in 90 days. You're currently paying $75K/year and your contract renews in 4 months. This increase wasn't budgeted.\n\nQUESTION: How will you respond to this announcement? What concerns will you raise? Will you accept it, negotiate, or start evaluating alternatives?"
    }
  })
}).then(r => r.json());

console.log('Communication test:', commTest.message);
```

[API Documentation →](/api-quick-start)

---

## Next Steps

#### [Drive Expansion & Growth](/workflow-customer-success-drive-expansion)

Identify expansion opportunities and improve support

#### [MCP Quick Start](/mcp-quickstart)

Set up in 5 minutes

#### [API Quick Start](/api-quick-start)

Build into your CS platform

> **Info**
>
> Questions? Email [support@reasoner.com](mailto:support@reasoner.com)