Bring Five Test Cases to Your Dispatch Software Demo
By STEADYWRK Team
A useful dispatch demonstration starts with a request that your team would recognize and an outcome you can inspect. Before the call, write down what should happen when information is missing, someone changes a booking, or two people act on the same request. A smooth prepared example cannot answer those questions by itself.
The five cases below are synthetic exercises, not STEADYWRK customer records or a promise that any particular product supports the behavior. Use them to ask what the product does today, what needs configuration and what remains a manual step. Download the CSV worksheet, open a copy, and replace the fictional site names with neutral labels for your own workflow.
Define the boundary before the call
Choose one workflow: for example, receiving a maintenance request and handing it to the person who can schedule a visit. Keep quoting, approval, assignment and completion as separate events. A request arriving does not mean a visit is booked; a quote being prepared does not mean a customer accepted it.
Write a short starting record:
| Field | Synthetic example |
|---|---|
| Request ID | DEMO-101 |
| Site | Site A |
| Reported problem | A light is not working in the meeting room |
| Requested window | Morning; exact date still missing |
| Approval | Not yet requested |
| Assignment | Unassigned |
The missing date is intentional. Ask the demonstrator to preserve that uncertainty. If a default date appears, establish whether it is a suggestion, a stored value or a confirmed booking. Record the answer using the product's actual labels.
Case 1: required information is missing
Try to continue without the visit date or a usable site reference. Look for a clear explanation of what is missing and a way to save or recover the unfinished request. Then supply the missing information and try again.
Your evidence should show both attempts. A blocked first attempt may be correct behavior. A successful second attempt should retain the details you already entered. Ask who is responsible for obtaining the missing information if the request arrives outside working hours; a software field does not establish that responsibility.