Custom SLA Configuration Beyond Default Options in HubSpot Service Hub

Service Hub Tips, Tricks & Best Practices
1

Hi all,

I’m currently working on setting up SLAs in HubSpot and wondering if there’s a way to configure them beyond the default options: Time to First Reply, Time to Next Reply, and Time to Close.

In our case, our ticket pipeline includes nearly 10 stages, and we’d like to define specific time thresholds for intermediate steps—based on custom logic and conditions (e.g., once a bid is approved the estimator has 48 hours to be on site).

Has anyone implemented this type of SLA logic, either natively in HubSpot or through creative workarounds?

Would love to hear any approaches or examples.

Thanks,
Diego

2

Hey @level-ground :waving_hand: Thanks for your question! I think you’re spot on about the current options and limitations — Set SLA goals in help desk.

I don’t have a magic answer for you unfortunately :wink:, but I did brainstorm a few ideas you might investigate:

  • Workflow + Custom Properties
    - custom date/datetime properties for each critical stage (e.g., “Bid Approved Date”, “Site Visit Due Date”)
  • Task-Based Tracking
    - create tasks with due dates when tickets hit specific stages
  • Custom Dashboard Solution
    - calculated properties that measure time differences between stage transitions

Have fun testing! — Jaycee

3

@level-ground I would model each intermediate SLA as its own timestamp pair rather than trying to force one global SLA.

For example:

  • Bid Approved At
  • Site Visit Due At
  • Site Visit Completed At
  • Site Visit SLA Status

Then repeat that pattern for each critical stage.

The practical advantage is that each stage can have its own threshold and reporting. You can then build views for currently inside SLA, at risk, and breached.

I’d be careful with task-only tracking because it can show that a task was created without proving the stage outcome actually happened. For any SLA that matters operationally, I’d want both the due timestamp and the completed timestamp recorded.

4

Hey @level-ground, another approach you could explore is a hybrid setup.

For milestones that align with a ticket stage, you can use HubSpot’s stage calculated properties instead of creating additional timestamp properties. HubSpot already tracks values like Date entered stage and Time in current stage, which can be used as the starting point for a workflow to monitor that SLA.

For milestones that happen within a stage rather than as part of a stage transition, a Due Date and Completed Date property pair works well. A workflow can compare those values to send reminders, trigger escalations, or update an SLA status based on whether the milestone was completed within the expected timeframe.

This approach helps avoid creating duplicate data where HubSpot is already tracking it natively, while still giving you the flexibility to support SLA checkpoints that aren’t tied directly to a stage change.

For reference, you can also take a look at HubSpot’s Stage Calculated Properties Knowledge Base article. It explains how these properties are populated and when they’re updated, which can be helpful when designing your workflow logic.