Service Hub Onboarding.
More than a ticket inbox.
Tickets get answered, and that's where it stops: the customer portal unused, the knowledge base stale, SLAs theoretical, survey data nobody trusts. That is L2 for Service Hub — and where 70% of the value goes uncollected. We advise on how it should be set up, then build the majority of it live with your team. Diamond Partner, strategy-led, done-with-you.
Service Hub Onboarding is a Layer 03 service.
Every service we offer maps to one of four layers. Service Hub Onboarding sits in the Kernel — the layer that owns revops & hubspot admin.
A support operation, not an inbox.
The standard Service Hub deployment we walk into: tickets created, inbox mostly working, team responding. The customer portal is unused. The knowledge base has 12 articles, four out of date. SLAs are theoretical. The CSAT survey goes out, occasionally. Reporting exists but nobody trusts the categories.
Our model flips HubSpot's default. Their direct onboarding is consultative coaching — they teach, your team builds between tickets. We advise on how Service Hub should be set up, do the slow work off-call, then spend half the engagement building live with your agents. A goal-based client portal carries intake, prep tasks, and recordings so live time goes to strategy and building.
Service Hub rewards the model three ways. A ticket pipeline modeled correctly handles 10x the volume with the same headcount; one modeled to defaults produces SLA misses and a team that hates the tool. Customer portals only work when they're alive — built with the KB and self-serve workflows that actually deflect volume. And SLAs are operating discipline, not configuration: designing a structure your team can meet (and that escalates when they can't) is a strategy conversation, not a checkbox.
Service Hub is part of the Kernel layer for customer operations — and the substrate the Breeze Customer Agent runs on once your knowledge base and routing are exposed correctly. Breeze configuration is the natural next step.
The process.
Strategy · 1 session
Recommendations, not how-to. Support process mapping, ticket pipeline and stage design, channel strategy, base SLA policy, knowledge base taxonomy, customer portal strategy, routing logic, and CSAT/NPS/CES survey strategy. Enterprise adds playbook design, multi-team partitioning, skills-based routing, conditional and escalation SLAs, and conversation intelligence. You keep the advisory artifact.
Build for you · off-call, async
Heads-down, off-call: help desk and inbox setup, channel connection, ticket pipeline scaffolding, base SLAs, customer portal, knowledge base structure, surveys, base automation. Enterprise adds conditional and escalation SLA configuration, playbook scaffolding, custom objects, and one primary integration.
Build with you · 2 workshops Pro / 3–4 Enterprise
Half the engagement, deliberately. A ticket pipeline with automation built live, a base SLA and the customer portal, a routing workflow, a KB article and structure, and a feedback survey. Enterprise adds a playbook, a conditional or escalation SLA workflow, skills-based routing, and conversation intelligence.
Training · 1 session · recorded
Role-based and capped at this tier. Agent-facing: inbox, tickets, knowledge base, customer portal. Enterprise adds a manager and admin session on advanced SLAs, playbooks, and reporting. Additional training rolls into the retainer.
What "done" looks like.
Pro runs 2–3 weeks across 4 meetings; Enterprise runs 5–7 weeks across 6. Build-for-you is async, so live time goes to strategy, workshops, and training.
Things people ask before booking.
HubSpot says onboarding is required — can we buy it from you instead?
Yes. HubSpot requires onboarding on every Pro and Enterprise subscription, and a Diamond Partner delivering it satisfies that requirement. Taking our onboarding waives HubSpot's fee entirely — you never pay both. Same anchor price ($1,500 Pro / $3,500 Enterprise), but you get a build instead of coaching.
How is this different from HubSpot's own onboarding?
HubSpot's direct onboarding is consultative coaching: setup guidance, bi-weekly check-ins, homework for your team. Ours is strategy-led and done-with-you: we advise on the architecture, do the slow work off-call, and spend half the engagement building live with your agents — pipeline, portal, KB, and SLAs that exist by the time training starts.
What's not included?
Imports that need processing, transformation, cleansing, or deduplication (scoped as Data Hub or a dedicated data SOW); programmable workflow actions and webhooks (they require Data Hub); integrations beyond standard email and chat; knowledge-base content writing at scale — we build the structure and demonstrate the pattern; and training beyond the session caps, which rolls into the retainer.
What do we save by bundling hubs or committing to a retainer?
The foundation layer is built once, not per hub — so two or more hubs take 10% off the stacked total, and the full suite takes 20%. Sign onboarding alongside a 12-month $2,000/mo fractional admin retainer and the package takes 20% off: Service Hub Pro drops from $1,500 to $1,200, Enterprise from $3,500 to $2,800.
Can you deploy the Breeze Customer Agent alongside this?
Yes — through the Breeze AI add-on ($3,500, available with any hub onboarding). The Customer Agent is the most concrete Breeze use case for service teams: grounded in the knowledge base we structure during onboarding, deflecting volume across channels. The combined engagement runs efficiently because the kernel work supports the agent work directly.
See how service hub onboarding fits into The Kernel.
Book the Diagnostic and we'll whiteboard your support operation against the kernel in a single 90-minute session. You leave with a recommendation: Service Hub onboarding, a lighter cleanup, or different work first.