How Do I Collect Feedback at Every Customer Touchpoint in HubSpot Service Hub?
Orchestrate CSAT, CES, and NPS across your journey—triggered by events, routed by workflows, and closed with a governance cadence in Service Hub.
Build an “always-on” system: map touchpoints; standardize a survey mix (**CSAT**, **CES**, **NPS**); instrument triggers (ticket closed, onboarding milestone, renewal, chat end, KB visit); and use **workflows** to target the right segment, prevent fatigue, and assign follow-up. Centralize results with contact/account associations and review a **closed-loop dashboard** weekly so insights turn into fixes—not just scores.
Every-Touchpoint Feedback Checklist
Journey map — Define moments that matter (onboarding, support, adoption, renewal, advocacy).
Survey mix — CSAT for interactions, CES for effort, NPS for relationship health; consistent scales.
Triggers & targeting — Event-based sends with segment rules and fatigue controls (e.g., max 1 survey/30 days).
Workflows & routing — Auto-create tasks, Slack alerts for low scores, and problem tickets for themes.
Closed-loop dashboard — Scores, response rate, themes, time-to-contact for detractors, and fix status.
Touchpoint-to-Survey Map (Starter Configuration)
| Journey Stage | Touchpoint | Survey Type | Trigger in Service Hub | Audience/Rules | Primary Goal | Owner |
|---|---|---|---|---|---|---|
| Onboarding | Milestone complete (e.g., first value) | CES | Custom property updated → workflow send | New customers, 1 time per milestone | Measure effort; remove friction | Onboarding Manager |
| Support | Ticket closed | CSAT + comment | Ticket status = Closed → post-case email | Exclude customers surveyed ≤30 days | Quality of resolution & agent coaching | Support Lead |
| Self-Serve | KB session | CSAT (thumbs up/down) | In-article widget; failed-search capture | All visitors; throttle by session | Content effectiveness & deflection | Knowledge Manager |
| Adoption | Feature usage threshold | CES (micro) | Event property crosses threshold → send | Active users; exclude admins | Ease of using key features | Product Ops |
| Relationship | Quarterly/biannual check-in | NPS | List-based cadence with throttling | Decision makers only | Loyalty & advocacy signals | CSM Leader |
| Renewal | 90–60 days pre-renewal | CSAT + “renew intent” | Deal stage enters Renewal → workflow | Active contracts; exclude escalations | Risk detection & save plays | Account Team |
Question Bank by Goal (Use These Prompts & Scales)
| Goal | Primary Question | Scale | Follow-Up/Branch | Where It’s Used |
|---|---|---|---|---|
| Interaction Quality (CSAT) | How satisfied were you with the help you received? | 1–5 (Very dissatisfied → Very satisfied) | What could we improve about this interaction? | Post-ticket email; chat end |
| Effort (CES) | How easy was it to complete your task today? | 1–7 (Strongly disagree → Strongly agree) | What made this easy/hard? | Onboarding milestone; feature usage |
| Relationship (NPS) | How likely are you to recommend us to a colleague? | 0–10 (Detractor/Passive/Promoter) | What’s the main reason for your score? | Quarterly/biannual cadence |
| Self-Serve Content | Did this article help you solve your problem? | Yes/No with thumbs | If no, what was missing or unclear? | Knowledge Base pages |
| Renewal Risk | How confident are you in renewing with us? | 1–5 (Not at all → Very confident) | What must we deliver to secure your renewal? | Renewal stage entry |
How to Run an Always-On Feedback Program in Service Hub
30-Day Implementation Sprint
- Map your journey & segments: Identify moments that matter and eligible audiences; define fatigue rule (e.g., 1 survey/30 days).
- Stand up CSAT/CES/NPS: Standardize scales and open-text prompts; localize where required.
- Instrument triggers: Ticket closed, milestone achieved, renewal stage, chat end, KB session/failed search.
- Automate workflows: Target lists, send surveys, suppress ineligible contacts, route low-score tasks to owners, and open problem tickets for themes.
- Publish dashboard: Scores, response rate, detractor follow-up time, theme counts, fixes shipped, and trend vs. last 30 days.
- Operate the loop: Weekly review to prioritize fixes; confirm follow-ups; update KB/macro; communicate improvements to respondents.
Frequently Asked Questions
Which survey should I use where?
CSAT for post-interaction, CES for onboarding/adoption tasks, and NPS for relationship health on a cadence—each with a short comment box.
How do I prevent survey fatigue?
Use workflow-level frequency caps (e.g., one survey per 30 days) and suppress customers with open escalations until resolved.
Who should get follow-up tasks?
Route by context: agent/owner for CSAT < 3, CSM for NPS detractors, Product/Content for recurring CES or KB themes.
Can I tie feedback to accounts?
Yes—associate responses to contacts, companies, and deals. Roll up to account health to inform renewal plays.
What metrics prove it’s working?
Rising response rate and CSAT/CES, faster detractor outreach, declining repeated themes, and renewal risk detected earlier.
Get in touch with a revenue marketing expert.
Contact us or schedule time with a consultant to explore partnering with The Pedowitz Group.