How to run nps and csat surveys on Starch
NPS and CSAT surveys are how you find out what customers actually think before they stop buying, churn quietly, or leave a public review you didn't see coming. The workflow covers sending the right survey at the right moment, collecting responses, and doing something useful with the data — closing the loop with unhappy customers, spotting trends before they compound, and feeding the signal back into product or operations decisions.
What this looks like in practice varies: a subscription business cares about post-onboarding NPS; a service firm cares about per-project CSAT; an e-commerce operator wants post-delivery scores at scale. The trigger, the audience, and what you do with results all differ.
On Starch, you end up with a live view of your satisfaction scores — segmented however you need, tied to the customer records you already have — without manually stitching together a survey tool, a spreadsheet, and a CRM. Detractors surface in a dedicated queue so someone can actually follow up. Trends show up in a dashboard that updates as responses come in, not after someone remembers to export a CSV. If a score drops, your team gets a Slack message before it becomes a pattern.
Why it matters
Customer satisfaction data has a short shelf life. A low NPS score from six weeks ago doesn't tell you who is about to churn this week. Operators who run surveys without a response workflow — no follow-up for low scores, no way to see trends by cohort or time period — collect data they never act on. The business cost is real: poor retention, missed expansion opportunities, and no early warning system before customers leave or complain publicly.
Common pitfalls
Sending surveys at the wrong moment — blasting NPS to your entire list quarterly instead of triggering CSAT immediately after a key interaction like delivery, onboarding, or ticket resolution. Collecting responses but never routing low scores to anyone; the data lands in a tool no one checks. Tracking a single aggregate score instead of segmenting by customer type, tenure, or product line, which hides the signal in the average. And treating NPS and CSAT as the same thing — NPS measures overall relationship sentiment, CSAT measures a specific experience; conflating them makes both less useful.
Starch apps used
See this running on Starch
Connect your tools, describe what you want, and the agent builds it. Closed beta is free.
Choose your operator
A version of this guide tailored to your role — same recipe, different starting context.
The AI stack built for small customer success teams.
The AI stack built for DTC founders.
The AI stack built for CPG brands.
The AI stack built for boutique professional services firms.
The AI stack built for educators, coaches, and course creators.
The AI stack built for independent clinic owner-operators.
The AI stack built for restaurant and hospitality operators.
The AI stack built for fitness studio operators.
The AI stack built for event planners and agencies.
The AI stack built for small law and accounting practices.
The AI stack built for small property management firms.
The AI stack built for real estate operators.
Related workflows in Customer Support
A customer knowledge base is the document — or collection of documents — that answers the questions your customers ask repeatedly.
Read guide →Refund and return requests are one of those workflows that looks simple until it isn't.
Read guide →Every review you receive — on Google, Yelp, or anywhere else — is a public conversation happening whether you show up to it or not.
Read guide →A quarterly business review is a structured conversation with a customer — a chance to show what's changed since last quarter, what's working, what isn't, and where you're headed together.
Read guide →