Deck

HubSpot Guide9 min read

How to Turn HubSpot Notes, Tickets, and Deals into Product Insights

Last updated: · By Matt Teixeira, Founder and CEO

On this page
Short answer

To analyze customer feedback in HubSpot for product insights, export the text from tickets, notes, call transcripts, survey comments, and closed-lost reasons, then group it into recurring problems. Join each problem to its HubSpot company ID and rank it by how many paying companies raise it, not by how often it was said. HubSpot's reports and Breeze AI can count feedback and label it with categories you define. Finding the problems nobody has named yet takes an export and an AI model, or a feedback tool that reads the text.

Key Takeaways

  • Treat HubSpot as your revenue key, not your feedback source. Its real value is telling you which accounts sit behind each problem.
  • Start with closed-lost reasons and deal notes. They're short, already summarized by sales, and tied to a deal amount.
  • Use Breeze to label, not to discover. Data Agent sorts records into categories you write, so it never surfaces a problem you didn't list.
  • Annual revenue is the wrong field. In HubSpot it is the customer's own company revenue, not what they pay you.
  • Deck's HubSpot integration adds context, not text. It ties feedback from your other sources to HubSpot Companies and Contacts so you can filter Themes by their properties.

What Customer Feedback Lives in HubSpot?

Feedback sits in five places, each with a different way out. Tickets and surveys export cleanly; notes hold the best material and are the hardest to extract.

Where it livesWhat you find thereHow to get it out
TicketsBugs, how-to confusion, and workaroundsExport from the Tickets index page
NotesSales objections, QBR summaries, "they'd sign if we had X"Activities report, engagements API, or a marketplace app
CallsThe customer's own words from demos and check-insCalls export for call records; HubSpot has no bulk transcript export, so pull transcripts through the API
Feedback surveysNPS, CSAT, and CES scores with a free-text reasonSurvey responses, on Service Hub Professional or Enterprise
Deal propertiesClosed-lost reasons and "missing feature" fieldsExport from the Deals index page

If you only have an hour, export closed-lost reasons and deal notes from the last two quarters. You'll see which missing features cost you deals before you open a single ticket.

What Can HubSpot Do with Feedback on Its Own?

HubSpot counts and labels feedback well, but it doesn't group free text into themes you haven't defined.

  • Reports: Count tickets by category or pipeline and split survey scores by any company property.
  • Feedback surveys: NPS, CSAT, CES, and custom surveys, with response analysis on Service Hub Professional and Enterprise (HubSpot Knowledge Base). Professional lists at $90 per seat per month billed annually, or $100 monthly (HubSpot pricing).
  • Breeze Data Agent: Custom prompt, Research, and Fill Smart Property workflow actions, on Professional or Enterprise with HubSpot Credits. Research reads a record's properties or up to five recent call transcripts; Custom prompt sees only what you insert, up to 3,000 characters (HubSpot Knowledge Base).
  • Buyer intent signals: The Pain Point Mention signal, added in June 2026, reads deal emails, notes, and call transcripts to help sales find accounts, not to rank a roadmap (HubSpot Community).

The most useful native setup is a labeling workflow. Create a dropdown ticket property called Product area with 8 to 15 values. Then add a ticket workflow that runs a Custom prompt on the subject and description and writes the answer to that property with an Edit record action.

A standard report now shows tickets by product area and lifecycle stage. The catch: new problems land in Other, where nobody looks. As a rule of thumb, once Other passes about 15% of tickets, rework your list with a feedback taxonomy.

How Do You Export HubSpot Notes and Tickets for Analysis?

Export properties from the index pages, and get notes through a report or the API. Record exports include property values and associations, but not notes or other activities (HubSpot Knowledge Base).

  1. Tickets and deals: On the index page, pick a view, click Export, and use Customize to add the description and associated company. Choose CSV, the only format that includes all associated records.
  2. Notes: Build a custom report on Activities, filter to notes, add the associated company, and export. For full history, use the engagements API or a marketplace export app.
  3. Clean the file: Keep one row per piece of feedback, with text, date, source, contact email, and company ID. Drop signatures and logistics such as "left voicemail," but never the company ID: it is how revenue comes back in.

How Can Product Teams Use HubSpot Notes and Tickets to Prioritize the Roadmap?

Group the text into problems, then score each one by the companies behind it. Three company fields are enough to start: lifecycle stage, a revenue field, and a renewal date if you track one.

  • Count companies, not mentions. A champion who opens ten tickets is still one company, so dedupe on company ID before you rank.
  • Pick the right revenue field. HubSpot defines Annual revenue as "the actual or estimated annual revenue of the company" and Total revenue as "the total value of deals closed with the company" (HubSpot Knowledge Base). Total revenue shifts with how you log renewals, so a finance-owned ARR property beats both.
  • Keep customers and prospects apart. Lifecycle stage separates "customers want this" from "deals we lost without it." Mix them and one large lost deal can outrank a renewal at risk.

A worked example (illustrative numbers). Say last quarter's tickets and deal notes produce 140 mentions of slow report exports and 60 of missing SSO. By mentions, exports win easily.

After deduping, exports come from 9 customer companies and SSO from 14, and 4 of those 14 renew in the next six months. SSO also appears in 3 closed-lost deals. It is the stronger case, and you can name every account behind it.

To total revenue per request, see the best tools to prioritize feature requests by revenue. For a scoring model that caps each account's ARR, see why feature voting fails.

How Does the Deck HubSpot Integration Work?

Deck uses HubSpot as context, not as a feedback source. Deck groups insights from tickets, calls, interviews, surveys, and Slack into Themes, and HubSpot tells it which company said each thing.

  • Access: Read-only access to contacts, companies, deals, and properties (Deck integrations). Deck never writes to HubSpot.
  • Fields: Any standard or custom Company and Contact property, such as Lifecycle Stage, Industry, or a health score. Deck stores only customer and company IDs and reads values when you filter (Deck HubSpot docs).
  • Matching: Feedback links to contacts by email and source IDs, so your support and call tools need to capture an email (Deck Contacts docs).

To connect it:

  1. An organization admin opens Settings → Integrations → HubSpot and authorizes Deck with OAuth.
  2. Select the Company and Contact fields you want to filter by.
  3. On Themes or a theme page, click the filter icon, choose HubSpot, and stack filters with operators such as equals and greater_than. In the example above, Lifecycle Stage equals customer would show which customer companies sit behind the SSO Theme.

To reuse a filter across Themes, Insights, and NPS, save it as a segment; segment rules can match a HubSpot company field (Deck segment workflow docs). The define segments playbook covers setup.

Limitations:

  • Plan: CRM integrations need the Business plan, at $249 a month or $199 billed annually.
  • No ticket or note import: The integration doesn't bring in HubSpot ticket, note, or call text. To analyze it in Deck, upload a CS Ticket or Feedback CSV of up to 10 MB with the requester email mapped (Deck CSV import docs). If support runs in Intercom or Zendesk, or calls in Gong, connect those natively.
  • Filters, not totals: Deck filters by HubSpot Company and Contact properties, not deal properties such as deal stage, and doesn't add up revenue per Theme.

Which Other Tools Work with HubSpot Feedback?

Choose by where requests get captured. If reps log requests in HubSpot, Canny, Aha! Ideas, and Savio capture them from the record and roll up deal or revenue value per idea. If requests hide in tickets, calls, and Slack threads nobody tags, you need a tool that reads the text.

ToolWhat it does with HubSpotPlan needed (USD)
HubSpot nativeSurveys, reports, and Data Agent labelingProfessional or higher, plus HubSpot Credits for Breeze (source)
CannyAdds insights to ideas from contact, deal, and company records; a linked deal's amount becomes the opportunity valueBusiness, custom pricing (source)
Aha! IdeasCreates or links ideas from company, deal, and ticket pages, with total deal value per ideaAdvanced, $59 per user per month billed annually, 3-user minimum (source, pricing)
SavioLogs feedback from HubSpot and sorts requests by MRR or deal revenueBusiness, $249 a month billed annually (source, pricing)
Productboard for BreezeSearches Productboard insights from Breeze AssistantFree app; Productboard billed separately (source)
DeckRead-only HubSpot context for feedback from every other sourceBusiness, $249 a month or $199 billed annually

If your evidence lives in tickets, calls, and Slack, Deck reads that text directly. You can start on Deck's Free plan and move to Business when you're ready to connect HubSpot.

Frequently Asked Questions

Partly. On Professional and Enterprise plans with HubSpot Credits, Breeze Data Agent workflow actions can read a record's properties or recent call transcripts and write a label to a property. They sort feedback into categories you define but don't discover new themes.

Not from a standard record export, which leaves out notes and other activities. Export a custom report built on Activities, use the engagements API, or install a marketplace export app. Include the associated company so you can join notes back to revenue.

Yes. Feedback surveys cover NPS, CSAT, CES, and custom surveys, with response analysis on Service Hub Professional and Enterprise. The product insight sits in the free-text reasons, which you still need to group into themes.

Not Annual revenue, which is the customer's own estimated company revenue. Total revenue sums deals closed with the company and works in a pinch, but a finance-owned ARR property on the company record is more reliable.

No. The HubSpot integration reads Company and Contact properties to enrich and filter feedback from your other sources. To analyze HubSpot ticket or note text in Deck, export it and upload it as a CSV with the requester email mapped.

Sources

Sources checked November 2, 2026.