One lead, two acts
A lead’s first hour, then the week.
This tour follows one internet lead through CarBot, start to finish. Act I is Pam’s first hour — an after-hours text answered from live inventory, her trade-in photos filed, a human-first callback. Act II is the week after — a reschedule, eLead write-back, a cadence for a quieter lead, and the manager’s QA review.
CarBot answers in nine seconds.
The text lands after everyone’s gone home. CarBot replies from your registered number, checks the CR-V against live HomeNet inventory, and offers two real test-drive slots.
Her trade-in photos land on her record, not a phone.
Pam texts two photos of her Pilot and asks what it’s worth. The MMS files into her thread — attached to Pam, not to whoever’s phone was on.
CarBot doesn’t quote a trade number by text. It points her to an in-person appraisal, right before the test drive she already booked.
See the one-inbox thread →The lead lands on the board, already warm.
Pam appears in the kanban with a score, the booked appointment, her trade-in photos, and the full thread attached. eLead gets the write-back; nobody retypes anything.
Jim’s phone rings before Pam’s does.
The human-first sequence dials Jim’s cell, whispers the context — “Pam, CR-V, test drive at 4:30, asked about trade value” — then connects Pam. She hears a prepared person, not a cold transfer.
CarBot passes Pam to Jim mid-call. She never starts over.
Pam calls the main line with one more question for Jim. CarBot answers as the store’s AI assistant, already holding her thread, and puts her through.
As Jim picks up, CarBot whispers who’s calling and why, then bridges the call. AI to human is a relay pass, not a cold restart.
How human-first calling works →Both calls are graded before the coffee’s cold.
Transcript, sentiment, and a grade land in QA reviews. The manager’s digest shows what booked overnight, what needs a callback, and who earned the spiff.
Act II · The week CarBot didn’t let go
The first hour is table stakes — the week is where deals are won.
Pam moves her test drive by text. The calendar absorbs it.
CarBot’s reminder goes out. Pam replies a minute later — something came up at four, is there anything earlier?
CarBot checks the real calendar, capacity rules and all, moves her to 1:15, and releases the 4:30 slot. Nobody on the floor touched it.
How real-calendar booking works →She walks in, and eLead already has the whole story.
The showed disposition writes back to eLead on its own — next to every text, both call recordings, and the moved appointment. Jim reads the trail, not a sticky note.
Had she not shown, the no-show follow-up would have picked her up instead.
See what writes back to eLead →Marcus goes quiet. The cadence doesn’t.
Not every lead is Pam. Marcus asked about an Accord Hybrid on Sunday, got his answer, and stopped replying.
The BDC cadence keeps working him — a day-3 call, a day-5 text in the store’s voice. Before every touch, the platform checks his consent and the quiet hours.
Every call graded. The manager opens one.
The week’s calls are already graded on greeting, discovery, and the appointment ask. The manager scans the distribution and opens the one flagged call.
The customer had asked to be called Monday, so the missed ask wasn’t one — the manager overrides the grade. Run a second store? Same login, switch rooftops, each one walled off.
See QA grading and manager overrides →Pam’s week: two calls, three text exchanges, one showroom visit — all of it in eLead, none of it typed by hand.
See the whole week on your own leads.
A 30-minute demo with your inventory, your hours, and your CRM — from the first after-hours text to Friday’s QA review. No slideware.