Gracjan Kasprzyk
Gracjan Kasprzyk, HubSpot consultant

HubSpot Service Hub Implementation

Every ticket has an owner and a due date, with the customer’s history right next to it. Sales sees open issues before calling with an offer.

What companies come to me with

A shared inbox with no owner

Three people read the same email and each assumes someone else will reply. Or two reply, each saying something different.

Urgent issues surface by phone

Nobody knows how many requests have been waiting since yesterday until an angry customer calls.

An offer at the wrong moment

A rep calls about expanding the contract while the customer has waited a week for an answer on a complaint.

What I set up in Service Hub scope set in the workshop

Tickets

Every channel in one place

Email, chat and forms become tickets with a category, priority and owner. I move tickets from your previous help desk with their history.

Zendesk migration
Due dates

Response targets and escalations

Targets for first response and resolution, your team’s working hours and an escalation when a deadline passes.

Routing

Tickets to the right person

Routing by team and topic, saved replies for repeat questions and internal comments when a ticket changes hands.

Context

Customer history on the ticket

Service sees the customer’s deals and past tickets, and reps see their customers’ open tickets.

Self-service

Knowledge base and customer portal

Articles that answer the most common questions, and a portal where customers check the status of their own tickets.

AI

Customer Agent

A Breeze agent answers basic questions from the knowledge base and hands harder cases to a person.

AI implementation

How the implementation works

  1. 1

    Free consultation30 minutes

    You tell me which channels customers use to reach you and who answers them. I outline what service would look like in Service Hub.

  2. 2

    Pre-implementation workshop1.5-2 hour sessions

    We look at where requests come from, who handles them and where they get lost. Categories, ticket stages, response targets and a license recommendation go into the implementation document.

  3. 3

    Setup and dataPer the document

    I connect inboxes, chat and forms and set up routing, response targets and escalations. The most common questions become the first knowledge base articles.

  4. 4

    Training1.5-2 hour sessions

    Your service team practices on its own tickets, and sales learns where to see a customer’s open tickets.

  5. 5

    Ongoing supportOn demand or on a retainer

    After launch you reach out when you need something, or we agree on a fixed scope of work for each month.

Who you'll work with Gracjan Kasprzyk, Spectage

Gracjan Kasprzyk, Spectage

I am a HubSpot consultant. I work in HubSpot every day: I implement it, train teams and connect it with the rest of the company’s systems. My advice comes from what has worked across dozens of portals.

HubSpot portals
50+
New implementations and cleanups of existing ones
Migrations
15+
Full migrations from other CRMs
Teams
Dozens
Sales, marketing and service teams trained
Consulting
Hundreds
Hours of hands-on work with clients in HubSpot

Questions before a Service Hub implementation

Which Service Hub edition should we choose?

It depends on the size of your service team and whether you need response targets, a customer portal and an AI agent. My recommendation is in the document after the workshop.

How much does a Service Hub implementation cost?

We’ll work it out on the call, once I know your service process and channels. The Service Hub license is a separate cost, paid directly to HubSpot.

How much of my service team’s time will it take?

Whoever runs service joins the workshop, and the whole team joins training, in 1.5-2 hour sessions. I set up the inboxes, routing and knowledge base.

Will HubSpot connect to Jira?

Yes, HubSpot has a Jira integration. A ticket that needs developer work creates a Jira issue, and its status shows in HubSpot. Where the native integration falls short, I build the missing piece through the API.

We use Zendesk. What about our ticket history?

I move tickets to Service Hub with their content, author and dates. Zendesk stays available for reference, and your team switches to HubSpot on an agreed day.

Does the knowledge base need to be ready before launch?

No. I launch tickets and response targets without it, and we write articles from the questions that come in most often. The better the articles, the better the AI agent answers.

Let's talk about Service Hub

Thirty minutes, free. Tell me what you want to do and I'll tell you where to start.

Gracjan Kasprzyk
Your call is with Gracjan Kasprzyk