Describe your dispatch workflow. Makeform turns it into a form for the job, location, urgency, assignment, schedule, and completion notes.
Route dispatch requests to email, Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a starting point, adjust it, and send it to the builder. Each example shows an intended structure.
Audience
Dispatchers assigning technicians to customer sites
Format
Service request with priority and technician assignment
Prompt size
285 chars
Example form structure
Service request with priority and technician assignment
Customer and callback number
Service location and access instructions
Issue, equipment, and photos
Priority and requested arrival window
Assigned technician and dispatch status
Suggested routing tags
Unassigned
In progress
Completed
Ask for the time window and access constraints, not only the address.
Step 1
Log
capture the request, location, and time window
Step 2
Triage
review urgency, access, and required skills
Step 3
Assign
send the job to a crew, driver, or technician
Step 4
Close
record the result, exception, and follow-up
Why dispatch intake matters
A structured dispatch form shows who should go, what they need, where they should arrive, and when the job is finished.
Require the address, callback number, issue category, time window, and access notes before queueing.
Use priority, territory, service type, or skill as structured routing choices.
Keep assignment, arrival, outcome, exception, and follow-up tied to the request.
Dispatch scenarios
Choose a scenario, then add your teams, territories, priorities, and statuses.
Match equipment type, required skill, territory, and availability to a technician assignment.
Capture pickup, drop-off, package handling, route, delivery window, and exceptions.
Surface location hazards, immediate impact, caller availability, and escalation contacts before dispatch.
Standardize requests from branches, facilities, warehouses, and customer support teams.
Build your workflow
Define the details that change an assignment, then build a clear path from intake to closure.
Describe requesters, job types, priority choices, and the details needed for assignment.
Add territories, crews, services, and statuses. Show specialized questions only when relevant.
Send submissions to dispatch with the reference, priority, location, contact, and time window.
Test routine, urgent, and incomplete requests, then verify the crew's closing path.
Form vs phone notes vs spreadsheet
Consistent fields make a dispatch queue easier to scan, hand off, assign, and review.
Field guide
Use short intake questions, structured routing choices, and internal assignment and completion fields.
Request identity
Capture the requester, callback channel, and an order, asset, ticket, or customer reference.
Location & access
Collect the address, unit, gate, dock, landmark, and access instructions separately from the issue.
Job scope
Start with a category, then show its relevant questions, equipment details, or handling notes.
Priority & constraints
Ask what is affected, when service is needed, and which site conditions were observed.
Assignment
Use internal choices for territory, route, assignee, vehicle, and status, plus dispatch and arrival times.
Completion & exception
Capture times, work or delivery result, exception reason, evidence, and any required follow-up.
Related tools
Connect intake with delivery details, maintenance requests, inspections, repairs, incidents, and transportation records using related Makeform generators.
Capture destination, recipient, schedule, handling notes, and delivery outcomes.
Open toolCollect repair symptoms, location details, access notes, photos, and preferred service times.
Open toolStandardize maintenance intake before a dispatcher assigns the appropriate trade or crew.
Open toolDocument vehicle condition before or after a driver starts a dispatched route.
Open toolRecord structured details when a service visit, route, or delivery includes an incident.
Open toolGather passenger, trip, schedule, pickup, destination, and coordinator information.
Open toolFAQ
Practical answers for dispatchers and operations teams replacing scattered request notes.
A dispatch form logs a service, delivery, maintenance, transport, or assistance request for assignment. It captures the requester, location, job, priority, schedule, access, assignee, status, and outcome.
Include a reference, requester contact, location, category, scope, time window, impact, and access instructions. Internal fields can cover priority, territory, assignee, vehicle, dispatch time, status, outcome, exception, and follow-up.
Yes. Use a request-type question and conditional paths for service or delivery fields. Both can share contact, address, schedule, priority, assignee, and status fields.
Ask for operational impact, response time, site conditions, callback contact, and the escalation reason. Use a structured priority choice and send urgent submissions to the appropriate notification path.
The form can collect routing inputs for connected workflows. Territory, category, or priority can pass to email, Slack, Google Sheets, Zapier, or another assignment workflow. Test every route.
Use a clear request reference with arrival, status, outcome, exception, photo, and follow-up fields. An internal form or connected system can key updates to that reference.
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and use your dispatch form without a response cap. The paid tier removes the Makeform badge.
Test routine, urgent, incomplete, and conditional requests. Check required fields, notification details, routing destinations, mobile usability, and whether closure updates retain the reference.
Give every request a clear next owner.
