See Churn Risk Right Inside Intercom
SaveMRR syncs churn data to Intercom. at risk scores, failed payment status, cancel flow history, and recovery outcomes. Your support team sees churn context without leaving Intercom.
Your support team talks to at risk customers every day without knowing it. A customer asks how to export their data. That might be a churn signal. Someone complains about a missing feature. They might already have a failed payment. A user goes quiet for two weeks and then opens a ticket. Churn Radar may have flagged them days ago. The problem is that your support team works in Intercom, but your churn data lives in Stripe and SaveMRR.
The SaveMRR Intercom integration bridges that gap. Every churn-relevant data point. risk scores, payment status, cancel flow history, recovery outcomes. syncs directly to Intercom user profiles. When a support agent opens a conversation, they immediately see whether this customer is at risk, whether their last payment failed, and whether SaveMRR is already working to recover them.
How the Data Sync Works
SaveMRR writes custom attributes to Intercom user profiles via the Intercom REST API. The sync is event driven. every time something changes in SaveMRR, the corresponding Intercom profile updates in real time.
- ●Real time updates. when a payment fails, a risk score changes, or a cancel flow completes, Intercom reflects the change within 10-15 seconds
- ●Matched by email. SaveMRR uses the customer's Stripe email to find the matching Intercom user. If no match exists, the data waits until the user appears in Intercom
- ●No Intercom code changes; the integration writes to Intercom's API server-side. You don't need to modify your Intercom Messenger installation or change any frontend code
What Data Syncs to Intercom
| Attribute | Type | Example Value | Updates When |
|---|---|---|---|
| savemrr_risk_score | Integer (0-100) | 72 | Churn Radar recalculates |
| savemrr_payment_status | String | failed | Payment fails, retries, or recovers |
| savemrr_cancel_flow | String | saved_with_discount | Customer enters or completes cancel flow |
| savemrr_mrr | Number | 49.00 | Subscription changes |
| savemrr_last_failure | Date | 2026-03-28 | New payment failure occurs |
| savemrr_recovery_status | String | dunning_active | Recovery campaign starts or completes |
Setup in 3 Steps
- ●Step 1: Generate an Intercom API token. in your Intercom workspace, go to Settings > Integrations > Developer Hub, create a new app, and generate an access token with read/write permissions for Users
- ●Step 2: Connect in SaveMRR. go to app.savemrr.co > Integrations > Intercom and paste your API token. SaveMRR validates the connection and displays your Intercom workspace name
- ●Step 3: Verify sync. SaveMRR sends a test attribute update to a sample user. Open that user's profile in Intercom to confirm savemrr_risk_score appears in the custom attributes panel
Support-Led Retention
Automated recovery handles the majority of churn, but support conversations are where you save the edge cases. A customer who ignored three dunning emails might respond immediately when a support agent says "I noticed your payment didn't go through. want me to help sort it out?" The key is giving your support team the right context at the right time.
- ●Prioritize high-risk conversations. sort your Intercom inbox by savemrr_risk_score to focus on customers most likely to churn. A customer with a risk score of 85 and an open support ticket deserves immediate attention
- ●Context-aware responses. when you see savemrr_payment_status is "failed," you know this customer has a billing issue before they even mention it. Address it proactively in the conversation
- ●Post-save follow up. If savemrr_cancel_flow shows "saved_with_discount," your support team knows this customer was on the edge. A personal check in two weeks later can solidify the save
- ●Escalation triggers. use Intercom's automation rules to assign conversations from customers with savemrr_risk_score above 80 to senior support agents or directly to the founder
Use Cases
- ●Proactive outreach. filter Intercom users where savemrr_risk_score > 70 and send a personal message before they churn. "Hey, just checking in. noticed you haven't used [feature] in a while. Anything I can help with?"
- ●Payment recovery assist. when a customer with savemrr_payment_status "failed" opens a chat, your agent can immediately share a card update link instead of waiting for the customer to bring it up
- ●Churn reason analysis. export Intercom conversations tagged with churn related attributes to understand why customers leave in their own words, supplementing SaveMRR's cancel flow survey data
- ●Targeted product tours. trigger Intercom product tours for customers with savemrr_risk_score above 50 to re engage them with features they haven't discovered yet
SaveMRR automates the heavy lifting of churn prevention. dunning emails, cancel flows, payment retries, win back campaigns. The Intercom integration gives your support team the context to handle the cases that automation alone can't catch. Together, you cover both the automated and human sides of retention. For real time team alerts, add the Slack integration. To route churn data to your analytics stack, connect Segment. Learn more about detecting at risk customers in Stripe.