Quick summary
HubSpot feedback surveys, the short answer: they are Service Hub's NPS, CSAT, CES and custom surveys. You build them under Service, then Feedback Surveys, and every response is saved on the customer's CRM record.
What you need: Service Hub Professional or Enterprise and an assigned Service Hub seat. Professional is $90 per seat per month billed annually, plus $1,500 onboarding.
Which one to start with: CES if you want feedback on each closed ticket, NPS if you want a regular read on the whole relationship, and a plan for what happens when a score is low.
HubSpot Feedback Surveys at a Glance
| Survey type | What it measures | Scale | Delivery | When it sends |
|---|---|---|---|---|
| Customer loyalty (NPS) | How likely the customer is to recommend you | 0 to 10, then a follow-up question | Email or a web page | One off or recurring, with reminders |
| Customer satisfaction (CSAT) | How satisfied they were with an interaction | A satisfaction rating | Email, chat or a web page | You choose the channel and audience |
| Customer support (CES) | How easy it was to get their issue handled | Seven points, Strongly agree to Strongly disagree | When a ticket closes, once per ticket | |
| Custom survey | Whatever you ask | Your question types, plus NPS or CSAT modules | Your choice | Your choice |
Plans: Service Hub Professional or Enterprise. Limits: up to 50 NPS, 100 CSAT and 100 custom surveys per account.
Before you build one, answer three questions:
Answer these first
- What do you want to learn? Loyalty across the whole account, or how one support interaction went. That picks the survey type.
- When should it send? At ticket close, after the fix ships, or on a schedule. The timing decides what the score actually measures.
- Who reads the low scores? Name a person and a deadline for every detractor and every "difficult" answer before the first survey goes out.
In this article
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
What Are HubSpot Feedback Surveys?
HubSpot feedback surveys are the survey tools built into Service Hub. You reach them by clicking More, then Service, then Feedback Surveys. HubSpot's knowledge base is clear about one requirement: you must have an assigned Service Hub seat to create feedback surveys.
The difference from a form or an outside survey tool is where the answers land. Each response is saved in the CRM as a feedback submission, connected to the contact who answered. HubSpot also creates survey response properties automatically, so a score can sit next to the contact's tickets, company and owner, and can trigger a workflow.
If you are still deciding whether Service Hub is the right help desk, our HubSpot Service Hub review covers the whole product.
Which Plan Includes HubSpot Feedback Surveys?
HubSpot's knowledge base lists Service Hub Professional or Enterprise for customer loyalty surveys and custom surveys, and HubSpot's own pricing guide lists customer feedback surveys among the Professional features. Some third-party guides say Starter includes surveys. Go by HubSpot's documentation and check your own portal before you plan around Starter.
| Service Hub Professional | Service Hub Enterprise | |
|---|---|---|
| Price per seat, billed annually | $90 per month | $150 per month |
| One-time onboarding | $1,500 | $3,500 |
| Feedback surveys | Yes | Yes |
Two permissions matter as well. Creating a survey needs a Service Hub seat. Sending one by email needs Marketing access with Edit and Publish permissions for the email tool, so check that the person building the survey has both. Our HubSpot Service Hub pricing guide breaks down the seat prices.
The Four HubSpot Feedback Survey Types
HubSpot NPS survey (customer loyalty)
The customer loyalty survey is HubSpot's NPS survey. HubSpot's knowledge base says respondents rate your company on a scale of 0 to 10, then answer a follow-up question based on their score.
You can send it by email or show it on a web page with the HubSpot tracking code. In the Frequency section you choose One off or Recurring, and for recurring surveys, how often it sends. A contact must meet the survey's criteria each time it goes out to receive it. Email versions can send an automatic reminder a set time after the first survey.
Use it for the relationship, not for one ticket. Send it to people at active customer accounts on a schedule, and read the comments as much as the score.
HubSpot customer satisfaction survey (CSAT)
The customer satisfaction survey asks how satisfied the customer was. HubSpot says you can send it by email or chat, or show it on any page that has your HubSpot tracking code installed.
Use it for a specific experience, such as onboarding or a support conversation, where you want a quick read on how it went.
HubSpot CES survey (customer support)
HubSpot calls its customer effort survey the customer support survey. It uses a seven-point scale from Strongly agree to Strongly disagree, and it is tied to tickets:
It sends when a ticket closes
You pick the ticket pipeline and the ticket status that send the survey. The pipeline needs a closed state.
You choose the delay
It can go out immediately after the ticket closes, or after a custom delay in minutes, hours or days.
One survey per ticket
HubSpot sends it only once per ticket. If a ticket reopens and closes again, no second survey goes out. Reminder emails are not supported for this type.
You choose who hears about responses
You pick the users or teams who are notified when a response comes in.
For a support team, this is usually the first survey worth turning on, because it rates the thing you control: how easy it was to get help.
Custom surveys
A custom survey lets you build your own questions. You drag question types from the left panel into the survey, mark any question as required, and add the standard NPS or CSAT question as a module. HubSpot's knowledge base lists custom surveys for Service Hub Professional or Enterprise as well.
Use a custom survey when the standard questions do not fit, for example a short survey after onboarding that asks about each setup step.
How to Set Up HubSpot Feedback Surveys
- 1
1. Check the plan, seat and permissions
Confirm you are on Service Hub Professional or Enterprise and that you have an assigned Service Hub seat. If the survey will go by email, confirm you have Marketing access with Edit and Publish permissions for the email tool.
- 2
2. Open Feedback Surveys and pick a type
Click More, then go to Service, then Feedback Surveys, and click Create survey. Choose Customer loyalty, Customer satisfaction, Customer support or a custom survey.
- 3
3. Choose the delivery method and recipients
Pick email, chat or a web page, depending on the type. For NPS, choose who receives it and whether it is one off or recurring, and check the estimated recipients count before you publish. For CES, pick the pipeline and the closed status that send it.
- 4
4. Set the timing and notifications
Set the delay and any reminder emails, and choose which users or teams are notified of responses. A short delay after a ticket closes gets answers from people who still remember the conversation.
- 5
5. Publish, then build the follow-up
Publish the survey. Then build the report and the workflow that act on low scores, covered in the next section, before the first responses come in.
If you want more control over when a survey sends, a workflow can send it instead of the survey's own trigger. Our HubSpot workflow examples include a workflow that sends a satisfaction survey when a ticket closes and skips tickets closed for inactivity.
Where HubSpot Survey Responses Go
Every response becomes a feedback submission in the CRM. HubSpot's developer documentation describes the same object: its feedback submissions API returns responses from NPS, CSAT, CES and custom surveys.
HubSpot also creates survey response properties automatically, and you can add your own. Its knowledge base lists three things you can do with them:
Segments
Build a list of contacts by their response, such as everyone who gave an NPS score of 6 or lower in the last quarter.
Workflow enrollment triggers
Start a workflow when a response comes in, for example to create a task or a ticket for the account owner when a customer is a detractor.
Reports
Report on responses in single-object or cross-object reports, for example average effort score by ticket owner, or NPS by company.
That last point is why the surveys earn their place on Professional. A score on its own is a number. A score next to the ticket, the owner and the account tells you where to look.
How to Read NPS, CSAT and CES Scores
NPS is the percentage of promoters (9 or 10) minus the percentage of detractors (0 to 6). Passives (7 or 8) count in the total but not in the subtraction, so the score runs from minus 100 to 100. Seventy promoters and ten detractors out of 100 responses is an NPS of 60.
CSAT is usually the share of positive responses: positive answers divided by all answers, times 100. Fifteen positive answers out of 25 is a CSAT of 60%.
CES on HubSpot's seven-point scale is easiest to read as the share of customers who agree it was easy, tracked by ticket owner and ticket category over time.
Report the response rate next to every score. A CSAT built on a handful of answers measures who felt strongly enough to reply. Our customer service metrics guide covers what each number does and does not tell you.
The Most Expensive Mistake: Surveying a Ticket That Is Still With Engineering
Picture a customer who reports that an export fails. The rep reproduces it, files it for engineering, replies "our engineers are on it," and closes the ticket. The CES survey goes out an hour later.
The customer answers while the bug is still there. If they rate it well, the score credits a fix that has not happened. If they rate it badly, the comment names a bug that is already filed, and nobody connects the two. Either way, when the fix ships three weeks later, the ticket is closed and nobody tells them.
Three habits prevent it:
Do not close tickets that are waiting on a fix
Move them to a waiting stage instead. The CES survey fires on a closed status, so a ticket that stays open until the fix ships is surveyed at the right time.
Read every low score's comment within a day
Use a workflow on the survey response properties to create a task for the ticket owner when a response is a detractor or says it was difficult. The comment often names the bug.
Close the loop when the fix ships
Tell the customer what changed, then survey. Our customer feedback loop guide covers the return trip step by step.
From Survey Feedback to Linear: HubSpot and Linear
For a B2B software company, the most useful low scores are about the product: a bug, a missing feature, a broken integration. That work happens in Linear, and HubSpot does not build a Linear integration, so the feedback stops at the ticket unless someone copies it over.
IssueLinker is a HubSpot Marketplace app for that step. It does not read survey responses. It works on the ticket the feedback lives on:
Create or link the Linear issue from the ticket
A card on the HubSpot ticket creates a Linear issue, pre-filled from the ticket and optionally drafted by AI from the conversation, or links an existing one. With customer requests turned on, the ticket's HubSpot company is attached to the issue as a Linear customer request, so engineering sees how many accounts asked.
Comments both ways
Notes on the ticket and comments on the issue sync in both directions with loop prevention, and edits and deletes follow them, so the rep and the engineer read the same thread.
Status back on the ticket
The Linear status is written to properties on the HubSpot ticket, including a Linear Issue Status Type of triage, backlog, unstarted, started, completed or canceled. Optional status emails tell the ticket owner, the ticket creator or both when the issue is done.
That status property is what fixes the timing problem above. A ticket-based workflow can wait until Linear Issue Status Type is completed, then send the survey, so the customer rates the fix rather than the promise. Our Linear HubSpot integration guide compares every way to connect the two tools.
Get survey feedback to Linear, and the fix back to the customer
IssueLinker creates the Linear issue from the HubSpot ticket, syncs comments both ways and writes the issue status back to the ticket. $39 per month flat, unlimited users, any HubSpot plan, 14-day free trial.
Which Survey Should You Start With?
It sends on its own when a ticket closes, once per ticket, and rates how easy it was to get help. Keep tickets that wait on engineering open, so they are surveyed after the fix.
Send it every quarter or half year to active customers, and route detractors to the account owner. Read the follow-up answers for product themes.
Use it after onboarding or a chat, where you want a quick read on how one experience went. Report the response rate next to it.
Who This Guide and IssueLinker Are Not For
This guide is written for B2B teams running support on HubSpot Service Hub, especially software companies whose hardest feedback ends up with engineering. If you run a large customer experience program with SMS, in-app or text analytics needs, a dedicated survey platform will do more than HubSpot's built-in tools.
IssueLinker is for teams that run support on HubSpot Service Hub and build in Linear, Jira or GitHub. It is not for teams whose support runs on Zendesk, Intercom or Front, since Linear connects to those natively, and it does not sync deals, contacts or custom fields between tools.


