Writing a Lead Handling Playbook for the Whole Store

Saturday at 11:40 a.m. A Marketplace inquiry comes in on a 2018 truck. The internet manager is at lunch. The assigned sales rep is on a test drive. An associate answers from a personal phone, quotes a number that is not the desk price, and tells the buyer to "come anytime." Twenty minutes later a second rep, who saw the same thread on a shared login, sends a different price. The buyer never shows. Nobody logs the lead. On Monday the CRM still says the truck is unworked.

That is not a people problem. It is a missing document problem. Most stores run lead handling as tribal knowledge: the BDC knows one version, the closer knows another, and the Saturday crew invents a third. Writing a lead handling playbook for the whole store turns those conflicting habits into one operating standard that a new hire can follow on day one.

This guide is for general managers, internet directors, and used-car managers who already have a CRM, a desk, and a floor. It covers what belongs in the playbook, how to write it so people will use it, and how to roll it out without producing a binder that lives in a drawer.

Why a Lead Handling Playbook Beats Tribal Knowledge

Verbal rules die the moment the person who remembers them is with a customer. A playbook is the store's answer to four questions that otherwise get decided in the moment, badly.

The four questions every lead creates

1. Who owns this lead right now? Name a person, not a department.
2. What is the first action, and by when? Call, text, Marketplace reply, or a combination, with a clock.
3. What is allowed in the first conversation? Price, availability, trade talk, credit talk, and what must wait for the desk.
4. What happens if the owner cannot act? Coverage, escalation, and a written handoff.

If those four answers live only in someone's head, you will get double-texts, silent threads, and cherry-picking. If they live in a short, current document, you can train, coach, and fire against them.

What a playbook is not

A playbook is not a 40-page internet-sales manifesto and it is not a script book that forbids judgment. It is a set of defaults: the move a competent rep makes unless a manager overrides it. Keep it short enough to read in a huddle. If a rule needs a paragraph of exceptions, it is not a rule yet.

Who the playbook is for

Write it for the whole store, not just the BDC:

• Associates who cover phones and Marketplace while seniors are on the lot.
• Sales reps who self-work internet leads and walk-ins.
• Managers who assign, intercept, and desk.
• Admin who owns CRM hygiene and source codes.

If only the internet director can explain the process, you do not have a process. You have a bottleneck.

What Belongs in a Store-Wide Lead Handling Playbook

Build the document in sections that map to a real lead's life, not to org-chart titles. Use the same headings in training so people can find the rule in under a minute.

Intake and source labels

Every inbound contact needs a source the store agrees on. Marketplace, website form, third-party listing, phone-up, and walk-in are different animals. The playbook should state:

• How the source is recorded on first touch.
• Who is allowed to create the CRM record.
• What minimum fields are required before the lead is "in the system" (name or handle, vehicle of interest, source, timestamp, owner).

Do not invent a 20-field intake form. Capture enough to work the lead and attribute it later. For a field-level companion, see Lead Intake Checklist: What to Capture on Every Internet Lead.

Ownership and assignment

State the assignment model in one paragraph. Round robin, skill-based, source-based, or manager assignment are all valid; mixing them without writing it down is not. Include:

• Who assigns (admin, manager, or automatic rotation in the CRM).
• When a lead is fair game for anyone versus locked to an owner.
• How long an owner keeps an unworked lead before it recycles.
• How disputes get settled, and by whom.

Response standards by lead type

Do not publish one speed for every source. A Marketplace "is this still available?" and a credit-app form fill do not deserve the same first move. The playbook should list lead types and, for each, the expected first channel, a conservative in-hours target, and an after-hours target. Pair this section with your lead response SLA so the playbook and the SLA never disagree.

Conversation boundaries

Write the lines reps are not allowed to cross without a manager:

• Discounting below a published floor.
• Promising a hold without a deposit policy.
• Quoting out-the-door numbers they cannot support.
• Discussing credit approval as if a decision has already been made.

This is operational guidance, not legal advice. Confirm financing language, deposit rules, and advertising claims with counsel or your compliance owner.

Status, next step, and stop rules

A lead without a next step is a dropped lead. The playbook should define a short status list (new, contacted, appointment set, showed, sold, lost, recycle) and require a dated next action on every live record. Include stop rules so people know when to quit: after a defined sequence of unanswered attempts, or when the customer asks to be left alone. Align statuses with lead status definitions that keep the pipeline honest.

Roles, Coverage, and Handoffs Inside the Playbook

The document fails if it assumes every lead is handled by the person who first saw it. Floor reality is interruptions. The playbook has to describe coverage as a first-class process.

Role map

Use the role names your store actually uses. If you have a BDC, give it a row. If you do not, do not pretend you do.

Coverage when the owner is occupied

Write the fallback in order:

1. Designated coverage person for that shift (rover or BDC).
2. Manager intercept after a stated wait.
3. A holding reply that acknowledges the message and promises a named person will follow up, with a time window.

"Someone will get back to you" is not a coverage plan. Name the someone.

Handoff notes

Require a note whenever ownership moves: weekend to Monday, lunch to close, BDC to floor, departing rep to the house. The note needs the vehicle, the last customer words, the last promise made, and the next action. Without that, the next person restarts the conversation and looks unprofessional.

How to Write and Roll Out the Lead Handling Playbook

A playbook that nobody can find is worse than none, because managers will assume the floor "already knows." Treat publication as an operations project.

Draft it from real failures, not from theory

Pull a week of CRM notes, unanswered threads, and appointment no-shows. List the five failure modes that actually happened: double-quoted prices, leads with no owner, after-hours silence, sold units still being offered, notes that say only "left vm." Write a rule for each. Then fill the remaining sections. Starting from a template produces a document that sounds right and misses your store's actual leaks.

Keep it to a length people will reread

Aim for a document a manager can walk through in a 20-minute meeting. Use headings, checklists, and a one-page quick card for the desk. Put long scripts in an appendix. If you need more than that, you are trying to solve training, pay plan, and inventory problems inside a lead document.

Version, owner, and review cadence

• Owner: one person, usually the internet director or sales manager, not "the managers."
• Version date on the first page.
• Review: monthly for the first quarter, then quarterly, or immediately after a process failure.

Print is fine for the desk. The live copy should live where the team already works: a shared drive, the CRM attachment, or an internal wiki. Announce changes in the Monday meeting. Do not rely on people noticing a new file.

Train, then mystery-shop

1. Read the playbook in a huddle. Do not email it and call that training.
2. Role-play one Marketplace inquiry, one form fill, and one after-hours message.
3. Mystery-shop the store within two weeks. Score against the playbook, not against "how we usually do it."
4. Coach the misses in the same meeting you review aged inventory.

If a rule keeps getting broken, the rule is wrong or the coverage model is understaffed. Change the document. Do not add a second unofficial process.

How PostToMarket Automates This

A lead handling playbook collapses when inventory state, posting ownership, and incoming inquiries live in three different places. The playbook says "confirm the unit is still available," but the listing is still live on a sold truck. It says "the assigned rep answers," but the inquiry arrived on an account nobody is watching. PostToMarket does not replace your CRM or your desk process. It removes the operational gaps that make the playbook impossible to follow.

Inventory state the floor can trust

• Statuses (draft, posting, posted, sold, failed) so the person answering a lead can see whether the unit is actually available.
• Mark as sold and archive from inventory or the queue, which stops the playbook's first conversation from offering a car that already left.
• Unlimited vehicles in inventory on every plan, so the playbook is not fighting a tool that only holds a slice of the lot.

Ownership that matches the playbook

• Per-rep posting queues and manager assignment to associate queues, so the person who posted the unit is a known owner, not a shared login.
• Team queue view where a manager can see and release a stuck claim instead of guessing who has the thread.
• Roles (admin, manager, sales rep, sales associate) that map to the playbook's role table instead of one inbox everyone raids.

Visibility for managers

• A leads inbox so managers can see inquiries instead of hoping a personal Messenger thread got answered.
• Team analytics by rep and source, which gives the playbook review meeting something to look at besides anecdotes.
• A mobile dashboard so a manager walking the lot can reorder a queue between customers instead of leaving coverage to chance.

PostToMarket is independent and is not affiliated with Meta. No tool can guarantee that every Marketplace listing gets distributed or that every inquiry becomes an appointment. What it can do is make the playbook's rules enforceable: clean inventory, named owners, and a place to see the leads those owners are supposed to work.

Put One Playbook on the Floor This Week

A store that posts well and answers badly still sits on aged inventory. The cheapest fix is not another headcount. It is a written lead handling playbook the whole store can execute on a Saturday without the internet director in the building.

PostToMarket gives you the inventory, queue, and leads layer that playbook depends on: unlimited units, AI listing copy you can edit before posting, bulk CSV and Excel import with a row-level error log, per-rep queues, and a leads inbox for managers. Starter is $59 per month for a solo seller who needs one login. Dealership is $299 per month for a floor team of up to 13 logins, including two managers.

Start your 10-day free trial with secure Stripe checkout. Import this week's inventory, assign queues to the people named in your playbook, and cancel anytime if the workflow does not fit the store.