AI Automotive Lead-to-Appointment Playbook

When a vehicle sells between a customer's first message and the calendar write, an instant appointment confirmation becomes a broken promise. This playbook moves one vehicle inquiry to a verified answer, accepted salesperson handoff, or confirmed appointment while keeping price, finance, trade-in, warranty, and safety commitments with authorized people.

Copy the pilot card below into a document or spreadsheet and begin with one vehicle and one appointment request. If the inventory record or the person accepting an exception is unknown, stop and repair that gap first.

Copy the pilot card and define completion

Vehicle transition	Source to check	Allowed result	Stop or human handoff
When [vehicle request] occurs, move from [start] to [end]	[inventory, listing, and calendar source]	[answer, appointment, alternative request, or no action]	[status/commitment conflict and receiver]

• Start: one lead break has an owner, baseline, authoritative inventory/listing source, approved response scope, and appointment capacity.
• End: the person receives a verified answer, accepted salesperson handoff, confirmed appointment, documented alternative request, or stop.
• Evidence: vehicle ID/VIN where appropriate, listing version, request, consent, routing, calendar write, handoff receipt, correction, and outcome.
• Time horizon: one inventory cycle with sold/reserved units, price changes, duplicate leads, test-drive restrictions, trade-in/finance questions, and opt-out.

Roles and prerequisites

Role	Owns	Approves	Receives handoff
Inventory/listing owner	Vehicle identity, status, facts, displayed price	Listing answer	Feed conflict
Sales owner	Customer relationship and alternatives	Commercial next step	Qualified inquiry
Appointment/store owner	Staff, location, vehicle access	Test drive/visit	Scheduling exception
Finance/trade-in/compliance owner	Estimates, applications, disclosures	Sensitive commitment	Finance/trade-in request
Workflow owner	Pilot and expansion	Keep/pause/expand	Cross-team issue

Map vehicle identity, location, status, listing version, price scope, approved specifications, appointment resource, customer permission, duplicate identity, active deal/service issue, and stop state. Define who may quote, appraise, finance, reserve, or substitute.

Phase 1: map the vehicle and lead state

• Owner: inventory owner with sales.
• Inputs: inventory, listing feeds, CRM, calendar, store access and events.
• Actions: trace listing inquiry through answer, assignment, appointment, arrival, deal boundary, follow-up, and stop.
• Output: source/state map with freshness and precedence.
• Exit gate: every automated vehicle fact and next step has an authoritative owner.
• Escalation/rollback: stop when vehicle identity, status, location, or duplicate lead cannot be reconciled.

Google documents structured fields and feed processes for vehicle listings. It supports the need for explicit vehicle/listing state, not a claim that a listing remains current without dealer verification. Review the source.

Phase 2: choose one lead-to-appointment transition

• Owner: workflow owner.
• Inputs: journey evidence, baseline, staffing, reversibility, risk boundaries.
• Actions: select a bounded job such as current vehicle inquiry to test-drive request; define approved facts, prohibited commitments, and no-action rules.
• Output: transition, acceptance criteria, and exception matrix.
• Exit gate: inventory and scheduling can be revalidated before customer confirmation.
• Escalation/rollback: fix feed, roster, or store process before automating when they do not agree.

Phase 3: validate inventory, authority, and appointment capacity

• Owner: inventory owner for vehicle facts; store owner for access.
• Inputs: live status, location, listing version, staff calendar, access rules.
• Actions: recheck status and displayed-price scope; verify test-drive eligibility and physical availability; route trade-in, finance, warranty, safety, and negotiation questions.
• Output: eligible appointment context or human route.
• Exit gate: vehicle, location, staff, time, and authority agree.
• Escalation/rollback: withdraw stale facts and clear unconfirmed holds.

Phase 4: execute and reconcile

• Owner: appointment owner; assigned salesperson accepts context.
• Inputs: eligible context, approved message, live calendar/inventory events.
• Actions: write one appointment using duplicate protection; confirm only after calendar success; recheck vehicle status before reminders; preserve corrections.
• Output: booked, changed, cancelled, alternative-requested, stopped, or human-owned state.
• Exit gate: inventory, CRM, calendar, salesperson, and customer-facing states match.
• Escalation/rollback: suppress confirmation/reminder after partial write or status change and route a transparent correction.

NIST's AI RMF Core describes governance, mapping, measurement, and management functions. It is a general risk-management reference, not certification of this workflow. Review the source.

Phase 5: review and expand by dealership cell

• Owner: workflow owner with store and compliance owners.
• Inputs: valid responses, appointment reconciliation, status conflicts, handoffs, complaints, opt-outs.
• Actions: review by store, vehicle class, channel, language, source, and stage; inspect every stale-listing and commitment error.
• Output: signed keep/pause/expand decision.
• Exit gate: pre-set quality thresholds hold under representative inventory changes.
• Escalation/rollback: disable the affected store/feed/vehicle-class cell.

Fictional completed run

A fictional dealer pilots used-hybrid enquiries. A customer requests a Saturday test drive for vehicle H-204. The initial retrieval shows available, but a second check before calendar write shows sold. The workflow does not confirm or silently substitute another car. It explains the status change and sends the original request to a salesperson. The salesperson accepts, verifies two alternatives, and asks the customer whether either is relevant. A trade-in value question remains human-owned because no inspected vehicle or approved estimate exists. The run proves status-change rollback and accepted handoff; no sales result is claimed.

Vehicle transition	Source to check	Allowed result	Stop or human handoff
H-204 enquiry to Saturday test-drive request	Inventory/listing version, vehicle access, and staff calendar	Confirm only if the same vehicle remains available; offer alternatives only after customer choice	Sold status blocks confirmation; trade-in value goes to the finance/trade-in owner

Handoff, QA, and measurement

The Trigger column is the join key between the two compact tables.

Trigger	Severity	Owner
Sold/reserved/location conflict	High	Inventory/store
Finance/trade-in/price commitment	High	Finance/trade-in/compliance owner
Safety/warranty/condition ambiguity	High	Appointment/store owner

Trigger	Required context	Response target	Fallback
Sold/reserved/location conflict	Vehicle ID, versions, location, requested time	Before confirmation	Withdraw and human alternatives
Finance/trade-in/price commitment	Original request, vehicle, known facts	Before estimate/promise	Human-only route
Safety/warranty/condition ambiguity	Vehicle, source, exact question	Before answer	State limit and route

QA checks: vehicle identity; feed freshness; price scope; location; access; staff calendar; duplicate lead/appointment; consent; commitment boundary; accepted handoff; reminder recheck; rollback.

The Metric column is the join key between the two compact tables.

Metric	Definition	Baseline
Valid-response rate	Responses backed by current vehicle, listing, permission, and authority / attempted responses	Pre-pilot replay
Appointment reconciliation	Due appointments matching inventory, calendar, salesperson, and customer states / due appointments	Pilot
Stale-status conflict rate	Responses/actions corrected or cancelled for status change / attempted actions	Pre-pilot audit

Metric	Decision threshold	Owner	Cadence
Valid-response rate	Set before launch	Inventory owner	Weekly
Appointment reconciliation	Set before expansion	Store owner	Weekly
Stale-status conflict rate	Pause threshold pre-set	Workflow owner	Weekly

Failure	Early signal	Corrective action
Wrong vehicle, phantom stock, or hidden price scope	Vehicle ID/version/status or displayed-price scope differs across sources	Withdraw the answer and let the inventory/listing owner reconcile it
Invalid appointment or silent substitution	Access/resource check fails or a different vehicle appears without customer choice	Cancel the hold, state the change, and route to the appointment/store and sales owners
Unauthorized commitment, reminder, or handoff	Finance/trade-in wording lacks approval, status changed, or no owner accepts	Suppress the message and require the declared authorized owner to accept the case

Pause the affected store, feed, or vehicle-class cell until correction is verified.

Frequently asked questions

Should AI recommend an alternative vehicle automatically?

Only within an approved, transparent matching rule and after revalidating each alternative. Otherwise ask permission or route to sales; never conceal that the requested vehicle changed.

Can it quote a trade-in value or monthly payment?

Not unless an authorized, reviewed process supplies the required inputs, disclosures, and approval. This playbook keeps those requests human-owned.

When should inventory be checked?

Before the answer, before appointment confirmation, and again before a reminder when status can change materially.

What belongs in the salesperson handoff?

Original request, vehicle/version, channel and permission, appointment preference, facts sent, unresolved question, conflict, and action withheld.

What to do after completion

Limits. This playbook is not vehicle, safety, warranty, financing, trade-in, legal, or purchasing advice. It claims no appointment or sales benchmark, integration, or Easy AI capability.

Use the lead-response guide for the general response contract, the appointment reminder template after revalidation, and the customer-data guide for record ownership.