What this playbook covers and when to run it
The playbook covers everything that happens to an inbound lead between the moment someone submits a form or starts a chat and the moment the lead becomes an opportunity, is disqualified or is placed in nurture. It also covers the reporting that tells marketing which sources produce pipeline. It does not define lead stages or explain how to build a scoring model; the lead stages guide and the lead scoring guide own those subjects.
Run it whenever inbound leads are handed from marketing to a sales or sales development team, which is most business-to-business companies and many considered-purchase consumer businesses. It is most urgent when sales and marketing disagree about lead quality, when response timesAverage time between a new lead arriving and the first contact from sales. are unknown, or when marketing cannot say which campaigns produce revenue. Those three symptoms usually share a cause: nobody owns the hand-offs.
The playbook is part of the playbooks library. It depends on the sales and marketing alignment guide for the broader relationship between the two teams; this page is the operational core of that relationship.
Roles and responsibilities
- Marketing operations. Owns the systems and the rules: forms, enrichment, routing logicRules that assign each new lead to an owner, queue or next step based on territory, segment, score or source., the CRM-to-marketing-platform sync, lead status definitions and the daily queue check.
- Sales development. Owns first contact and qualification: responding within the agreed time, qualifying against agreed criteria, and recording the outcome with a reason.
- Sales manager. Owns the sales side of the agreement: staffing the response, enforcing the service levels for their team, and bringing quality feedback to the weekly review.
- Marketing analyst. Owns the numbers: response times, conversion between stages, pipeline by source and the reconciliation between marketing data and the CRM.
The role that most often goes missing is the one that owns rejected and unworked leads. Write it into the playbook explicitly: marketing operations owns any lead that has no other owner, and the daily check exists partly to find them.
Cadence, inputs and outputs
| Cadence | Owner | Inputs | Outputs |
|---|---|---|---|
| Daily | Marketing operations, sales development | Routing queues, unassigned leads, leads past their response target | Leads reassigned or escalated; response gaps flagged to the sales manager |
| Weekly | Sales manager, marketing operations, analyst | Rejected leads with reasons, a sample of qualified and disqualified leads, response time report | Agreed fixes to routing, forms or criteria; quality issues fed back to campaigns |
| Monthly | Marketing analyst | CRM stages, campaign data, spend | Pipeline and revenue by source and stage; conversion between stages; cost per stage |
The daily check is the part most teams drop first when they get busy, and it is the part that catches the most expensive failures: leads assigned to someone on leave, or a sync that stopped overnight. When someone leaves for good, the tutorial on reassigning CRM records when someone leaves moves their deals, contacts, tasks and routing slots by rule so the daily check is not left to find them.
The playbook in phases
Capture and enrich
Every lead starts with capture, and most later problems trace back to it. Forms should ask for what routing and qualification actually need, and no more. Hidden fieldsA form field the visitor never sees that records values such as source, campaign and landing page, so each lead arrives in the CRM with its origin. should record the source, campaign and landing page, which depends on consistent campaign tagging; the UTM link request procedure makes sure every link carries the right parameters. Enrichment, whether from a data provider or from what the business already knows, fills in company and role details so routing does not depend on what the person chose to type. Marketing operations checks weekly that new forms map correctly into the CRM and that source fields are populated; a lead without a source cannot be credited in reporting later.
Route and assign
Routing decides who owns the lead and how fast they must act. Write the rules down: by lead type, such as a demo request versus a content download, by territory, by company size or by existing account ownership. Simple rules that everyone understands beat clever rules nobody can explain. The lead routing rules template writes them one row per route, each with an owner, a fallback and a response target. Assignment should happen automatically and notify the owner. Every route needs a fallback: if the assigned person is away, the lead goes to a named queue that someone checks. Marketing operations reviews the routing queues every day for unassigned leads, leads assigned to people who have left, and leads stuck between systems because a sync failed. Before a new form, source or rule goes live, the lead routing QA checklist tests every route with test leads.
Respond and qualify
Sales development contacts the lead within the response target set in the service level agreement, with the fastest targets reserved for the highest-intent requests. The first contact should acknowledge what the lead asked for; a demo request answered with a generic sequence feels like nobody read it. Qualification follows the criteria both teams agreed, and the outcome is recorded in the CRM with a reason: accepted as an opportunity, not ready, or disqualified with a reason code. Reason codes matter because they are the raw material of the weekly quality review. "Bad lead" tells marketing nothing; "student", "competitor" or "no budget this year" tells them where to look.
Nurture the not-ready
Many inbound leads are genuine but early. They have a real need and no plan to buy yet. These should not be discarded or left in a sales rep's list to go cold. Route them back to marketing with their reason code and place them in a nurture track that matches their stage and interest, built with the lead scoringAssigning points to leads for fit and behaviour to decide which are ready for sales. and automation guidance. Define the signals that bring a nurtured lead back to sales: a return visit to pricing, a demo request, a score threshold if the team uses scoring. Teams that do can write the rules down in the lead scoring model template, including where a lead is routed at each threshold. Marketing operations owns the nurture tracks; sales development owns the re-engagement when a lead re-qualifies. Review the nurture pool monthly for leads that have been there too long without any engagement.
Close the loop
Closing the loop means connecting what happened in sales back to where the lead came from. The CRM integration guide explains how to send stage changes and revenue back to analytics and advertising platforms. The marketing analyst reports monthly on pipeline and revenue by source, conversion rates between stages and cost per stage, using the FunnelModel of the customer journey stages. stages both teams agreed. The conversion rate calculator and the CPA calculator help with quick checks. The report goes to marketing and sales together, and it feeds budget decisions: sources that produce leads but not pipeline get less money.
Service levels between marketing and sales
A service level agreement turns the hand-off from a matter of goodwill into a written commitment both teams report on. It does not need to be long. It should say what marketing promises to deliver, what sales promises to do with it, how both are measured and what happens when either side misses.
| Commitment | Owner | Measured by |
|---|---|---|
| Leads meet the agreed definition before hand-off | Marketing operations | Share of leads accepted by sales development |
| Every lead has a source and campaign recorded | Marketing operations | Share of leads with populated source fields |
| Every lead is assigned to a person or a monitored queue | Marketing operations | Unassigned leads found in the daily check |
| Leads are contacted within the response target for their type | Sales development | Response time by lead type |
| Every worked lead has an outcome and reason code | Sales development | Share of leads with a recorded outcome |
| Rejected and not-ready leads return to marketing | Sales manager | Leads sitting in sales queues with no activity |
Review the agreement each quarter. If one side keeps missing, the agreement may be unrealistic or the staffing may be wrong; either way the conversation should start from the numbers, not from anecdotes. A service level that is never measured quickly becomes a source of blame rather than a tool.
An HR software company finding its leaking leads
An HR software company receives about 900 inbound leads a month. Sales says lead quality is poor; marketing says sales ignores half the leads. The marketing analyst pulls a month of CRM data and finds that 31% of leads were never contacted, mostly because they were routed to two reps who had left. Median response time for demo requests is 26 hours. The teams agree an SLA with a same-day target for demo requests, add a fallback queue and introduce six reason codes. Three months later, uncontacted leads are under 5%, and the reason codes show that one content syndication source produces most disqualified leads, so its budget is cut.
Whether a faster service level pays for itself can be tested rather than assumed: the lead response time test routes leads at random to an immediate-response rota or the standard queue and reads meetings held per lead. Leads bought from comparison sites and other partners belong in the same queue and service level, and the guide to pay-per-lead affiliate programmes explains why their recorded outcomes double as the evidence for accepting or returning each lead.
Measuring the playbook
The playbook works if leads move through the hand-offs quickly and nobody gets lost. Operating signals include median response time by lead type, the share of leads with no recorded outcome after a set period, unassigned leads found in daily checks, the share of leads with source data, and how many rejected leads returned to marketing with a reason code. These are the measures the service level agreement reports on.
Outcome signals show whether better handling is producing better business: conversion rate between stages, pipeline and revenue by source, and CACCost to acquire one new customer. by channel once the loop is closed. Be careful with AttributionAssigning conversion credit to touchpoints. in this reporting; a lead that touched several campaigns will be credited differently depending on the model, so agree the model with sales before the numbers are used to cut budgets. Track the CVRShare of visits or clicks that convert. from lead to opportunity by source, because that is the number that most often changes the budget conversation.
Common mistakes
- No owner for rejected leads. Leads rejected by sales with no route back to marketing simply vanish. Make marketing the default owner.
- Routing rules nobody can explain. Complex logic breaks silently when someone leaves or a territory changes. Keep rules simple and documented.
- Response targets that are never measured. A target without a daily check is a hope. Measure it every day.
- "Bad lead" as a reason. Without specific reason codes, quality feedback cannot change campaigns. Agree a short list of codes.
- Reporting leads instead of pipeline. Lead volume flatters sources that produce poor leads. Report on pipeline and revenue by source.
- Forgetting the not-ready. Early-stage leads discarded today are tomorrow's buyers who chose a competitor. Nurture them deliberately.
