Playbooks

Plays to own the thread.

Plays the floor can run this week after hours, first reply, held visits, aged lists, and the scorecard a GM already understands.

After hours
Speed to lead
Held visits

After hours playbook

10:42 PM

Lot closed · thread still live

Ping → SMS → Saturday hold

Marketplace → SMS → owner

Ping

Jordan · 24

10:42 PM

SMS

Saturday 10?

12s

Hold

South lot

Booked

Lot closed Thread owned CRM in the morning
After hours

The after-hours lead playbook

Marketplace pings do not wait for the lot to open. Own the thread before morning standup.

Nights and weekends dump into a personal inbox. This play puts a tracking number, an owner, and a Saturday slot on every ping that lands after close.

01

Forward after-hours sources

Facebook, Google, ADF, and marketplace mailboxes land in LeadStreamIQ — not a personal phone.

02

AI drafts the first reply

SMS on the same thread. Inventory questions get answered from the lot you actually have.

03

Assign a rooftop owner

Team Inbox puts one specialist on the ping. Hudson does not eat the south lot.

04

Offer a real Saturday slot

Calendar Booking uses live availability. Confirm on SMS. Cadence stops when it is held.

05

Write the visit back

Lightspeed, Aimbase, DP360, BoatCrazy, ADF Email, or your API — the morning closer opens the CRM with context.

Speed to lead playbook

First reply

Unread is not a strategy

One stream → SMS → owner

Form · ADF · ads → Team Inbox

In

Site form

Just now

SMS

Still looking?

On thread

Owner

Alex claimed

Assigned

Same stream Buyer’s channel Measured on the thread
Speed to lead

Speed-to-lead without a fire drill

The first reply should not depend on who is walking the lot.

Speed dies in Unread and in “I thought you had it.” This play makes first response a system, not a hero closer.

01

One stream, every source

Forms, ads, OEM, and marketplace feeds stop living in four inboxes.

02

Reply on the buyer’s channel

SMS and call tracking first. Email parse for ADF. No “we will call you tomorrow.”

03

Qualify in the same thread

Budget, timeline, trade, and unit captured before the specialist picks up.

04

Measure first-touch on the thread

Reporting sits next to the conversation. No vanity chat counts.

Booking playbook

Sat 10:00

A reply is not a visit

Qualify → live slot → confirm

Thread → calendar → CRM

Intent

South lot

Mapped

Slot

Sat 10:00

Live hours

Hold

SMS confirm

Booked

Live availability Cadence stops Closer has the transcript
Booking

Booking more held lot visits

A conversation that never becomes a slot is still Unread by another name.

Turn qualified threads into confirmed appointments against live availability then stop the cadence.

01

Qualify before you offer times

Intent and rooftop first. Do not book Hudson on the south lot.

02

Offer live availability

Calendar Booking uses the store’s real hours and the assigned closer.

03

Confirm on SMS

The buyer gets the slot on the same thread they started.

04

Write-back, then stop nurture

CRM sees the visit. Cadence does not ping the morning of.

05

Remind once, then hand off

The specialist walks in with the transcript, not a cold sheet.

06

Review no-shows in Reporting

Source, owner, and hold status live on the same record.

Nurture playbook

Aged list

A name still needs an owner

Import → SMS → book or stop

Dormant list → new thread

List

Last season ADF

Imported

SMS

Still looking?

In-stock match

Loop

Held or opt-out

Closed

Consent stays Human override No third-party mill
Nurture

Reviving aged and dead leads

Last season’s ADF is still a name. Give it an owner and a reason to reply.

Rehash without a second spam blast. Cadence with a human override, then stop when they book or opt out.

01

Import the dormant list into one stream

Do not blast from a personal phone. Keep consent and rooftop with the record.

02

Start a new thread, not a new mill

AI SMS with the unit they asked about or the closest in-stock match.

03

One owner watches the replies

Team Inbox. A human jumps in when they say “still looking.”

04

Book or close the loop

Held visit writes back. Opt-out stops cadence. No third-party resale.

05

Keep the CRM honest

Aged does not mean invisible. Status updates on Lightspeed, Aimbase, DP360, BoatCrazy, or ADF.

Qualification playbook

Intent

Questions before the desk

Unit · timeline · trade · visit

Same questions → transcript

Unit

24 in stock

Grounded

Trade

On the thread

Captured

Desk

Closer ready

Handoff

Standard questions Real inventory Transcript on CRM
Qualification

Qualifying buyers before the floor burns time

The closer should walk into a thread that already has intent, not a name and a guess.

Ask the same questions on every ping so the specialist is not reconstructing the story at the desk.

01

Standard questions in the first replies

Unit, timeline, trade, and how they want to visit on SMS or the call.

02

Ground answers in inventory

No invented trims. If it is not on the lot, say so and offer the next unit.

03

Score the thread for the owner

CRM Sales IQ sits on the same record. The floor sees why this ping is next.

04

Hand off with the transcript

Team Inbox → CRM. The closer does not start from zero.

Reporting playbook

Standup

Metrics next to the thread

First-touch · owner · hold

Thread → Reporting → standup

Touch

By source

On record

Owner

Inbox empty

At close

Hold

Visit booked

Converted

No vanity chats Write-back checked GM can click in
Reporting

The lead scorecard a GM can run

Track the numbers that already live on the thread not a dashboard nobody opens.

First reply, owner, held visit, write-back. That is the scorecard. Use it in standup.

01

First-touch time by source

Facebook vs ADF vs site form on the same stream.

02

Owner coverage

Unassigned threads are the leak. Team Inbox should be empty at close.

03

Held visits vs conversations

A reply is not a slot. Calendar Booking is the conversion event.

04

Write-back completeness

If the CRM never saw it, the floor will not work it.

05

After-hours share

Pings after close should still have an owner by morning.

06

Review in Reporting, not a spreadsheet

The metrics sit next to the thread so a GM can click into the story.

FAQ

Questions before you pick a play.

After hours, first reply, held visits, and write-back - in plain language. The full list lives on the FAQ page.

All FAQs

No. Most rooftops start with after-hours and speed-to-lead so nights and first reply are owned. Booking, nurture, qualification, and reporting layer on once Team Inbox is the single stream.

No. Sources forward in, AI drafts the first SMS, and one specialist owns the thread. Calendar Booking offers a real Saturday slot. The morning closer opens Lightspeed, Aimbase, DP360, BoatCrazy, or ADF Email with context - not a pile of Unread.

The play lives on the same thread as the buyer. First reply, owner, held visit, and write-back sit together. Nobody reconstructs the story from a shared inbox or a personal phone.

No. Aged names import into one stream with consent and rooftop on the record. Cadence starts a new thread. A human jumps in from Team Inbox. Held visit or opt-out stops it. No third-party resale.

Yes. Owner, transcript, and held visits write back to Lightspeed, Aimbase, DP360, BoatCrazy, ADF Email, or your API - per rooftop, so Hudson does not eat the south lot.

Reporting sits next to the conversation: first-touch by source, owner coverage, held visits, write-back, and after-hours share. Use it in standup. We do not invent a vanity score.

A 20-minute demo on the mailbox and CRM you already run.

View pricing

Enter your information

Privacy Policy.
By submitting, you agree to be contacted regarding your inquiry. Consent is not a condition of purchase.