A bad score that actually reaches someone
A detractor NPS response or a low CSAT score pushes an alert to the right person automatically, Slack, email, or a flagged task, instead of sitting on the contact record until someone happens to look.
Intercom's native surveys let you ask NPS, CSAT, or custom multi-question questions inside the product or by email, triggered by whatever event or attribute you choose, with every response stored directly on the contact as a user attribute. That part works well out of the box. What Intercom doesn't do on its own is act on a bad response the moment it comes in, flag the account, alert someone, change how that customer gets treated next. That's the piece we build on top.
A survey in Intercom can run as a single NPS question, a CSAT check after a support interaction, or a longer custom survey with branching questions, and it can trigger off nearly anything: a signup date, a feature used, a support conversation closing. Every answer lands as a structured attribute on the contact record, which means it's immediately usable in Intercom's own segmentation and messaging, not stuck in a separate reporting tool.
Reporting inside Intercom covers the basics well too: response rates, score trends over time, and segment-level breakdowns, enough to see that NPS dipped last month without needing a separate analytics tool bolted on.
The gap is what happens next. A detractor score sitting as an attribute on a contact doesn't, by itself, notify your CSM, flag the account in your CRM, or change what Fin or a human agent sees the next time that customer opens a conversation. Intercom's own automation can trigger a follow-up message based on a score, which covers the simplest case. Anything that needs to act on a different system, alerting a real person, updating an account health score that lives in Salesforce or HubSpot, flagging a renewal risk, sits outside what the native survey feature does on its own.
A detractor NPS response or a low CSAT score pushes an alert to the right person automatically, Slack, email, or a flagged task, instead of sitting on the contact record until someone happens to look.
NPS and CSAT responses combine with billing and usage data from other systems into one account health signal your CRM can actually act on, instead of living as an isolated attribute inside Intercom.
Tell us what should happen the moment a detractor response comes in, and we'll scope what it would take to make that automatic.
Tell us what a bad response should trigger, an alert, a CRM flag, a different conversation path, and we'll build the connection that makes it automatic. And if the manual check that's actually eating time in your business isn't survey scores at all, we take that work too.
Let's talk →Yes, native surveys cover NPS, CSAT, and custom multi-question formats, triggered by events or attributes you set, with responses stored directly on the contact record.
Intercom's own automation can trigger a follow-up message based on a score. Anything that needs to act on a different system, like alerting a person outside Intercom or updating a CRM record, needs a connection built on top of the survey data.
As structured attributes on the contact record, which makes them usable in Intercom's own segmentation and messaging immediately, though they don't automatically sync anywhere outside Intercom on their own.
Not natively. That requires pulling the attribute data out through Intercom's API and combining it with whatever else feeds the health score, which is exactly the kind of connection we build.