Your support team is answering the same questions every week.

They know it. You probably know it too. But nobody has time to sit down, identify which questions keep coming up, write clean answers, and publish them somewhere customers can actually find them.

That last part is the problem. The knowledge exists, it's just locked inside closed tickets.

This hack extracts it in about 20 minutes, using a CSV export from HubSpot and a prompt you can copy straight from this post.

Why This is Worth Doing

Every ticket your team resolves manually is a ticket that could have been prevented.

The benefit nobody talks about: published FAQ content ranks. HubSpot's Knowledge Base articles are indexed by search engines, which means a well-written answer to "how do I change my billing details" doesn't just deflect tickets, it brings in organic traffic from customers searching that question before they ever become a support problem.

The data to build this content is already sitting in your HubSpot portal. You just need to get it out.

How to Set it Up

Step 1: Export Your Closed Tickets

Go to Service > Tickets in HubSpot.

Switch to the list (table) view if you're not already there. Now apply two filters:

  • Ticket status: Closed
  • Create date: Last 30 days

This scopes the export to resolved tickets from the past month - recent enough to be relevant, broad enough to show real patterns.

Before exporting, make sure these columns are visible in your view:

  • Ticket name/subject
  • Ticket category (if you use it)
  • Create date
  • Close date
  • Ticket owner
  • Associated contact or company (optional but useful)

In the top right, click Export. Select CSV as your file format, then choose whether to include only the columns in your current view or all properties. For this exercise, the columns above are all you need, don't export everything or you'll be sorting through noise.

HubSpot will email you a download link. It usually arrives within a couple of minutes.

Step 2: Drop it into Claude or ChatGPT

Open the CSV. Open Claude or ChatGPT. Upload the file and use this prompt:

"Group these support tickets by topic. Count each group. Write a one-paragraph FAQ answer (under 50 words) for each topic that would have prevented the ticket. Flag any topic with 5 or more tickets as high priority. Output as a table."

What comes back is a table with four columns: topic, ticket count, a draft FAQ answer, and a priority flag. The whole thing takes about 30 seconds to generate.

A few things make this prompt work well. Grouping by topic means the AI clusters tickets thematically rather than treating every subject line as a unique issue. Capping answers at 50 words keeps them useful - short enough to scan, specific enough to actually answer the question. The 5-ticket threshold is a practical triage filter: high-priority topics are the ones your team is fielding multiple times a week, which are the same ones customers are searching for online.

Step 3: Read the Output

You'll typically find that three or four topics account for the majority of your ticket volume.

That's not surprising, most support queues follow a power law distribution where a small number of issues generate most of the load. What changes when you can see it in a table is that you now have a prioritised publishing list, not a vague sense that "billing questions seem common."

Look for two things specifically:

The high-priority flags. Any topic with five or more tickets in 30 days is generating at least 60 tickets a year. If there's no self-service answer published anywhere, that's a predictable cost you're choosing to absorb manually.

The quality of the draft answers. The AI writes from the ticket subjects and categories, not from the actual ticket content, since those are rarely in the export. The drafts will be directionally correct but will need a review pass from someone on your team who knows the actual resolution. Don't publish them raw.

Step 4: Publish the Top Answers

You have two natural places for this content: your HubSpot Knowledge Base, or an FAQ section on your website.

HubSpot Knowledge Base (available in Service Hub Professional and Enterprise) is the right home if you want articles searchable inside your chat widget, accessible to your support team while they're inside tickets, and potentially surfaced automatically by Breeze Customer Agent when it handles inbound queries. Go to Service > Knowledge Base > Create Article, paste in the FAQ answer, write a descriptive title that mirrors the question a customer would actually type, and add a meta description and URL slug before publishing. HubSpot indexes these articles externally, so they can rank in search.

A website FAQ page is the right home if you want the content public-facing and optimised for organic search from the start. Either way, start with the high-priority topics. The rest can follow.

One practical note: publish the content first, worry about the perfect format second. A published 50-word answer that's 80% right beats a beautifully structured article that's still in draft three months from now.

Run This Monthly

The value of this hack compounds when you run it on a schedule.

Once a month, export the previous month's closed tickets and run the same prompt. You're looking for two things: new topics appearing in the high-priority category, and existing published topics that are still generating tickets, which means either the answer isn't easy enough to find, or it's not answering the actual question well enough.

That second signal is important. A knowledge base that nobody uses isn't a support tool. It's a document library. The ticket data tells you whether your published content is actually doing its job.

What to Do With What You Find

If this surfaces a deeper problem, ticket categories that suggest a product or onboarding issue, volume patterns that point to a process gap, or a knowledge base that needs a full rebuild rather than a few new articles, that's the kind of work we dig into at Neighbourhood.

We're a Diamond HubSpot Partner and we've helped a lot of Service Hub customers turn a reactive support operation into one that actually scales. If your support queue is running you rather than the other way around, get in touch.

Talk to us about your HubSpot setup →

Stay in the Loop

If you want more hacks like this one, practical, no-fluff, built for teams who actually run HubSpot day-to-day. Here's where to find us:

Ops Intel, our newsletter for HubSpot admins and RevOps teams, lands in your inbox with exactly this kind of content. No padding, no roundups of stuff you've already seen. Subscribe to Ops Intel →

We're also on Facebook and YouTube if you'd rather watch someone click through it than read about it. Follow us there for more updates.


Happy HubSpotting!