A Dealership Lead Response Playbook

Map what arrives before choosing the automation

List the channels that produce work: website chat, inbound calls, text conversations, forms, and any other sources your store handles. For each one, identify where the inquiry lands, who answers during business hours, who owns the next action, and what happens after closing. Include service, finance, and parts requests where those departments are in scope.

Review a sample of recent inquiries with the people who handled them. Separate unanswered questions from slow responses, incomplete bookings, and unassigned callbacks. Each needs a different fix. Automating the first acknowledgment will not repair a calendar staff cannot trust or a handoff queue nobody watches. Start with a specific break in the process and describe the desired completed outcome.

Make the first response answer the actual question

A useful first response recognizes what the customer asked and supplies the information you can verify. If a shopper asks about a stock number, check that vehicle before asking broad qualification questions. If the customer wants service, establish the request and the appropriate department. Ask the smallest next question needed to move forward instead of collecting every possible detail at the start.

Distinguish acknowledgment from a substantive response. An automated message saying that someone will reply can reassure a customer, but it does not answer whether the car is available or whether a visit can be arranged. Track both events if you use acknowledgments. Otherwise a fast automated receipt can make the dashboard look healthy while customers still wait for useful help.

Illustrative website-chat reply after checking the record: 'The blue SUV you are viewing is listed as available at $28,500. Are you looking for more details or a time to see it?' The vehicle and price in this example are fictional. In a live conversation, every factual detail should come from the store's current records, and unknown information should stay unknown until verified.

Define an after-hours path your store can honor

After-hours coverage needs two paths: actions the system can complete now, and requests a person must handle later. Publish and configure department hours accurately, including exceptions. An assistant may be available overnight while the service advisor is not. The customer should understand whether they have a confirmed appointment, a requested appointment, or a callback waiting for the next staffed period.

For a supported booking, check current availability and obtain confirmation before saving the visit. For an unresolved question, capture the relevant details and assign a follow-up owner. Avoid promising a callback time unless your team has committed to it. At opening, have the designated staff member review overnight requests before starting unrelated outbound work.

Illustrative callback acknowledgment: 'The sales team is closed now. I have recorded your question about the trade-in and passed it to the sales team for follow-up.' Use that language only after the handoff is actually saved. If a system cannot create a request, it should explain the available contact route instead of claiming that someone has been notified.

Give every handoff an owner and a definition of done

Name the role responsible for each department's queue and define how coverage changes during breaks, absences, and busy periods. A shared inbox can be useful, but shared visibility is different from assigned responsibility. Staff should be able to tell whether a request is waiting, being handled, or complete without reading every transcript from the beginning.

Set a practical definition of done for each request. A callback is complete when the required contact attempt and result are recorded. A booking is complete when the customer and calendar agree on the appointment. An unresolved finance question belongs with an authorized person even if the assistant has gathered all the introductory details. Review aged open work with the same attention as new inquiries.

• Identify the customer and preferred contact method.
• Record the vehicle, department, and original request.
• Show the facts already checked and actions already completed.
• Assign the outstanding decision or follow-up to a named owner.
• Record the result so the next person can continue.

Follow up with a reason, then respond to the customer's intent

Follow-up should reflect why the conversation is open. A missed appointment, a question about an unavailable car, a lease ending, and a service request are different situations. Decide which events create follow-up, which channels are allowed for that customer, who approves the message, and what stops the sequence. Review your approved contact process before enabling outbound messages.

A reply should change the next step. If the customer has bought elsewhere, close the sales follow-up. If they need a different date, work that request. If a staff member has taken ownership, avoid competing automated messages. Preserve opt-outs and other contact restrictions in the system that controls sending; a note in a transcript is not enough if scheduled messages can ignore it.

Illustrative missed-visit message: 'Hi Jordan, this is the team at Example Motors. Would you like help finding another time for the visit you missed?' Illustrative availability message: 'You asked us about a compact SUV. Would you like us to check current options for you?' These fictional examples illustrate intent, not approved templates or a recommendation to contact any particular person.

Choose cadence using your store's results and customer preferences. More attempts can create more work without creating better outcomes. Examine replies, opt-outs, complaints, appointments, and staff interventions together. Do not keep a sequence running merely because the next scheduled step exists; its purpose is to help the customer reach a useful decision.

Measure a customer journey rather than message volume

Define your reporting cohort before comparing results. Use the same source, department, and date window, and exclude internal tests and duplicate records consistently. Separate customers who first inquired during the period from appointments scheduled or attended during the period. Those groups answer different questions and should not be mixed into a single conversion rate.

Response time should measure the interval from the inquiry to the first useful answer, with acknowledgment time tracked separately when needed. Review the median and a slower-response percentile so a few instant answers do not hide a backlog. Segment business-hours and after-hours inquiries to understand whether coverage improved where the original problem occurred.

Separate a business case from a performance claim

Build the initial business case using your own call volume, lead counts, appointment results, and costs. Label assumptions clearly. Estimated recovered opportunities are a planning scenario; they are not booked revenue, profit, or proof that an assistant caused a sale. If you use an ROI calculator, review its assumptions before presenting its output to the team.

During a pilot, compare like periods and keep the original inquiry source attached to each customer journey. Note changes in marketing spend, inventory, staffing, and promotions that may affect the result. A before-and-after improvement can be encouraging without isolating the effect of one tool. Read a sample of the actual successful and unsuccessful conversations before deciding what to expand.

For illustration only, if 40 confirmed appointments out of 100 eligible inquiries meet your reporting definition, the booking rate is 40%. If 30 of those 40 due appointments are attended, the show rate is 75%. Those invented counts explain the formulas; they are not Paddock results or industry benchmarks. Keep the denominator visible whenever you report a percentage.

Create a review routine that survives a busy week

At opening, review overnight requests and appointments that need staff preparation. During the day, watch the assigned queues and take over conversations that need judgment. At a regular review, inspect a sample across departments, channels, successful bookings, unresolved requests, and customer contact preferences. Assign a concrete owner for each process fix you decide to make.

Repeat the relevant checks after changing hours, inventory connections, appointment rules, contact routing, or automation settings. NIST's AI Risk Management Framework emphasizes continuing evaluation in operation; the dealership-specific routine here is our practical recommendation for applying that principle to customer communication. The process should evolve as your store's requests and staffing change.

Paddock brings website chat, phone and text conversations, follow-up campaigns, appointments, and handoffs into one staff console. Use the linked product pages to review each workflow and the evaluation checklist to test your proposed setup. Start with the channel where your own records show the clearest gap, then expand based on accurate outcomes and the team's ability to handle the resulting work.