HubSpot Lead Response Time SLA: How to Set, Build and Measure It

A HubSpot lead response time SLA states, for each type of lead, how fast its owner must make first contact, which hours the clock runs and what happens after a miss. HubSpot has no SLA setting for leads, so you build one from owner assignment, a workflow with delays and branches, tasks and the Lead response time report.

This guide covers the definition, a worksheet for setting targets by lead type, a step-by-step workflow blueprint, the HubSpot properties that measure response time and the failure modes to test for. The worked example uses a fictional company. Workflows, rotation and calculation properties need paid tiers, noted where they come up, so confirm each tool in your own portal before you plan around it.

What is a lead response time SLA in HubSpot?

A lead response time SLA is an agreement between marketing and sales. For each lead type it records five things: the event that starts the clock, the event that stops it, the target time, the hours that count and the escalation when the target passes. Sales leadership owns the targets. RevOps owns the build and the report.

The wait a buyer feels has two parts, and each has its own fix, so measure them as two clocks:

A report that tracks only response time can look healthy while leads wait hours for an owner, so show both.

HubSpot’s own SLA feature belongs to the help desk. Its SLA goals need Service Hub Professional or Enterprise, and HubSpot states that they apply to help desk tickets only. For leads you combine features that already exist:

• an owner assignment that sets the Owner assigned date contact property;
• a workflow that waits for the target time and checks whether the owner made contact;
• the contact properties Date of first engagement, Type of first engagement and Lead response time, which HubSpot sets automatically;
• two custom properties of your own, SLA tier and SLA status, so reports can split results by lead type.

A written SLA makes the speed of first contact visible to everyone involved. The case for measuring it is old: a Harvard Business Review study by James Oldroyd, Kristina McElheran and David Elkington, The Short Life of Online Sales Leads (March 2011), looked at how companies handled online sales inquiries and concluded that most were not responding nearly fast enough.

What should the SLA define for each lead type?

One target for every lead hides the difference between a buyer asking for a demo and a student downloading an ebook. Split leads into tiers by intent and fit, then fill one row per tier. The table shows the core columns with example values from the fictional company described below.

On smaller screens, scroll to compare all columns.

Download the lead response SLA worksheet (CSV)

The worksheet has 15 columns per tier: how to identify the lead, the target, the business hours rule, the property that starts and stops the clock, the owner rule, two escalation steps, the HubSpot trigger, the workflow delay, a millisecond filter value for the Lead response time property and the report that shows compliance. The values are examples to replace with your own.

Give T6 an owner as well. Records that fail the fit check still need someone to review them, or they sit in sales views and drag the averages. If your lifecycle definitions are still loose, settle the handoff point first with the HubSpot lifecycle stages guide.

How fast should sales respond to each lead type?

Set each target from three inputs: how ready the buyer is, how many leads of that type arrive and how many people can cover the inbound queue during business hours. A 15-minute target only works if someone is free to call at any minute of the working day.

Here is a capacity check for the fictional example. Larchfield Analytics is an invented B2B software company with six SDRs in one time zone, working Monday to Friday from 09:00 to 18:00. It receives about 58 demo requests a month, which is roughly 2.8 per business day across 21 business days. Covering a 15-minute T1 target means someone is on inbound duty for all 45 business hours of the week. Split across six SDRs, that is 7.5 hours each per week, or 1.5 hours a day. The numbers are illustrative; run the same arithmetic with your own volumes before you publish a target to the team.

Write the business hours rule into the SLA. Decide whether only working hours count, and whether a request that arrives at night or over a weekend starts the clock at the next opening. Write the answer down, because the measures HubSpot records run on the wall clock, as the measurement section shows.

If you want help building and testing this in your portal, the HubSpot lead routing and workflow automation service covers owner rules, SLA workflows and the reports that track them.

How do you build a lead response SLA workflow in HubSpot?

Workflows need a Professional or Enterprise subscription. The Rotate record to owner action needs Sales Hub or Service Hub Professional or Enterprise, and only active users with a paid Professional or Enterprise seat receive records. The blueprint below uses one contact-based workflow per entry point. Build it first with test records, then turn it on.

1. Add a dropdown contact property SLA tier (T1 to T6) and a dropdown SLA status (Open, Met, Missed, Reassigned, No SLA).
2. Enroll on submission of the forms that create inbound requests, or on the lifecycle stage your handoff uses. Decide whether a repeat request re-enrolls the contact, and test what that does to an existing owner.
3. In the workflow’s timing settings, allow actions only Monday to Friday during business hours and add public holidays as pause dates. The window uses the account time zone.
4. Use a branch on form, fit and existing owner to set SLA tier, and set SLA status to Open. Send T6 down its own path to the RevOps queue with status No SLA.
5. For T1, T2 and T4, use Rotate record to owner with the overwrite option off, so owned records keep their owner. T3 keeps the existing owner. Then set Lead Status to New; the HubSpot Lead Status guide has example definitions for each value.
6. Add a Create task action for the new owner, named after the tier and target, and send an in-app notification. Creating tasks with workflows also needs a Professional or Enterprise subscription.
7. Add a Set amount of time delay: 15 minutes for T1, 1 hour for T2. For day-based tiers, tick Business days only (Monday – Friday), which skips weekends and accepts whole days only.
8. Branch on Date of first engagement is known. Yes: set SLA status to Met. No: set it to Missed and send an internal email and in-app notification to the owner and team lead.
9. On the Missed path, add a second delay of the same length and branch again. With still no engagement, rotate the record to the inbound pool with overwrite on, set SLA status to Reassigned and notify the new owner.

Before go-live, submit test leads through each real form, including one after hours, one from a company that already has an owner and one with missing fields. Check the owner, task, notifications and status each one receives. The HubSpot lead routing audit lists more test cases for the assignment part.

Portals that use the Leads object on Sales Hub Professional or Enterprise can rotate lead records instead. That version of the action, still labeled beta in HubSpot’s documentation, offers round robin, load balanced and random distribution and an option to assign to available users only.

How do business hours and weekends affect the SLA clock?

Workflow timing settings reschedule actions only. HubSpot’s settings article says an action that falls outside the allowed window runs at the earliest allowed time on the next available day, within a 15-minute window, while records still enter delays and branches at any hour. Three effects follow.

After-hours leads wait at the assignment step. A Larchfield contact requests a demo at 19:40 on a Friday. The Rotate record to owner action is rescheduled to Monday between 09:00 and 09:15, so the owner is assigned at 09:07 and the 15-minute delay starts then. The SDR calls at 09:18, which is 11 minutes after assignment and inside the target.

Leads assigned just before closing escalate the next morning. A T1 lead assigned at 17:52 leaves its 15-minute delay at 18:07. The branch runs at once, but the notification and status actions after it wait until the next morning’s opening. Accept this edge, or end the timing window 15 minutes before the team’s last shift ends.

Business-day delays skip weekends. A record that enters a 1 business day delay at 15:00 on a Friday leaves it at 15:00 on Monday. Holidays are a separate matter: add them as pause dates so the actions after the delay wait for a working day.

How do you measure lead response time in HubSpot?

HubSpot records several timing values automatically. They start and stop at different points, so choose one per question and label it clearly in reports.

On smaller screens, scroll to compare all columns.

The Lead response time report in the sales analytics suite counts sending an email, making a call, using chat, marking a task as in progress or complete, and a meeting’s start time as qualifying interactions. You can group it by owner or by team. The contact property stores the value in milliseconds, so a 15-minute target is 900,000 and a 1-hour target is 3,600,000 when you filter on it.

Lead response time starts at owner assignment, which hides the wait before routing ran. To see the buyer’s side, create a Time between calculation property from Recent conversion date to Date of first engagement and tick Exclude weekends. Check that both are date and time properties in your portal, because HubSpot reads a date-only property as midnight UTC. HubSpot counts the weekend from 00:00 Saturday to 23:59 Sunday in the account time zone, and nights still count. For the Friday request above, Lead response time shows 11 minutes (660,000 ms), while the buyer-side property shows 13 hours 38 minutes: 4 hours 20 minutes on Friday evening plus 9 hours 18 minutes on Monday morning. The wall-clock wait was 61 hours 38 minutes.

Portals on the Leads object also get Time to First Touch and First Outreach Date on each lead, and the team activity report in sales analytics lists an average time to first touch under Leads. HubSpot does not document a business hours option for any of these measures, so treat them as wall-clock values.

What should a lead response SLA report show?

Averages hide the leads that waited longest, so lead with the share of each tier that met its target. Build a contact report on SLA status broken down by SLA tier and owner, then add the Lead response time report for detail. Include these views:

• share of leads with status Met, by tier and by week;
• Missed and Reassigned counts by owner;
• Lead response time by owner for T1 and T2;
• the buyer-side Time between property by tier;
• Type of first engagement, to spot first touches that were task updates.

In the fictional example, Larchfield’s first month shows 58 T1 requests: 49 Met, 6 Missed and 3 Reassigned, so 84.5% met the 15-minute target. T2 shows 97 of 112 within an hour, or 86.6%. These invented numbers only show the format. In the review, each miss gets a reason, for example a meeting that ran over, a gap in the rotation or a form that skipped the workflow, and the most common reason is the next thing to fix.

For custom reports across objects you need a Professional or Enterprise subscription for the custom report builder.

Why do lead response SLAs fail?

Each of these comes from the build. Test for them before go-live and again after any change to forms, teams or integrations.

• A task update can stop the clock. Marking a task as in progress or complete counts as a qualifying interaction, so a rep can close the SLA task without calling anyone. Review Type of first engagement monthly and agree that the task is closed after the call or email.
• Reassignment resets the timer. Lead response time restarts for the new owner, so an escalated lead can look fast. Keep SLA status as the record of the miss and set it before the reassignment step.
• Owned records can pass the check at once. Date of first engagement belongs to the current owner, so a customer whose owner engaged with them last year already has a value. For T3 and repeat requests, branch on Last contacted with a relative date filter and test it with real records.
• If no eligible user is left in the rotation, HubSpot assigns no owner. Users who lose their paid seat or are deactivated drop out of assignments, and changing the user list after the workflow goes live resets the rotation counts.
• Integrations can overwrite the owner. HubSpot warns that if the owner property syncs with Salesforce, Salesforce may write back the previous owner. Check which system owns the owner field before turning the workflow on.
• Some entry points skip the workflow. A new landing page form, a chat flow or an import creates contacts the SLA never sees. Compare weekly form submissions against SLA enrollments.

Lead Status should move with the SLA. When the owner makes first contact, the status leaves New, and a report of contacts sitting in New past their target shows breaches the workflow missed. The HubSpot routing test lab helps check assignment rules before a change.

Frequently asked questions

To have the SLA tiers, workflows and reports built and tested in your portal, see HubSpot lead routing and workflow automation.