A report of “overdue leads” can create an argument before it creates a next action. Marketing may start the clock at form submission. Sales may start it at assignment. Neither team can fairly interpret the result until the agreement defines the clock.
We recommend reviewing missed follow-up against an explicit operating definition. The goal is to identify the next action and the process failure, while separating a real missed commitment from missing evidence.
TLDR: Define the qualifying event, start time, stop event, business-hours rule, exclusions and escalation owner. Build the overdue view from those definitions, then inspect the records behind it. Keep unknown timestamps in a separate exception group instead of reporting them as either compliant or overdue.
A marketing-to-sales service level agreement defines the conditions for handing a lead to sales, the follow-up commitment and the evidence used to review both sides. It is a written operating agreement between the marketing team and the sales team. It should specify lead quality as well as response times.
Marketing commitments might include a required qualification definition, usable contact details and the information sales needs for a relevant response. Sales commitments might include accepting or rejecting a qualified lead, recording a reason and making the agreed contact attempts. These are recommended categories for your agreement, not universal HubSpot settings.
Keep the commercial goal visible without pretending the SLA guarantees it. A revenue goal can inform planning, but a missed revenue target does not tell you whether marketing supplied the wrong leads, sales missed follow-up or the buying cycle simply extended beyond the reporting period. Measure those stages separately.
The two teams need a shared meaning for “qualified.” If the marketing team counts every content download while the sales team expects a verified buying request, they are using different definitions. A dashboard cannot settle that disagreement.
Document the relevant lifecycle stages, the lead scoring model if one is used, and the exclusions. Marketing qualified leads and sales qualified leads represent different decisions. Do not assume that a lead score, owner change or logged task proves sales acceptance.
Use a cohort such as “leads that first met the agreed handoff definition during this week.” Then decide how repeat qualification, reopened records and ownership changes affect that cohort. This makes the report reproducible. Counting whichever records currently have a selected status may describe a different population each time someone changes the data.
Here is a synthetic agreement specification you can adapt:
| Agreement field | Example definition |
|---|---|
| Eligible lead | Meets the approved fit and engagement criteria and is not excluded |
| Clock start | The recorded event that first qualifies the lead for this handoff |
| Sales owner | The person accountable at assignment, retained for historical review |
| First response | A documented external contact attempt that meets the agreed criteria |
| Follow-up cadence | The agreed sequence of later attempts, with channel and stop conditions |
| Rejection | An explicit reason, date and person responsible for the decision |
| Exception | Missing evidence, unsupported coverage or another approved condition requiring review |
These field names are a specification, not a claim that your HubSpot CRM already contains them. Reuse suitable existing properties and activity records before introducing new ones.
Begin with counts that can be reconciled to records: eligible handoffs, assigned leads, leads with a qualifying first response, overdue responses and leads whose response evidence is missing. A contact attempt count alone cannot show which leads received no attempt.
For a synthetic example, suppose a cohort contains 40 eligible leads. Evidence shows 28 received a timely first response, 8 received a late response and 4 have no qualifying response. If the written SLA counts all 40 as eligible, timely-response compliance is 28 divided by 40, or 70%. Reporting 28 divided by the 36 contacted leads would hide the four without a response.
Keep that calculation separate from close rates and conversion rates. A timely first response is an SLA result, not a sales outcome. Lead-to-opportunity conversion, accepted-lead rate and revenue can sit beside the SLA metrics, provided their definitions and reporting windows are explicit.
Response times also need a clear unit. An elapsed-hours report and a business-hours target are not directly comparable. Choose the applicable time zone, holiday treatment and pause conditions before judging a person against the target.
Before building a custom report, list the source for each measurement: the qualification event, assignment record, response activity, rejection reason and relevant timestamps. Write down which object holds each value and how records will be associated. Report availability and cross-object options depend on your HubSpot subscription and the selected reporting tool. HubSpot custom reporting guidance
Retain a small record-level reconciliation beside the summary report. For each sampled missed SLA, open the underlying evidence and verify that the report did not exclude an activity or use the wrong date. A completed workflow proves that an action ran; it does not by itself prove that a prospect received an appropriate response.
Do not substitute Service Hub ticket SLA metrics for this marketing and sales SLA without validating the data model. Customer-support response and resolution measures answer a different operating question. A contact handoff may need its own documented report logic rather than a renamed ticket dashboard.
Use the review to assign a next action, not simply to rank teams. Repeated missing phone numbers may require a lead-capture change. Repeated unsupported account types may require revised qualification. Repeated timely assignments without a response may require a coverage or follow-up change.
Record the decision, its owner and the date it will be checked. Preserve the original missed-SLA evidence even when the process improves. That gives the leadership team a traceable explanation of what changed and lets both sales and marketing teams review the next cohort against the same agreement.
Write the event that makes a lead subject to the agreement. It might be a qualified handoff, an accepted assignment or another business-approved point. Do not assume every form submission carries the same follow-up obligation.
Next, define the action that satisfies the commitment. An attempted call, a recorded email and a completed conversation are different events. Choose the event the business intends and specify what evidence must exist.
Use tracking leads in HubSpot for broader context, but make the timestamps and evidence explicit in this report specification. A familiar property label is not a substitute for confirming what populated it.
Specify the timezone, working hours, holidays and handling of assignments outside coverage. Decide whether a reassignment restarts the clock, pauses it or leaves the original deadline intact.
Ask how the team handles duplicates, invalid inquiries, existing opportunities and missing information. Some cases may be excluded under the agreement. Others may need a separate next action. Record the reason rather than removing them from the report without explanation.
These are recommended report requirements, not built-in HubSpot SLA settings.
Hypothetical example: A team agrees that a qualifying assignment received during its coverage period needs a documented first attempt within 2 business hours. This is an invented agreement, not a benchmark or Selworthy service commitment.
In a controlled example, assignment A begins at 10:00 and has a qualifying attempt at 11:15. Assignment B begins at 10:00 and is still unanswered at 13:00. Assignment C has no reliable assignment timestamp.
Assuming uninterrupted coverage for the entire example, A meets the agreement after 75 minutes. B is overdue by 60 minutes at review time. C is an evidence exception, so the team cannot classify it reliably from the available data.
The point is not the chosen threshold. It is the separate treatment of timely action, missed action and insufficient evidence.
Include the record identifier, responsible role, qualifying event, start time, deadline, observed action and current disposition. Add a link to the underlying record so the reviewer can inspect the evidence.
HubSpot's custom-report documentation describes different report types and notes subscription and permission requirements. Read the custom-report guide before selecting an implementation. The specification should not promise that every account can build the exact view in the same way.
If a calculation cannot be supported by the available data or tooling, document the limitation. A manually reviewed exception list can be more honest than a dashboard that silently substitutes another timestamp.
For each missed commitment, determine whether the record reached the intended owner, whether the evidence is complete and whether an approved exception applies. Assignment logic belongs in its own diagnostic process; this review uses the result to decide what needs attention.
Do not infer that a seller ignored a lead solely because an activity field is empty. Investigate whether the required action occurred elsewhere, whether it was recorded correctly and whether the agreement was understood.
Keep the outcome actionable: follow up now, correct the evidence, repair a process, clarify the rule or accept an exclusion. Record who is responsible for the next step without changing the original evidence.
Bring the written service level agreement, the cohort report and the underlying exception records. Start with the marketing commitments and sales commitments that were actually approved. Then compare the measured response times and follow-up attempts with those definitions.
The marketing SLA should specify the lead-quality standards at handoff. The sales side should specify the first contact attempt, later follow-up cadence and rejection feedback. Reviewing only lead volume leaves the marketing team without evidence of quality and the sales team without a clear accountability standard.
Use SLA performance to assign a correction to a process. A report that identifies a late response should distinguish a coverage gap, an ownership problem and missing activity evidence. Keep the exception visible until the next action is verified.
For this use case, show eligible marketing-to-sales handoffs, accepted and rejected leads, timely responses, late responses and missing response evidence. Display the agreement version and date basis beside the metrics. Those are recommended report requirements, not a claim that a prebuilt HubSpot dashboard supplies them automatically.
No. Service Hub ticket SLAs concern service operations such as response and resolution. Ticket properties, resolution times and customer satisfaction scores do not automatically measure a marketing-to-sales handoff. Your support team may need that service reporting, while the sales and marketing SLA needs its own validated definition and data sources.
State the numerator and denominator. A percentage should show which leads are eligible and how exclusions or missing evidence are handled. If the required timestamps are unavailable, report the gap instead of claiming SLA compliance. Keep customer satisfaction and revenue outcomes separate from the response commitment itself.
Review the oldest unresolved items and the recurring causes. Ask whether the same exception keeps appearing because the rule is unclear, the data is missing or the team lacks coverage.
Our sales funnel guide can help place that review within the broader sales process. Keep the meeting focused on the agreed handoff and the actions needed to resolve it.
We recommend reviewing the report design through HubSpot operations and the operating agreement through HubSpot Sales Hub services. Start with the clock definition, then make the report reflect it.
Product documentation checked September 6, 2026. All times and the follow-up threshold in the worked example are synthetic.