Set a Lead Response-Time Standard That Reflects Branch Staffing and Service Urgency

A lead is not served when it enters the CRM

A paid campaign can produce an accurate, relevant enquiry and still lose the customer if nobody owns the next step. For multi-branch businesses, response delays may vary because one branch has a receptionist, another relies on a manager, and a third routes enquiries through a central team.

Define response in operational terms

Decide what counts as a response: a human call attempt, a meaningful message, an appointment confirmation, or a resolution. An automated receipt is useful but should not be reported as a completed human follow-up. Measure business-hours and after-hours leads separately so the team is not penalised for a window when the branch is legitimately closed.

Use tiers rather than one blanket promise

A suggested framework:

• Urgent, time-sensitive service: route to an explicitly staffed queue and define a short escalation window.
• Appointment request: confirm receipt promptly, then contact within the service's approved booking window.
• General product or course enquiry: assign to the responsible branch or central team with a realistic next-contact expectation.
• After-hours enquiry: send an accurate acknowledgement and specify when follow-up resumes; do not imply 24/7 staffing if none exists.

The actual time targets must be set by operations based on staffing, customer risk and service requirements. Do not copy a generic “five-minute rule” as though it were a platform requirement.

Make ownership visible

Every enquiry should have an owner, branch, received timestamp, due time, last attempt and escalation state. If a branch misses the due time, the system should route it to a backup owner or a central queue according to the agreed process. If the business cannot support automated routing, a shared queue and scheduled review may be enough initially.

Diagnose before blaming advertising

Track response-time percentiles, contact rate, qualification rate and completion rate by branch and time-of-day cohort. A branch with low conversion may have weaker demand, but it may also have missed calls, unassigned leads or inconsistent follow-up. Compare like with like before changing bids.

Example escalation

An enquiry arrives for a service that only one branch provides. If that branch is closed, the system should acknowledge receipt without promising immediate service, place the lead in the named queue and alert the backup owner when the agreed window expires. It should not silently reassign the lead to a branch that cannot perform the service.

Audit the standard monthly

Review overdue leads, unowned records, reassignment frequency and exceptions. Ask branch staff which steps are impractical. If every location misses the same target, the target or staffing model may be wrong—not every branch's discipline.

Link to marketing measurement carefully

Qualified and converted lead stages may be useful in advertising reports, but only after CRM status definitions are consistent. Google Ads supports offline conversion measurement; it does not prescribe this operational SLA. See the offline conversion FAQ.

Deliverable

Publish the tier, operating window, owner, backup, escalation path and reporting definition. That creates a standard teams can actually meet.