NPS in Salesforce: why detractors go unanswered

A customer scores you a 3 and writes a paragraph explaining why. The integration they depend on has failed twice this quarter, support took a week to respond, and they’re evaluating alternatives. The response sits in the survey tool. A month later it shows up as one point on a falling NPS chart, and the account owner never reads the paragraph.

Survey and NPS feedback is one of the sources a customer 360 brings together. It’s the one source where the customer tells you directly what they think, and in most companies it reaches the account team last.

What is an NPS to Salesforce integration?

Net Promoter Score asks customers how likely they are to recommend you, on a scale of 0 to 10. Scores of 9 and 10 are promoters, and 0 to 6 are detractors. An NPS to Salesforce integration sends each response, with the score, the comment and the date, from the survey tool to Salesforce, attached to both the person who answered and their account. A complete one also routes detractors to the account owner quickly and stops the same people being surveyed too often. It works the same way for Qualtrics, Delighted, SurveyMonkey and any survey tool with an API or webhooks.

Where it breaks

1. Only the score travels. The comment, which says what the problem is, stays in the survey tool.
2. The response lands on the wrong record, or a new one. It’s attached to a contact but not the account, or the respondent is a lead or isn’t in Salesforce at all, so the integration creates a duplicate.
3. Detractors wait for a monthly report. A complaint answered the same day can still be fixed. Answered a month later, it explains the churn.
4. Nobody checks the follow-up happened. Detractors are routed, and nothing records whether anyone called them.
5. The same people are surveyed again and again. Champions get three surveys a quarter, response rates fall, and the people still answering are the most annoyed.

What it costs

Customers who could have been saved leave, with the reason written down in a tool nobody opened.

The score becomes a board metric instead of an account signal. A company-level number is reported each quarter, while the account-level detail that could change an outcome goes unused.

Customer marketing loses out too. Promoters are the people most likely to write a review or join a case study, and without their scores in the CRM, finding them means asking around.

What to fix first

1. Send the comment with the score. The number says there is a problem, and the comment says what it is.
2. Attach every response to the person and the account. Look up leads and contacts before creating anything, and create a record only when there’s no match.
3. Route detractors to the account owner within the hour. Include the score, the comment and the account’s open support tickets.
4. Record whether follow-up happened. Track the time to first contact, and report detractors nobody has contacted.
5. Set fatigue rules. For example, survey no one more than once a quarter, and nobody during an open escalation.
6. Use promoters deliberately. Flag them for reviews and references, and track how often each one is asked, so nobody is asked three times in a month.

The guide to building an NPS and survey to CRM sync has the prompts for each step.

How we did it at Tray.ai

When customer marketing at Tray.ai wanted to find customers willing to write a review or join a case study, the monthly survey responses were sitting in Promoter.io and nowhere else. A workflow listened for each new response by webhook, found the person in Salesforce as a contact or a lead, and wrote three fields to their record: the response date, the score and the comment. A one-time batch run brought in past responses. Finding promoters became a Salesforce report instead of a round of messages to sales and customer success.

Where it fits

Survey responses depend on customer data matching to reach the right account, and they’re one of the inputs to the customer health score. A detractor with open escalations in their support history needs a different conversation from one without.

For every source a customer 360 brings together, and where each one goes wrong, read why the customer 360 never sticks.