Published November 2026. Topics is a HubSpot public beta as of this writing, so screens and behavior may change.
I'm in the middle of a HubSpot build for a nonprofit right now, and it started with a question I bet you've asked too: "Can HubSpot read the email and send it to the right person automatically?"
Their shared general inbox did a lot of jobs. Emails came in about program questions, mentorship and volunteering, sponsorships and partnerships, and, of course, spam. Every one of those needs a different human on the other end.
Then we found the real problem in their portal. The channel's routing rule was assigning new emails to an app account tied to a deactivated person. Not a human. Emails were landing, technically getting assigned, and nobody owned them.
I was like, that's no good at all. And I told them, "We got you. We'll figure out a solution!"
So the goal got simple: hand-deliver every email to the right human.
The Short Answer
- Inbox routing rules can't read the subject or body, and in our client's portal, conversation workflow filters couldn't either.
- Topics (public beta, Service Hub Professional and Enterprise) has HubSpot's AI classify each conversation into properties like Primary topic. In our client's portal, a conversation-based workflow could branch on them and assign the owner.
- A None met branch makes sure a human sees everything else.
Below: the two dead ends we hit, the workflow we built and the gotchas to dodge.
Why Routing Rules and Workflow Filters Fall Short
Dead End One: Inbox Routing Rules
First stop: the inbox. Team email routing can assign conversations to specific people or teams, the contact owner or the AI customer agent.
What's missing? Any condition for the subject line, a keyword or the body. Routing rules decide who gets the email, not what it's about. They could fix our client's "nobody owns it" problem, but only by sending everything to one person. And the burden shouldn't land on one person.
Dead End Two: Conversation Workflow Filters
Next stop: conversation-based workflows. Surely a workflow can check the subject line? Not quite. In our client's portal, the Conversation object's message properties were dates and "last message from visitor." Nothing reads the subject line or body, so you can't build "if the email mentions sponsorship, send it to this human."
So we had a who without a what. That's when we found the feature hiding in plain sight.
The Fix: HubSpot Topics (Public Beta)
Topics is a public beta in Service Hub Professional and Enterprise (the knowledge base still says Beta). You turn on topic tracking under Settings > Data Management > Topics.
Once it's on, HubSpot's AI classifies each conversation and writes the results to properties:
- Primary topic
- Primary topic drill-down 1 and Primary topic drill-down 2
- All topics mentioned
Here's the thing that changed everything: in our client's portal, workflows could filter and branch on those properties.
Think of It Like a Mailroom
Picture an old-school mailroom with two people. The first opens every envelope, reads it and stamps it: sponsorship, volunteering, program question, spam. The second never opens anything. They just read the stamp and drop the envelope in the right box.
That's the whole system. The AI stamps. The workflow sorts.
Why the Default Topics Didn't Fit
HubSpot's default topics include Billing & Payments, Bug Report and Other Inquiry. Those fit a software support team, not a nonprofit fielding program, mentor and sponsor emails.
In our client's portal, "Other Inquiry" had caught 96 conversations in 90 days. That's the AI telling you, plainly, "I don't have a stamp for this."
Writing Custom Topics the AI Can Actually Use
You can create custom topics with a name and a description. In our client's portal, the form allowed up to 50. HubSpot's help article doesn't list a limit, so check yours.
The description is what the AI matches against, so write it like instructions, not a label: what belongs, the key phrases humans use and what doesn't belong. Here's the shape of one (a made-up example, not our client's):
Volunteer and Mentor Inquiries: Emails from people who want to volunteer their time or mentor someone. Key phrases include "volunteer," "mentor," "give back" and "how can I help." Doesn't include requests to sponsor, donate or partner as an organization.
In our client's portal, the existing group we used told the AI to prefer a specific topic over Other Inquiry, which is exactly what you want. Group names in the beta vary (HubSpot's help article lists Product Areas, Voice of Customer and General Support), and a brand-new custom group we created didn't show up in the topic form, so stick with an existing group.
And the good news? Our custom topics showed up as workflow filter values within minutes of creating them.
How We Built the Routing Workflow for Our Client
Step 1: Create a Conversation-Based Workflow
Go to Automation > Workflows, create one from scratch and choose Conversation as the object.
Step 2: Set the Enrollment Criteria
We used four filters, all joined with AND:
- Primary topic is known
- Inbox is [your inbox]
- Conversation status is Open
- Create date is less than 30 days ago
That last one is a rolling window, so only recent conversations enroll.
Step 3: Add One Branch per Topic
Add an AND/OR branch with one path per custom topic. In our test, the single-property branch wouldn't save custom topic values, but the AND/OR (filter) branch did. Start there.
Step 4: Assign the Conversation Owner
In each branch, add the Assign conversation owner action, pick the target inbox and the owner. Build it once, then clone it into each branch and change only the owner.
Per HubSpot's docs, only teammates who can access the inbox and have visited it at least once appear in the owner list.
Step 5: Build a Safety Net for Everything Else
For our client, the None met branch sends an internal email notification to a triage owner with:
- The contact's name and email
- A link to the contact record, built from the Record ID
- A link to the conversation, built from the Thread ID
- The topic the AI picked
If the AI's stamp doesn't match a box, a human still sees it.
The Gotchas We Hit (So You Don't Have To)
| Gotcha | What Happens | What to Do |
|---|---|---|
| "Last 30 days" can skip today | In our client's portal, it skipped today's emails. | We used "is less than 30 days ago." HubSpot notes that "is less than [x] days ago" filters are checked at the start of the day, so test same-day enrollment before you rely on it. |
| Other inboxes get pulled in | Without an Inbox filter, the workflow can grab other inboxes' conversations, and Assign conversation owner moves them into the target inbox. | Always filter by inbox. |
| Closed conversations come back to life | Assigning a closed conversation reopens it. | Filter for Open, or you'll resurrect a pile of old threads. |
| Owners get assigned no matter what | Assign conversation owner ignores availability and capacity, and doesn't update an associated ticket's owner. | Plan for that if your team works out of tickets. |
| Routing rules and workflows collide | If the channel's routing rule assigns on arrival, the workflow may find an owner set. | Pick who's in charge: turn off automatic assignment on the channel so conversations arrive unassigned and let the workflow route, or let the workflow override the rule. |
| Re-enrollment refires | In our testing, with re-enrollment on, "Primary topic is known" fired every time the topic changed value. | Leave it off until you've seen how stable labels are. |
| Skipping the test | HubSpot says no actual actions run in test mode. At turn-on, you choose whether to enroll existing matches. | Use the workflow Test feature first, then start with new conversations only. |
| Not every conversation gets a topic | HubSpot says some won't: automated or unreadable messages, very recent ones not yet processed, unclear matches and accounts past their monthly conversation-processing limit. Sensitive data accounts don't get Topics. | One more reason for the safety net. |
What About Cost?
Here's what HubSpot's pages said on November 9, 2026. Rates change, so check yours.
- Topics: no rate on either the credits rate sheet or the flexible seats-and-credits rate sheet. HubSpot says beta features "may consume credits in the future" and aims to give 30 days' notice.
- AI in a workflow: 10 credits to "Execute one AI action in a workflow" on HubSpot's Credits Rate Sheet.
- Assign conversation owner: HubSpot's Workflows FAQ doesn't list it among credit-using features. But HubSpot's credits guide for flexible seats-and-credits pricing says "all workflow actions except branches, delays, and go-to actions" use credits: 3 each for the first 10,000, less at higher volumes, unless a workflow actions capacity pack covers them. Your safety net email is a workflow action, too.
- Routing to the customer agent instead: 50 credits to "Resolve one conversation (text-based channels)."
HubSpot's Topics article says an account can reach its "monthly conversation-processing limit," but doesn't give its size or say whether it's tied to credits.
Let Topics stamp. Let a standard workflow sort. Simple wins.
What We'd Tell Any Super Admin
If your shared inbox feels like a pile nobody owns, don't build the shiny new thing on a bad foundation. The data is your foundation. Fix it before you automate anything.
Then let the AI read and the workflow sort. That's how you get back to the goal we started with: hand-deliver every email to the right human.
So here's your next step. Open your shared inbox settings today and find out who, or what, your routing rule assigns to.
Going deeper? Read our HubSpot automation workflows guide for Super Admins. We covered topic reporting in Analyze Help Desk and Customer Agent Performance by Topic. And if you're the Super Admin holding it all together, the HubSpot Super Admin Workshop is live and virtual on January 8, 2027.
Let's Tune Up Your Inbox
Want every email in your shared inbox to land with the right human? Talk with Sidekick about a HubSpot inbox and automation tune-up. We'll look at your routing, your workflows and whether Topics fits, then help you build a system that supports your humans instead of overwhelming them.
Sources
HubSpot pages we checked on November 9, 2026:
- Use topics to analyze customer interactions
- Set up routing rules in the conversations inbox
- Assign a conversation owner in a workflow
- Test your workflow
- Create workflows (enroll existing records on activation)
- Set filter-based enrollment triggers (date filters checked at the start of the day)
- Manage HubSpot Credits (beta features and credits)
- Understand how to use HubSpot Credits (Flexible Seats-and-Credits Pricing), "All workflow actions except branches, delays, and go-to actions"
- HubSpot Product and Services Catalog, HubSpot Credits Rate Sheet
- Flexible Seats-and-Credits Pricing Supplement (rate sheet)
- Workflows FAQ (which workflow features use credits)
- HubSpot product update, Analyze help desk and customer agent performance by topic (status: Public Beta, Service Hub Professional and Enterprise), October 13, 2026
