Requester owns the request. Dispatch owns the delivery.
People ask for deliveries where they already work, in Requester. Dispatch decides whether and when they can happen, who does them and what happened — and keeps Requester told.
One delivery, start to finish
- Day before, 11:00Day before, 11:00Requester
A delivery is requested
Ayesha at the One Galle Face showroom raises a delivery for order ES-4471 in Requester: the customer, the address, Wednesday 10:00–12:00, a small truck and a helper.
- 11:0111:01Dispatch
It lands in the inbox with a suggestion
Dispatch checks small-truck capacity in that window, the load, the opening hours and the crew, and says it fits.
- 11:1511:15Dispatch
Confirmed in one click
Kamal, the dispatcher, presses Confirm. The slot is held and Requester shows the delivery as confirmed. Ayesha doesn't need to call.
- AfternoonAfternoonDispatch
Tomorrow is planned
Kamal puts Wednesday's confirmed jobs on trips, gives each a vehicle, a driver and helpers, and checks the board for clashes.
- 17:0017:00Dispatch
The day is published
Publishing sends each requester the arrival time and vehicle: “Planned for Wed 06 Mar, arriving around 10:40 · CAB-2214”.
- WednesdayWednesdayDispatch
Changes look after themselves
If a job has to move, Kamal reschedules it and Requester shows the new day and window. If it's cancelled, the reason goes with it.
What Dispatch is built to do
One touch per person
The requester fills in a form once and the dispatcher confirms once. Anything more is the exception.
Dispatch proposes, people decide
Dispatch works out whether a request fits and suggests the answer. Your dispatcher accepts it or changes it.
Promise first, plan later
Confirming holds a slot: a day, a window and a vehicle type. The exact truck and driver are chosen when the day is planned.
Nobody chases anybody
Decisions, new times and arrival times go back to Requester on their own, so nobody has to ask.
Facts, not re-typing
Reports come from what happened in Dispatch. Nothing is typed in twice or quietly overwritten.
Your words, not codes
Reasons and statuses reach Requester as plain sentences that anyone can read.
A place for everyone in the team
| Role | Works in | Does |
|---|---|---|
| Requester | In Requester | Raises requests and answers suggested new times. |
| Internal requester | In Dispatch | Raises requests for warehouses, stores and factories, and answers suggested times. |
| Dispatcher | In Dispatch | Decides requests, plans trips and handles the day. |
| Fleet admin | In Dispatch | Looks after vehicles, drivers, locations, documents and settings. |
| Manager | In Dispatch | Follows the dashboard, the planning board, trips and reports. |
| Owner | In Dispatch | Everything a fleet admin does, plus the organisation's name and time zone. |
Run tomorrow’s deliveries from one screen.
Connect your Requester workspace and Dispatch is ready for your first request. Your team signs in with the Requester accounts they already have.