I'm learning what it is · 5 min read
What Service Hub is, and what changed here in 2026
You run Service Hub already, or you're deciding whether to, and you want to know what actually shipped this year before you trust a description of it.
If you have five minutes
- At the center of Service Hub is one thing: the ticket, sitting in a Help Desk queue, with a person or an agent working it.
- Everything else covered on the show this year is something HubSpot built to read that same ticket queue — scoring it automatically, generating knowledge from it, or suggesting what to do with the next one that looks like it.
What Service Hub is, in one screen
At the center of Service Hub is one thing: the ticket, sitting in a Help Desk queue, with a person or an agent working it. Everything else covered on the show this year is something HubSpot built to read that same ticket queue — scoring it automatically, generating knowledge from it, or suggesting what to do with the next one that looks like it. The Help Desk is the oldest, most-worked layer in this Hub, and it's also the layer Chris asked this door to lean into hardest.
Five things filed under this Hub right now
- Help Desk and tickets
- the queue itself: routing, macros, spam handling, board views, ticket automation messages. A substantial vein of 2026 activity in this Hub, and the one carrying the most features with no on-air take yet.
- Two scores read off ticket data
- Customer Experience Score (CXS) and Quality Assurance Score (QAS), both scored automatically off closed tickets rather than a survey.
- Two AI features that turn tickets into content
- the knowledge base agent, which drafts articles from ticket and email history, and customer agent's newer ability to generate FAQ-style knowledge straight from resolved tickets.
- Automatic similar ticket suggestions
- surfaces resolved tickets next to the one an agent is currently working.
- Customer Success Workspace and Customer Portal
- the relationship-level surfaces that sit above any single ticket; the material behind this door on them is thinner than on Help Desk itself (see "What we do not know yet," below).
What Chris asked this door to lean into
"Yes and more help desk" — Chris Carolan, ruling on this Hub, 2026-09-05
Read against the full 2026 feature list for this Hub, that steer points at a real vein: a substantial run of Help Desk-specific features that shipped this year carry no on-air take at all. They're not undocumented — every one has a title, a status and a first-covered date in the record — they just haven't had the show's own commentary yet. Here they are, named plainly rather than glossed over:
| Feature | Status | First covered (AOM) |
|---|---|---|
| Introducing Folders for Help Desk Views | live | 2026-06-02 |
| Create Your Own Ticket Automation Messages | public beta | 2026-06-03 |
| Close a Chat and Keep the Ticket Open in Help Desk | public beta | 2026-06-22 |
| Help Desk Conversation Expand All and Collapse All | live | 2026-06-15 |
| Support Macros | public beta | 2026-06-15 |
| Help Desk Board Layout Redesign | live | 2026-05-05 |
| Help Desk Board Redesign: New Card Settings | public beta | — |
| Help Desk Routing: Use Assignment Workflow | public beta | 2026-05-15 |
| New Conversation Routing Option: Use Assignment Workflow | public beta | — |
| Conversation Routing fallback to Customer Agent | public beta | — |
| Two Way SMS in HelpDesk & Inbox (Service SMS) | public beta | — |
| Bulk Unmark Spam in Help Desk | live | — |
| Help Desk: Searching Spam | live | — |
| Ticket Capacity Limits in Service Hub Professional | live | 2026-05-08 |
| Inline Screenshots Now Surface as Attachments in Help Desk | live | 2026-07-02 |
| Workforce Management in Help Desk | public beta | — |
| New Help Desk Composer Experience | public beta | — |
| Nested Teams Selectable for Default Team Email in Help Desk | no status recorded | 2026-05-13 |
A dash in the "first covered" column means the record carries no date for that update, not that nothing happened; that's stated honestly rather than guessed. "No status recorded" for the nested-teams feature is the same discipline: the live record's status field for that one is literally empty, not "beta" or "live" — worth confirming in your own portal rather than assuming either.
The two scores that read your ticket queue
Both Customer Experience Score (CXS) and Quality Assurance Score (QAS) work the same way underneath: instead of waiting for a survey a customer might never answer, they score every closed ticket automatically, reading tone and language against a fixed list of signals.
"And so what are the chances that AI, the AI tool set in HubSpot, is gonna miss positive stuff and over index on negative stuff." — Chris Carolan, on Track Customer Experience Score (CXS)
His full caution: the signal list is lopsided, a couple of positive factors against roughly a dozen negative ones, so an AI reading tone against a list shaped like that will miss positives and over-index on negatives, the same way a person would. His instruction was concrete — set your own business context and exclusions in the portal before you let the number drive a decision.
Credit: the full take — Chris Carolan, Track Customer Experience Score (CXS).
"Any score that's gameable gets gamed. AI just applies that truth at a scale humans never could." — Zach Hussion, on Track Quality Assurance Score (QAS)
Credit: the full take — Zach Hussion, Track Quality Assurance Score (QAS).
A status worth checking in your own portal.
The live record read on 2026-09-05 marks both CXS and QAS as live. But the takes that introduced them told a different story at the time: Chris's CXS take (aired 2026-07-31) said "if you run support on Service Hub Professional or Enterprise, get into the beta," and Zach's QAS take (aired 2026-08-05, last covered 2026-09-02) said plainly, "It's private beta, Service Hub Enterprise only, and the scoring categories, communication, tone, clarity and empathy, aren't customizable yet." Both readings are honest for the moment they were made — features move from beta to live over months. What's not established here is exactly when each one crossed that line, or whether your own portal's tier already has it. Check live, don't assume either date's answer still holds.
The two AI features that turn tickets into content
The knowledge base agent drafts knowledge base articles from ticket and email history (private beta, first covered 2026-08-18). Customer agent's newer capability goes further: it reads your resolved tickets specifically and drafts FAQ-style knowledge from them (public beta, first covered 2026-09-02).
"If you are using tickets in HubSpot, you almost certainly bought Service Hub to get them, which means this is an immediate win sitting in nearly every portal." — Chris Carolan, on the Knowledge Base Agent
Credit: the full take — Chris Carolan, Knowledge Base Agent.
"This is where you switch what the humans are responsible for." — Chris Carolan, on Customer Agent now generates knowledge from your ticket history
Credit: the full take — Chris Carolan, Customer Agent now generates knowledge from your ticket history.
Both features ship with a human-approval step before anything gets published — that's covered in full in the implementing door, since it's a decision to make before you configure either one.
Automatic similar ticket suggestions
In development as of its first covering (2026-08-31): resolved tickets get surfaced next to the one an agent is currently working, rather than the open-ticket-clustering the show initially assumed HubSpot had built.
"AI can excel at trend analysis, but not over a help desk nobody has been keeping clean." — Chris Carolan, on Automatic similar ticket suggestions in help desk
Credit: the full take — Chris Carolan, Automatic similar ticket suggestions in help desk.
Where to next
Where this comes from
- Chris Carolan on "Track Customer Experience Score (CXS)". the lopsided signal list and the instruction to set your own business context first; aired 2026-07-31, last covered 2026-09-02
- Zach Hussion on "Track Quality Assurance Score (QAS)". any score that is gameable gets gamed, and the tier and beta status as he named them; aired 2026-08-05, last covered 2026-09-02
- Chris Carolan on "Knowledge Base Agent". private beta, first covered 2026-08-18; the immediate-win argument for a portal already running tickets
- Chris Carolan on "Customer Agent now generates knowledge from your ticket history". public beta, first covered 2026-09-02; the human-approval step and who owns it
- Chris Carolan on "Automatic similar ticket suggestions in help desk". in development, first covered 2026-08-31; only as good as the Help Desk data already sitting there
- The Service Hub material pack, built 2026-09-05. the feature table above — title, status and first-covered date per record, from a live read of the HubSpot Updates object on 2026-09-05, with the published take quoted verbatim for every quote here
- Chris's ruling on this Hub, the nine-Hub walk, 2026-09-05. the steer this door was written to, in his own words: "Yes and more help desk"
What we do not know yet
- Customer Success Workspace and Customer Portal are thin in the material behind this door. The show's own take on Revenue Data and Reporting in the Customer Success Workspace (public beta, first covered 2026-08-18) exists and is sourced in the material pack, but this door leans into the Help Desk vein per Chris's own steer — a fuller Customer Success Workspace treatment is future work, not something invented here to fill space.
- Outside archive material is genuinely scarce. A search across every non-AOM show in the archive (1,402 episodes) found only three that touch this Hub's subjects at all. Two are title-only: Let's Build Daily — Unboxing Customer Success Workspace (2024-04-24) and Let's Build Workspaces in HubSpot with Danielle Urban — Unboxing the Customer Success Workspace (2024-09-16); the archive record for both carries no description or keyTopics, so they are named here as pointers, not summarized past their titles. The third was actually read: on The Road to UNBOUND (2026-07-22), Kyle Jepson made an economics argument about Customer Agent — "a real, calculable return, because roughly 70 percent deflection against a support team you already pay for is arithmetic" — framed as an AI-ROI comparison point, not a Service Hub feature explainer.
- Whether the "beta at first covering, live by the current read" pattern on CXS and QAS holds for other Help Desk features has not been checked feature by feature. It is flagged here for these two because their takes explicitly named a beta tier; the no-take features in the table above may or may not have moved the same way, and there is no on-air commentary to say.
Turning the Help Desk AI on, or stuck on who reviews what it writes?
Come walk through it on the show and we will work it out on air, weekday mornings.