> This page is for version v8.3.0 (default). > For other versions, use one of these documentation indexes: > - v8.3.0 (default): https://docs.mindreasoner.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.mindreasoner.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.mindreasoner.com/_mcp/server. # Strengthen Relationships ![Mind Reasoner](/_fern-files/_img/466e07efd0202b28f29ec8dda3be88918c85104c2652efceb8ff717127f861ca.webp) > **Stop Missing Opportunities** > > **The shift:** Create customer minds. Know when they're ready to expand. Understand how to improve their experience. Build stronger partnerships. > > **Result:** Higher account growth and deeper customer relationships. --- ## Two Key Opportunities #### Account Expansion **The challenge:** * Is this customer ready for upsell? * Which products/features would they value? * How should I approach the conversation? * Will this damage trust or strengthen it? **The solution:** * Predict their readiness for expansion * Know which offerings resonate * Test upsell approaches beforehand * Expand accounts without damaging trust **Outcome:** Grow revenue while strengthening relationships #### Support Quality **The challenge:** * How do customers perceive our support? * What frustrations aren't they voicing? * How can we improve their experience? * What would increase their satisfaction? **The solution:** * Predict their support experience * Uncover unvoiced frustrations * Test service improvements * Act on feedback before they complain **Outcome:** Proactively improve support quality --- ## Account Expansion: Know When to Grow #### 1. Assess Expansion Readiness Ask the customer mind: ```bash > "How satisfied are you with our current service? What additional capabilities would help you?" ``` **Result:** Know if they're ready to expand or need more value first #### 2. Identify What They'd Value ```bash > "If we offered [product/feature], would you be interested? What value would it provide for you?" ``` **Result:** Know which offerings resonate before proposing #### 3. Test Your Approach ```bash > "If I approach you about expanding into [offering], how will you respond? Is now a good time?" ``` **Result:** Expand accounts with approaches that strengthen trust ### Real Example: Upsell Opportunity #### The Problem **Without customer mind:** You think customer is ready to expand based on usage data. **What happens:** * You: "I wanted to discuss upgrading to our Enterprise plan" * Customer: "We're actually evaluating if we're getting value from current plan" * You: *\[damaged trust by pushing expansion when they're questioning value]* **Result:** Upsell attempt backfired. Relationship weakened. #### The Solution **With customer mind:** ### Before Proposing Expansion **You ask customer mind:** ```bash > "How satisfied are you with our current service? Would you be interested in expanding?" ``` **Customer mind reveals:** ``` EXPANSION READINESS: NOT READY Current state: - Satisfaction: MEDIUM - Not fully utilizing current plan - Team adoption still ramping - Budget pressures this quarter Why I'm not ready: - Need to prove ROI on current spend first - Concerned about team capacity - Can't justify expansion to CFO yet What would make me ready: - Help maximizing current plan value - Success metrics to show CFO - Team fully trained and adopting - Seeing clear need for more capacity If you push expansion now: - Will feel like you're not listening - Damages trust in partnership - Makes me question our relationship ``` ### Alternative Approach **You ask:** ```bash > "Instead of expansion, what if I focus on helping you maximize value from your current plan? What would help?" ``` **Customer mind confirms:** ``` YES. This is what I actually need. What would help: - Training session for the team - Best practices from similar customers - Metrics dashboard for CFO reporting - Help with adoption challenges If you offer this: - Strengthens our partnership - Shows you care about our success - Builds foundation for future expansion - When we're ready, you'll be first call ``` ### In Actual Conversation **What happens:** * You: "I wanted to check in. How's the team adoption going?" * Customer: "Actually, we're working through that..." * You: "Let me help. Here's what similar customers have done..." *\[provides value]* * Customer: *\[appreciates partnership approach]* **Result:** Strengthened relationship. Future expansion opportunity preserved. --- ## Support Quality: Improve Proactively #### 1. Assess Support Experience Ask the customer mind: ```bash > "How would you describe your experience with our support team? What frustrates you?" ``` **Result:** Understand their support experience from their perspective #### 2. Uncover Hidden Issues ```bash > "What frustrations with support haven't you told us about? What would improve your experience?" ``` **Result:** Find issues before they escalate or damage the relationship #### 3. Test Improvements ```bash > "If we implemented [improvement], would that address your concerns? What else would help?" ``` **Result:** Focus improvements on what actually matters to customers ### Real Example: Support Quality #### Hidden Frustration ### Before QBR **You ask customer mind:** ```bash > "How would you describe your experience with our support team? What frustrations do you have?" ``` **Customer mind reveals:** ``` SUPPORT SATISFACTION: LOW (at risk) Frustrations I haven't voiced: 1. Response Time Inconsistency Experience: Sometimes 2 hours, sometimes 2 days Why I didn't say: Don't want to complain Impact: Can't rely on support for urgent issues Risk: Actively looking for more reliable vendors 2. Knowledge Gaps Experience: Often get transferred 2-3 times Why I didn't say: Assume it's normal Impact: Wastes my time, delays resolution Risk: Losing confidence in your expertise 3. No Proactive Communication Experience: I have to chase for updates Why I didn't say: Thought that's just how it works Impact: Feel forgotten and unvalued Risk: Damages overall relationship If one more urgent issue gets slow response: - Will escalate to executive team - Will evaluate alternatives - Renewal at risk ``` ### In QBR **What happens:** * You: "I wanted to address support response times. How has that been?" * Customer: "Actually, that's been inconsistent..." *\[opens up about frustration]* * You: *\[acknowledges issue, commits to SLA and proactive updates]* * Customer: *\[feels heard, gives you chance to improve]* **Result:** Prevented escalation by addressing hidden frustration proactively. #### Test Improvements ### Planning Support Improvements **You ask customer mind:** ```bash > "We're implementing a new support model with dedicated engineer assignments and 4-hour SLA. Would this address your concerns?" ``` **Customer mind confirms:** ``` YES. This would significantly improve my experience. Why this addresses my concerns: - Dedicated engineer = consistency + no transfers - 4-hour SLA = can rely on support for urgent issues - Accountability and relationship vs. ticket queue What would make it even better: - Proactive status updates (don't make me chase) - Direct contact for my dedicated engineer - Escalation path for critical issues With these additions: - Confidence restored - Can rely on you for critical needs - Would be a differentiator vs. competitors ``` ### Implementing Improvement **What happens:** * You implement dedicated support with SLA * Add proactive updates and direct contact * Follow up: "How's the new support model working?" * Customer: "This is exactly what we needed. Much better." **Result:** Improved support quality based on what actually matters to customers. --- ## Common Scenarios #### Upsell Readiness Assessment **Predict:** * Current satisfaction with existing service * Readiness for expansion conversation * Which products/features would resonate * Budget and approval constraints * Best timing and approach **Know before proposing** whether expansion strengthens or damages trust. **Outcome:** Grow accounts when customers are ready (not when you need revenue) #### Cross-Sell Opportunities **Predict:** * Awareness of your other offerings * Interest level in additional products * Use cases and value perception * Budget availability and priorities **Test cross-sell approaches** to find what resonates. **Outcome:** Expand relationships with relevant offerings at the right time #### Support Experience Audit **Predict:** * How they perceive support quality * Specific frustrations (voiced and unvoiced) * Response time expectations * Communication preferences **Identify support issues** before they damage relationships. **Outcome:** Proactive support improvements based on customer perspective #### Customer Health Monitoring **Predict:** * Overall relationship strength * Satisfaction trajectory (improving/declining) * Advocate potential vs. churn risk * What would increase loyalty **Monitor regularly** to catch declining satisfaction early. **Outcome:** Maintain strong relationships through continuous monitoring --- ## Quick Start #### 1. Create Customer Minds For high-value customers and expansion targets: * Recent interactions * Support conversations * Business review discussions * Email exchanges **Training:** 5-15 minutes per customer #### 2. Assess Before Acting Before expansion conversations: * Are they satisfied with current service? * Are they ready to expand? * Which offerings would they value? Before support changes: * What frustrates them about current support? * Would proposed improvements help? #### 3. Build Stronger Relationships Use predictions to: * Expand accounts at the right time * Improve support proactively * Address concerns before they escalate **Result:** Deeper partnerships and higher lifetime value --- ## Implementation #### MCP (No Code) **Use Mind Reasoner through Claude Code** No coding. Just natural conversation in Claude. ### Assess Upsell Readiness **You:** ```bash > Create a customer mind for Robert Martinez, VP Operations at LogisticsCo, using /Documents/customer-calls/logisticsco-vp-ops.vtt ``` **Mind Reasoner:** ``` ✓ Training customer mind... (~10 min) ``` **You:** ```bash > How satisfied is Robert with our current service? Would he be interested in expanding to our Premium tier? ``` **Mind Reasoner:** ``` Based on Robert's communication patterns: EXPANSION READINESS: READY Current satisfaction: HIGH - Team fully adopted current tier - Using 95% of capacity - Frequently asking about features in Premium - Budget approved for Q2 expansions Interest in Premium tier: HIGH What he values about Premium: - Advanced reporting (his team needs this) - Priority support (critical for operations) - API access (tech team requesting) Best approach: - Frame as natural progression - Lead with reporting capabilities - Show ROI on reduced manual work - Offer trial period to validate Timing: NOW is good - Budget cycle aligns - Current pain points Premium solves - Won't feel like pushy sales ``` **You:** ```bash > If I approach it this way: [your proposal], how will Robert respond? ``` **Mind Reasoner:** ``` POSITIVE. This approach will work. His likely response: "This makes sense. The reporting alone would save my team 10 hours/week. Let's discuss pricing and migration timeline." Why it works: - Addresses his current pain (reporting) - ROI is clear and relevant - Timing aligns with his needs - Feels like partnership, not sales push You'll close this expansion. ``` ### Assess Support Quality **You:** ```bash > How would Robert describe his experience with our support team? Any frustrations he hasn't voiced? ``` **Mind Reasoner:** ``` SUPPORT SATISFACTION: MEDIUM (room for improvement) Voiced feedback: "Support is generally good" Hidden frustrations: 1. Timezone Coverage Issue: His team operates 24/7, support is 9-5 Impact: After-hours issues wait until morning Risk: Not dealbreaker yet, but growing concern 2. Technical Depth Issue: Often need escalation for complex questions Impact: Delays resolution Risk: Questions if team understands operations use case What would improve experience: - Extended support hours or on-call option - Dedicated engineer familiar with logistics - Faster escalation path for critical issues If you address these proactively: - Differentiates you from competitors - Strengthens partnership - Supports Premium tier expansion ``` [MCP Tools Reference →](/mcp-tools) #### Direct API **Build relationship strengthening into your CS workflow** ```javascript const API_BASE = 'https://app.mindreasoner.com/api/public/v1'; // Create customer mind and train // (See API Quick Start for full workflow) // Assess expansion readiness const expansionReadiness = await fetch(`${API_BASE}/simulate`, { method: 'POST', headers: { 'Authorization': `Bearer ${API_KEY}`, 'Content-Type': 'application/json' }, body: JSON.stringify({ mindId: customerMindId, scenario: { message: "How satisfied are you with our current service? Would you be interested in expanding to Premium tier?" } }) }).then(r => r.json()); console.log('Expansion readiness:', expansionReadiness.message); // Assess support quality const supportFeedback = await fetch(`${API_BASE}/simulate`, { method: 'POST', headers: { 'Authorization': `Bearer ${API_KEY}`, 'Content-Type': 'application/json' }, body: JSON.stringify({ mindId: customerMindId, scenario: { message: "How would you describe your experience with our support team? What frustrations do you have?" } }) }).then(r => r.json()); console.log('Support feedback:', supportFeedback.message); ``` [API Documentation →](/api-quick-start) --- ## Next Steps #### [Predict Customer Needs](/workflow-customer-success-predict-needs) Learn to predict churn risk and test communications #### [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@mindreasoner.com](mailto:support@mindreasoner.com)