When to use this checklist
- Morning catch-up: after overnight calls, weekend forms, holiday closures, storms, or staffing gaps.
- After a lead spike: when ads, marketplace profiles, seasonal demand, or referrals create more inquiries than the front desk can handle immediately.
- Before automation: if AI or autoresponders are drafting callbacks, the source facts and priority rules need to be clear first.
- Human review rule: a manager should approve any safety, emergency, warranty, refund, financing, legal, or price-sensitive callback before automation sends a promise.
Copy/paste callback queue worksheet
Lead/customer name: [paste]
Channel: missed call / voicemail / web form / chat / text / marketplace / referral / existing customer / warranty / other
Received at: [date/time/time zone]
Response age: under 15 minutes / 15-60 minutes / same day / 1-2 days / older
Need type: emergency/safety / booked-customer issue / quote request / estimate approval / warranty-callback / reschedule / general question / not a fit
Location/service-area fit: in-area / maybe / out-of-area / unknown
Known consent/channel rule: call ok / text ok / email ok / marketplace-only / unknown / do-not-contact
Priority: P1 safety or booked-customer issue / P2 hot lead under one hour / P3 qualified same-day lead / P4 older or low-fit lead / P5 closeout or no-contact
Owner: [front desk / dispatcher / estimator / manager / owner]
Next safe action: [call / text / email / request photos / schedule / manager review / closeout]
Promise allowed? yes / no / NEEDS OWNER REVIEW
Priority rules that prevent bad callbacks
- Safety and active customers first: do not let a warranty, access, safety, or in-progress job issue sit behind cold prospects.
- Fresh qualified leads next: service-area fit, clear job type, and reachable channel beat vague older inquiries.
- Do not invent urgency: if a form says “quote when available,” do not mark it emergency just to speed the queue.
- Respect consent and channel limits: do not text if the only approved path is a marketplace inbox or email.
- Route exceptions to a human: price disputes, refunds, warranties, legal threats, medical/safety claims, and emergency promises need manager review.
- Close stale/no-fit records cleanly: mark why a lead was not contacted again so tomorrow's queue stays honest.
AI queue-summary prompt
You are helping a local service business prioritize a callback queue. Use only the lead records, timestamps, service area, consent/channel notes, job types, current capacity, and owner-approved rules provided. Do not invent urgency, availability, price, diagnosis, warranty coverage, consent, emergency coverage, customer intent, or prior contact history. Return a table with: record ID, priority level, reason, next safe action, owner, promise allowed yes/no, missing facts, and NEEDS OWNER REVIEW flags. If a record involves safety, emergency service, refund, warranty, legal threat, payment dispute, or uncertain consent, mark STOP AUTOMATION.
Callback scripts by priority
- P1 active/safety issue: “Hi [Name], we saw your message about [issue]. I’m routing this to [owner/manager] now before we promise a time or next step. If there is an immediate safety risk, please use emergency services or the appropriate utility/emergency contact.”
- P2 hot new lead: “Hi [Name], thanks for reaching out about [service]. To confirm the next step, can you send [missing detail/photo/address/access window]? We’ll review and confirm whether we can schedule, quote remotely, or need an inspection.”
- P3 same-day qualified lead: “Hi [Name], we received your request and are checking fit and availability. The next safe step is [next step], and we’ll avoid quoting timing or price until [owner/estimator] reviews the details.”
- P4 older lead: “Hi [Name], following up on your request about [service]. If you still need help, reply with [detail]. If not, no worries — we’ll close the request so we don’t keep messaging you.”
- P5 no-fit/closeout: “Thanks for checking with us. Based on [service area/service type/policy], we are not the right fit for this request. We’re closing this record so no one keeps following up by mistake.”
Where this fits in the lead-response system
Pair this queue with the Lead Response SLA Checklist, Lead Routing Checklist, Lost Lead Reason Code Checklist, free speed-to-lead swipe file, and Local Lead Rescue System.