Why capacity promises need a source of truth
When phones, forms, and messages stack up during busy weeks, teams can accidentally promise the same opening to multiple customers, imply emergency priority, or let AI turn a rough note into a confirmed schedule. A capacity/waitlist card keeps the customer informed while protecting dispatch reality.
STOP AUTOMATION: do not promise arrival windows, same-day service, emergency priority, cancellation-list placement, discounts, or crew availability from AI output alone. A dispatcher/owner must verify live calendar capacity, service area, crew skill, part availability, travel time, safety priority, and customer consent before confirming.
Capacity and waitlist intake card
| Field | What to capture | Human review rule |
|---|---|---|
| Customer/job need | Name, contact, service type, location, urgency, safety issue, access limits, preferred times. | Separate verified urgency from customer preference; do not let AI assign emergency priority. |
| Capacity source | Calendar screenshot/link, dispatch board, crew count, skill needed, parts/equipment needed, travel zone. | Use the live dispatch source, not a stale note or memory. |
| Waitlist status | Earliest confirmed option, cancellation-list eligibility, backup window, next update time, owner. | Waitlist does not mean guaranteed service unless a slot is actually assigned. |
| Customer-safe wording | Acknowledge demand, give the verified next step, and avoid unsupported availability claims. | Use review-status language when the schedule is not confirmed. |
| Escalation triggers | Safety issue, vulnerable customer, property damage risk, repeat no-contact, high-value job, or SLA promise. | Owner/dispatcher decides priority; AI can only flag the possible trigger. |
| CRM closeout | Label, owner, due time, promised update, waitlist rank/status, confirmed slot, cancellation reason. | Every waitlist lead needs a next touch; no orphaned “maybe” leads. |
Copy/paste customer replies
Hi [Name] — thanks for reaching out. We are checking crew capacity for [service/location] now. I do not want to guess on timing, so I will verify the dispatch board and update you by [time].We do not have a confirmed opening for [requested time] yet. The earliest verified option is [option], and we can also keep you on the cancellation list if you want a call/text if something opens sooner.CRM note: capacity/waitlist lead. Service: [type]. Location: [area]. Urgency/safety: [verified facts]. Live capacity source checked: [link/time]. Owner: [person]. Next update due: [date/time]. Do not promise arrival window until dispatch confirms.AI dispatch review prompt
Act as a cautious local-service dispatch capacity reviewer. Use only the verified facts below. Do not invent availability, arrival windows, crew skill, emergency priority, pricing, discounts, parts, diagnosis, warranty, or customer consent. Return: 1) missing fields, 2) risky promises in the draft, 3) customer-safe waitlist wording, 4) dispatch/owner questions, and 5) a STOP AUTOMATION decision if scheduling is not ready.
Verified facts:
- Customer/job need:
- Location/service area:
- Live calendar/dispatch source checked at:
- Crew/skill/part constraints:
- Earliest verified option:
- Waitlist/cancellation-list policy:
- Customer update deadline:
- Stop rules:Fast QA before replying
- Check the live dispatch board before sending any time window or cancellation-list promise.
- Mark safety or property-damage triggers for human triage instead of letting AI prioritize.
- Give a specific next-update time when there is no confirmed opening.
- Keep waitlist leads in the CRM with owner, due time, and status so they do not disappear during busy season.
Related free assets: Appointment Confirmation Text Templates, Missed Callback Owner Changeover Checklist, and Lead Channel Coverage Audit Checklist.
Disclosure: Horizon Flow is Andrew Burton's digital product catalog. This worksheet is useful without purchase; product links are labeled and UTM-tagged.