OperationsHome, Commercial & Field Servicesdispatchschedulingtechnician

Field Services Dispatch Brief

Turn a raw work order into a clean dispatch brief a technician can act on in the field.

When to use this

Use this when a work order lands as messy details and the assigned technician needs a clean brief before rolling out. It is most valuable for jobs with access quirks or safety notes that get lost in a raw ticket.

The prompt

You are the dispatch coordinator for a field services company. Using the raw job details below,
write a dispatch brief to send to the assigned technician.

Job details: [CUSTOMER_NAME], [SERVICE_ADDRESS], [JOB_TYPE], [SCHEDULED_WINDOW], [EQUIPMENT_OR_UNIT],
[REPORTED_ISSUE], [ACCESS_NOTES: e.g. gate code, pets, parking], [PRIOR_VISIT_NOTES].

Produce, in this order:
1. A one-line job summary suitable for a dispatch board.
2. A briefing for the technician covering what to expect, what tools/parts to bring based on
   [REPORTED_ISSUE], and any access or safety notes.
3. A customer-facing SMS confirming the appointment window and technician name [TECH_NAME], with a
   link to reschedule at [RESCHEDULE_LINK].

Rules: keep the technician briefing under 120 words; flag clearly if [ACCESS_NOTES] mentions a pet
or safety concern; do not invent parts or diagnoses not implied by [REPORTED_ISSUE].

Replace the [BRACKETED] placeholders with your business's details, then paste into ChatGPT, Claude, or the AI tool you already use.

How to customize it

Put anything about pets, gates, or hazards in [ACCESS_NOTES] — the prompt is told to flag those clearly.
Fill [REPORTED_ISSUE] with the customer's words so the tools and parts suggestion stays grounded.
Send the customer-facing SMS separately from the technician briefing so nothing internal leaks out.
Leave [PRIOR_VISIT_NOTES] in if it is a repeat call — it changes what the tech should expect.