An appointment request should reach the person who can actually schedule it, with enough vehicle and service context to respond quickly. Routing rules need to account for departments, hours, duplicate requests, and unavailable staff.
Classify the request
Capture sales, service, parts, finance, trade-in, test drive, delivery, or other intent along with vehicle, location, preferred time, source, and customer permission. Use clear fallbacks when a visitor chooses an unknown option.
Match staff and availability
Define department, location, appointment type, resource, hours, holidays, lead ownership, and scheduling constraints. Do not promise a slot until the scheduling source confirms it.
Preserve source and context
Carry campaign, page, vehicle, service, reference, and prior conversation context into the CRM or scheduling system. Keep the original timestamp and source when records are merged or handed off.
The lead source tracking guide and response dashboard checklist depend on these fields.
Confirm and escalate
Send an acknowledgment that distinguishes request from confirmation, assign a response deadline, and escalate when no owner accepts the lead. Give staff a safe way to update status without creating a second appointment.
Handle duplicates and privacy
Link repeated submissions carefully, protect contact and vehicle data, limit access, and avoid putting sensitive information in notifications. Respect channel permissions and retention.
Measure the routing path
Track valid requests, assignment, acknowledgment, response time, booked appointments, no-shows, handoffs, duplicate records, exceptions, and lost leads by department and source.
Appointment leads arriving in the wrong queue? Ask Vertinus to map routing by intent, department, and availability.