Customer Support

How to run nps and csat surveys as Small Customer Success Teams

Customer SupportFor Small Customer Success Teams2 apps11 steps~22 min to set up

Your 3-person team covers 250 B2B accounts. You know you should be running NPS after onboarding and CSAT after support tickets close, but right now 'running surveys' means someone exports a CSV from HubSpot, pastes emails into Typeform or SurveyMonkey, waits two weeks for responses, downloads another CSV, and manually maps scores back to accounts in a spreadsheet. By the time you have a number, the unhappy customer has already gone quiet. You have no automated way to trigger a survey when a ticket closes in Intercom, no dashboard that shows NPS by cohort or segment, and no alert when an account scores below a 7. Gainsight does all of this — it also costs more than your entire software budget.

Build this on Starch → See the apps used

Customer SupportFor Small Customer Success Teams2 apps11 steps~22 min to set up

Outcome

What you'll set up

A survey dispatch automation that triggers NPS sends after onboarding milestones and CSAT sends when support tickets close in Intercom — no manual CSV exports

A live score dashboard showing NPS by account tier, CSAT trend by month, and a detractor list sorted by renewal date so you know exactly which accounts need a call this week

A churn-risk alert that fires to Slack when any account scores below 7 on NPS or below 3 on CSAT, with the account's HubSpot deal stage and last activity pulled in automatically

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

CRM Customer Support Agent

Data sources & config

Starch syncs your HubSpot data on a schedule (contacts, companies, deals, deal stages). Connect Intercom from Starch's integration catalog — the agent queries it live when a ticket closes and when the automation needs contact data. Gmail is synced directly by Starch on a schedule and used to send survey emails. Slack is connected and used to fire detractor alerts. Survey responses are logged back to account records in real time.

Prompts to copy

Build me a survey dispatch automation: when a new customer completes their onboarding call (tracked as a stage change in HubSpot), send them an NPS survey via email after 14 days. Log the score and verbatim response back to the account record.

Build me a CSAT trigger: when a support ticket is closed in Intercom, send the contact a 1-question CSAT email within 2 hours. Pull their first name from HubSpot so the email isn't generic.

Build me a health-score dashboard that shows each account's most recent NPS score, most recent CSAT score, number of open tickets in Intercom, and renewal date from HubSpot — sorted by accounts most at risk.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect HubSpot — Starch syncs your contacts, companies, deals, and deal stages on a schedule. This is the account master record that every survey score attaches to.

2 Connect Intercom from Starch's integration catalog. The agent queries it live to detect when a ticket status changes to 'closed' and to pull the contact's email and name for personalization.

3 Connect Gmail — Starch syncs it directly on a schedule and uses it to send survey emails from your team's address, not a generic no-reply domain.

4 Connect Slack — Starch will use it to push detractor alerts to your #cs-alerts channel the moment a low score comes in.

5 Tell Starch: 'Build a 14-day post-onboarding NPS automation. When a HubSpot deal moves to the Onboarding Complete stage, schedule an NPS email for 14 days later. Use the contact's first name, keep the email under 60 words, and include a 0–10 scale with a single follow-up text box.'

6 Tell Starch: 'Build a CSAT trigger. When an Intercom ticket closes, send the contact a one-question CSAT survey within 2 hours. Score it 1–5. Log the score and any comment back to the HubSpot contact record.'

7 Tell Starch: 'Build me a score dashboard. Show every account's latest NPS, latest CSAT, open Intercom ticket count, account tier from HubSpot, and renewal date. Let me filter by accounts renewing in the next 90 days and sort by lowest NPS first.'

8 Tell Starch: 'Add an alert: when any NPS response is a 6 or below, or any CSAT response is a 2 or below, post to #cs-alerts in Slack with the account name, score, verbatim response, deal stage, and the name of the CSM who owns the account.'

9 Review the detractor list weekly. The dashboard surfaces accounts by renewal date so you're not triaging randomly — the account renewing in 30 days with a 5 NPS is always at the top.

10 Use the verbatim response data to build a recurring prompt: 'Summarize the last 30 days of NPS and CSAT verbatims. Cluster the themes and tell me which 3 issues came up most often.' Run this before every team standup.

11 When a pattern emerges — say, 6 detractors all mention slow response times during onboarding — tell Starch: 'Flag all accounts in the Onboarding stage that haven't received a check-in email in the last 10 days.' Act before the survey tells you there's a problem.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

Q1 2026 NPS cycle — 250-account B2B portfolio

Sample numbers from a real run

Ridgeline Logistics (renews April 30)	6
Fenway Data Co (renews June 15)	9
Anchor Ops (renews May 1)	5
Clearpath Medical (renews July 10)	8
Stonemill Agency (renews April 15)	4

In January your team sent 48 NPS surveys triggered automatically at the 14-day onboarding mark — no manual exports, no follow-up reminders needed. Response rate came in at 62%, versus the 30% you were getting when surveys went out manually weeks late. Of the 48 responses, 5 were detractors (score 6 or below). Starch pushed all 5 to #cs-alerts in Slack within minutes of the response arriving. Stonemill Agency scored a 4 and noted 'we still don't know how to use the reporting module' — their renewal is April 15, two weeks out. Because the alert fired the same afternoon the survey closed, you had time to schedule a training call, fix the gap, and keep the renewal. Without the automation, that response would have sat in a Typeform dashboard until someone remembered to check it. Anchor Ops scored a 5 with a comment about slow ticket response; Starch's CSAT data showed their last three tickets averaged 19 hours to first response in Intercom, which confirmed the problem wasn't perception — it was real. You fixed the routing rule and followed up directly. Both accounts renewed.

Measurement

How you'll know it's working

NPS by account tier (SMB vs mid-market) tracked monthly

CSAT score by ticket category (onboarding, billing, product bug) to identify where your process breaks

Detractor-to-churn conversion rate — how many sub-7 NPS accounts churned in the following 90 days

Survey response rate by send trigger (post-onboarding vs post-ticket) to see which touchpoint gives you more signal

Time from detractor response to CSM outreach — your goal is under 4 hours

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Gainsight or ChurnZero

Both do this well, but they start at $30K–$60K/year and require a CS-ops person to configure health scores and workflows — not realistic for a 3-person team on a startup budget.

Delighted or Medallia

Good at collecting scores but the data lives in yet another silo; you still have to manually connect NPS back to HubSpot deal stages and Intercom ticket history to make it actionable.

Typeform + Zapier + HubSpot

This is probably what you're doing now. It works until a Zap breaks silently, someone changes a HubSpot field name, and you spend an afternoon debugging instead of calling accounts.

HubSpot Service Hub surveys

Native integration with your CRM is a real advantage, but the survey logic is limited, CSAT-to-Slack alerting requires a paid Operations Hub tier, and you can't build a custom health-score view across ticket data plus deal stage without custom reports that are annoying to maintain.

On Starch RECOMMENDED

One platform — crm, customer support agent all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Does Starch actually send the survey emails, or does it just trigger them through another platform?

Starch sends them directly through Gmail, which it connects to and syncs on a schedule. The emails come from your team's actual Gmail address — not a no-reply domain. This matters for response rates; customers are more likely to reply to an email that looks like it came from their CSM.

We use Intercom for support tickets. Can Starch detect when a ticket closes and trigger a CSAT send automatically?

Yes. You connect Intercom from Starch's integration catalog and the agent queries it live. When a ticket status changes to closed, the automation fires the CSAT send within whatever window you specify. You tell Starch how long to wait and what the email should say — it handles the rest.

Where do the survey scores live? We need them in HubSpot, not locked in Starch.

You can configure Starch to write scores back to HubSpot contact or company records directly. Starch syncs your HubSpot data on a schedule and can push updates back. Your CSMs will see NPS and CSAT on the account record without leaving HubSpot.

Is Starch SOC 2 certified? We have customers who will ask.

Not yet — Starch is not currently SOC 2 Type II certified. If that's a hard requirement for your procurement process today, it's worth knowing upfront. It's on the roadmap.

We only have 250 accounts. Is this overkill for our size?

250 B2B accounts with a 3-person team is exactly the size where manual survey operations break. You're too big to do it by hand without missing responses, and too small to justify a dedicated platform that needs a CS-ops person to run it. The setup here is a few hours, not a quarter-long implementation.

Can we segment NPS results by account tier or product line?

Yes. HubSpot syncs your company and deal data including whatever custom properties you use for tier or product. Tell Starch: 'Build a dashboard that breaks NPS scores down by company tier and renewal quarter.' It builds the view from the data you already have.

What about the Customer Support Agent app — can that help us respond to detractors faster?

The Customer Support Agent app is currently in development. When it launches, it will handle first-response to common support tickets automatically, which would reduce the CSAT problems that come from slow ticket response times. You can request beta access now to get notified when it's available.