A response-time report is misleading when it starts a clock while the department is closed or routes a request to a team that cannot act. Define lead hours by department and make the after-hours experience part of the workflow.

Map department calendars

Record sales, service, parts, finance, internet, and location schedules, including holidays, closures, time zone, and overnight rules. Use the calendar that matches the request, not a single company-wide default.

Define the after-hours promise

Confirm receipt, state the next staffed response window, and offer a safe self-service or urgent path when appropriate. Do not make an automated acknowledgment sound like a personal response.

Keep source and vehicle context

Carry stock number, service, customer preference, source, and original timestamp into the queue. The CRM routing business-hours checklist helps set fallback and escalation ownership.

Start and stop the right clock

Separate receipt, assignment, acknowledgment, human response, appointment, and resolution. Stop follow-up when the customer replies, books, declines, opts out, or the vehicle or service context changes.

Alert without noise

Escalate unassigned, overdue, urgent, failed-delivery, and wrong-department leads. Suppress duplicate alerts and keep sensitive contact details out of broad channels.

Measure actual service

Report response by department, hours, source, request type, and outcome. Track after-hours queue age, reassignment, missed targets, duplicate contact, and qualified conversation rather than only raw lead count.

Lead reports making the team look slower or faster than reality? Ask Vertinus to align response metrics with department hours.