Newsletter

One email on Fridays, and nothing else.

  • Practical B2B tips

  • 4-min read on Fridays

  • For anyone in B2B growth

Common failures

Common failures

Setting the service hub up as a complaints desk. Teams configure for time-to-close and ticket volume, which rewards clearing the queue rather than keeping customers. It happens because the tool ships with queue-clearing metrics front and centre. Avoid it by deciding up front that this is a retention system, and building the pipelines, properties, and reports around resolution and at-risk accounts instead.

Copying generic ticket statuses instead of modelling the real workflow. A pasted-in "New, In progress, Waiting, Closed" pipeline describes nothing, so a ticket's stage stops meaning anything and nobody trusts the board. The fix is to model stages around the real states work passes through, each one naming who it waits on and what unblocks it.

Routing to whoever is free instead of to an owner. A shared everyone-inbox feels efficient and destroys accountability, because no one owns an outcome. Configure routing on skill and ownership, cap each agent's concurrent load, and make assignment sticky so a customer keeps talking to the same person.

Writing SLAs you never enforce in the tool. A response-time promise that lives in a help doc holds until the busy day it is supposed to cover. Configure the SLA as a live rule with separate first-response and resolution targets, tiered by customer and severity, with automated escalation that fires before the breach, not after.

Treating the knowledge base as a one-off content project. Articles get written once from imagination, never updated from real tickets, and go stale within a quarter. Build the knowledge base from your actual ticket data, wire a one-click loop from answered tickets to articles, surface articles at the point of need, and measure deflection so dead articles get pruned.

Automating the moments that need a human. A bot that traps a frustrated customer, or an auto-flow that processes a cancellation like routine volume, saves minutes and costs relationships. Automate the mechanical glue, but configure an instant human handoff on any frustration signal and route cancellations, escalations, and high-value accounts straight to a person.

More articles

  • Article

    Automate the contact lifecycle from customer through onboarding, active, and renewal so the CRM always reflects where someone is in the journey.

  • Article

    Configure ticket stages and routing rules so every customer issue gets to the right person without manual triage.

  • Article

    What happens when a new customer lands: ticket creation, owner assignment, welcome email, and first onboarding task.

  • Article

    Build workflows triggered by health score drops: internal alerts, outreach tasks, manager escalation. Catch problems before customers leave.

  • Article

    Define the properties that signal a healthy vs. at-risk customer (engagement, support tickets, NPS). Create a score HubSpot updates automatically.

  • Article

    Create a dedicated CS view with upcoming renewals, recent tickets, and account activity. One screen that tells your CS team who needs attention today.

All 15 articles under Tickets and SLAs
FAQ

Questions about this topic

Academy

Growth Academy

Start free

A free account opens the first course and keeps your progress.

  • A free course

  • Track your own skills

  • Every playbook you unlock