Skip to content
Tutorials Center
My learning

Topics

Lesson 36 of 37 ยท Projects and Practice

Project: A Support SLA Monitor and Escalation Plan

Plan a Service Hub support setup with ticket pipeline, priorities, SLA targets, escalation workflow, CSAT survey and a dashboard, and prototype the monitor in runnable Python.

This project builds the support side of a business. You will design a ticket pipeline, set priority-based targets, plan an escalation workflow, add a CSAT survey, and prototype a monitor that reports which tickets need attention. It reuses ideas from tickets, SLAs, feedback and workflows.

HubSpot cannot run here, so the steps describe what to do in your own Service Hub trial, and the Python block is a stand-in prototype of the report you want. Features such as SLAs and surveys depend on your plan.

The scenario

Northwind Cloud gets about 40 support requests a day by email and chat. Customers on the Premium plan expect faster help than Basic customers. Management wants: no urgent ticket unanswered for more than an hour, a clear daily list of at-risk tickets, and satisfaction measured after every closed ticket.

Design

Item Choice
Pipeline New, Waiting on contact, Waiting on us, Closed
Priorities Urgent (1h first reply), High (4h), Medium (8h), Low (24h)
Priority rule Premium customers start one level higher (Medium becomes High)
Escalation At 75% of target: notify the team; at breach: task for the lead and set "Escalated"
Survey CSAT after the ticket is closed
Dashboard Open tickets by owner, first-response met rate, CSAT trend

Support loop

Intake Email, chat, form
Prioritize Plan sets the level
Watch the clock Warn, then escalate
Survey CSAT after close

Measure every step

1 / 2

Build steps in HubSpot

  1. Settings > Objects > Tickets > Pipelines: set the four statuses with open/closed states.
  2. Create a Customer plan property on companies (Basic or Premium), and keep it in sync with billing.
  3. Workflow 1, intake (ticket-based): when a ticket is created, branch on the associated company's plan and set priority accordingly; rotate to an available agent.
  4. Workflow 2, escalation: trigger on tickets that are open and priority is Urgent or High; delay to the warning point; if still without a first reply, send a notification; delay again; if still without a reply, create a task for the lead and set Escalated to Yes.
  5. Workflow 3, survey: trigger when ticket status becomes Closed; delay one hour; send the CSAT survey.
  6. Dashboard: add reports for open tickets by owner and priority, time to first response, and CSAT.

Prototype the monitor

Python Daily at-risk report (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

T-101 is a Premium ticket whose Medium priority is bumped to High (4 hours), so three hours waited means 75% of the target is used and it is flagged "at risk" right behind T-102 (88% of its 8-hour target). Compare this to how the HubSpot SLA indicator behaves in your trial.

Prototype the CSAT trend

Python Weekly CSAT and first-response met rate

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

With so few responses the numbers jump around; note the sample size on the dashboard title.

Test and review

  • Create test tickets for a Premium and a Basic company and check the assigned priority.
  • Close a test ticket and confirm the survey sends after the delay (use your own address).
  • Check the escalation workflow history for each branch.
  • After two weeks compare actual breaches with the monitor's at-risk list to tune the 75% warning point.

Stretch goals

  • Add business hours to targets (see the calculator in the SLA lesson).
  • Create a knowledge base article for the top three ticket causes (knowledge base).
  • Add a chatbot that suggests articles before opening a ticket.

Check your understanding

Quick check ยท 3 questions

of 3 answered You scored / 3 ยท perfect!

  1. 1. In the prototype, why does T-101 appear at 75% used?

    The plan rule raises the priority, shortening the target.
  2. 2. Which workflow sends the CSAT survey?

    Surveys belong right after the event they measure.
  3. 3. Why show the sample size next to CSAT?

    A few responses can swing the percentage a lot.

Summary

  • Combine pipeline, priority rules, SLA targets, escalation workflows and surveys into one support design.
  • A small monitor report ranks tickets by how much of their target is used.
  • Review results regularly and tune thresholds from real data.

Next: Practice and Review: Think Like a HubSpot Admin