Auto service calling playbook for the service desk

What this playbook covers

Fixed ops phone work is calendar arithmetic: fill tomorrow’s lineup, revive declined work, keep no-shows down. This playbook covers the three queues, block structure, cadence, dispositions, the three-line workflow, and KPI ranges against production reference points. One principle sits above all of it: the customer book is a relationship asset, and the dialer’s job is to prove the store remembers the customer, not to extract the next invoice.

List building and hygiene

Three queues, each with its own rhythm:

Open recalls. Rows come from the manufacturer’s notice and parts-availability records, with the notice date on the lead. The call schedules covered work; it never substitutes for the notice, and it never interprets safety scope. If parts are unavailable, the customer does not get a call promising one.

Declined work. Items declined 90 or more days ago, each row carrying the last visit date and the written estimate. The service visit within 540 days is the established business relationship under 16 CFR 310.2, so hygiene here mostly means accuracy: right customer, right item, right last visit.

Tomorrow’s book. Every appointment due for confirmation. A two-way text from the dialer number counts as a touch and catches reschedules early.

Mechanical hygiene: internal do-not-call suppression before import; National DNC scrubbing refreshed at least every 31 days for any cold campaign beyond the book; 8 a.m. to 9 p.m. local hours under 16 CFR 310.4(c) and 47 CFR 64.1200(c)(1); bad numbers dead on second confirmation.

Call block structure

Morning block, 8:00 to 10:00. Recall and declined-work calls. Commuters answer before work; the shop is quiet enough for the desk to breathe. This block owns the highest booking density of the day.

Midday block, 11:00 to 12:30. Second attempts from the morning, plus inbound overflow callbacks promised at the counter.

Afternoon block, 1:30 to 3:00. Tomorrow’s confirmations. Every scheduled customer gets a call or a text; unconfirmed rows get a live attempt first thing the next morning.

Late window, 5:00 to 6:30. Working customers unreachable all day, plus declined-work touches that need a conversation rather than a booking.

All calls respect quiet hours at the customer’s local time, computed per row by the dialer.

Attempt cadence

Four touches, then a hard stop:

1. Day 1. Live call from the history opener. Book it or log the refusal.
2. Day 3, different daypart. The catch-the-customer attempt.
3. Day 7. Text with one concrete slot from the dialer number.
4. Day 10. Final live call with an honest close: “I will leave the estimate on file and stop bothering you; the offer does not expire.”

Refusals exit the cadence the day they happen and live in the log with their reason. No-shows get one recycle attempt within the week, a new slot, and zero guilt. Attempt caps in the dialer enforce all of it; a desk should never be deciding from memory.

Dispositions and what they mean

• Recall booked: slot, parts confirmed, shuttle flag, confirmation text sent.
• Recall refused: reason logged, customer thanked, cadence ended. The log is the store’s protection and its future conversation.
• Declined work rescheduled: new slot against the written estimate, advisor briefed.
• Appointment confirmed: two-way yes in hand; the lineup trusts these rows.
• No-show: one dated recycle, new reason, no guilt script.
• Bad number / Left voicemail / Do not call: the mechanical set, honored same day.

The three-line workflow and AI summaries

Three lines fit the desk when blocks stay short and the board carries the memory:

• The queue order is the strategy: recalls by parts-arrival date, declines by estimate age, confirmations by tomorrow’s lineup.
• Quote from the ticket or promise a re-run; never improvise a price on a recorded line.
• Keep the recall lane bright: scheduling support, not the formal notice, no safety scope interpretations on the phone.
• Edit the AI summary before the next connect: history, item or recall number, slot, shuttle flag, confirmation sent. The advisor’s first sentence at the car depends on these fields.
• Recording disclosure on in all-party consent states; use it store-wide rather than per-state logic.

KPI targets

Ranges against production reference points. In production use across 3-line sessions over 90 days, the median operator ran about 85 dials per active hour and roughly 600 dials per operator day, with person connects around 17.8 percent. Planning ranges for a service desk:

• Dials per active hour: 60 to 90; book lists with live numbers run at the top.
• Person connects: 15 to 30 percent, above the general benchmark, because the book is real and current.
• Bookings: 25 to 40 per 100 person contacts on recall queues; 15 to 25 on declined work.
• Confirmation rate: 80 to 95 percent of tomorrow’s book confirmed by close of the afternoon block.
• No-show rate: 5 to 10 percent with two-way confirmations, against 15 to 25 percent without them.

These figures are measured in production use, 3-line sessions, 90 days; they are reference points, not a promise of results.

Compliance guardrails

The book’s established business relationship under 16 CFR 310.2 covers recall, declined-work and confirmation calls; cold campaigns beyond the book need National DNC scrubbing refreshed at least every 31 days, 8 a.m. to 9 p.m. local hours under 16 CFR 310.4(c) and 47 CFR 64.1200(c)(1), and immediate opt-out honoring. TCPA wireless rules at 47 CFR 64.1200 apply regardless of list origin. Recall notice duties stay with the manufacturer’s process; the dialer schedules. Several states require all-party recording consent; use the disclosure. DialBreeze applies your internal DNC list, quiet hours and attempt caps. This guide describes rules, not legal advice.