Who this guide is for
A dispatcher in Hauler Hero gets every request onto a route, keeps an eye on the day, and gives drivers what they need to finish it. This guide covers those jobs only, written generically so it fits any hauler and any line of business.
In scope: publishing on-request work (deliveries, swaps, finals, extra pickups), assigning and sequencing stops, rescheduling and cancelling work, monitoring routes and driver paths, writing notes and tags drivers will see, supporting drivers on the tablet, and confirming completed work (including disposal tickets) so it is ready for the office.
Out of scope: creating and sending invoices, taking or posting payments, configuring pricing or settings, and building reports. A dispatcher may see the Billing tab to review work orders, but hands off from there.
Every company routes differently. Where this guide says "your company decides," agree the convention with your manager before you start (for example, route names, naming of services, or how often tickets are reviewed).
Your toolkit and a typical day
A dispatcher works mostly in two tabs, Customers and Routes, and dips into Billing → Work Orders Review only to confirm completed work. Ask your admin for a Dispatcher role with Office login turned on, so you see what you need and nothing else (Training Plan for New Office Staff).
Screen | What you do there |
Customers → account → Services tab | Add on-request work, schedule or cancel events, assign a stop, add notes and tags |
Configured service → Map & Routing | Route a service by nearest stop or by route, set sequence |
Routes → Advanced Board | See each route's stops for one day; drag and drop; unassigned bucket |
Routes → List | Quick progress per route (not started, in progress, complete) and stop counts |
Routes → Advanced Map | Where stops and drivers are; driver path breadcrumbs; unassigned pins |
Routes → Master Sequence | The standing order of each route for every future occurrence |
Billing → Work Orders Review | Check completed on-request work and disposal tickets, mark ready for invoice |
Chat bubble (bottom right) | Ask Oscar or reach Support |
Skip the older Board and Map views; the Advanced versions replace them. Star the Advanced Board so it opens by default.
A typical day
Start of day: check unassigned stops for today and tomorrow.
Through the day: take requests, publish them, and assign every stop to a route.
Watch progress on List view and the Advanced Map; answer driver questions.
Handle changes: reschedule, cancel, move stops between routes, add notes.
End of day: check unassigned stops again, then review completed work orders and disposal tickets.
Before you start: know your services
Every stop comes from a service on a customer account, and the service type decides how you schedule it.
Service type | Use it for | How work orders appear |
Recurring | Weekly, every-other-week, monthly collection | Generated automatically about 10 weeks ahead; routing once assigns every future occurrence |
On-request | Roll-off deliveries, swaps, finals, extra pickups, bulky items, one-time jobs | Created only when you schedule an event; each one must be routed |
Service names should say the action. On an account, an on-request service can show only its name, not its action. If the price book has several services all called "Roll-off Service," you cannot tell the delivery from the swap. Ask your admin to name them with the action and size, for example "20-Yard Roll-off Delivery" or "30-Yard Roll-off Swap." When a name is edited in the price book with Update all related configured services checked, existing accounts pick up the new name too.
Use pricing-zone filters when they exist. When adding a service, the left panel filters (recurrence, business line, measure, pricing zone) are optional. They shrink a long price book to the right options, for example only the services priced for the customer's zone. You can also type in the search box.
Pins matter. Routing and the tablet both use the service location's map pin. If a stop shows up far from everything else, the address was probably not selected from the dropdown. Open the location, correct the address, and pick it from the dropdown so it re-pins.
Workflow 1: Publish an on-request job
A published job does nothing until it is on a route, so publishing is only half the task.
Customers → find the account → Services tab.
Optional: click the service location on the left to show only that location's services.
Click the blue + on the Services bar to add a service. Switch the filter from Recurring to On request.
Search or filter, then select the service (for example a 20-yard delivery) so it highlights.
Confirm the service address at the bottom, set the work order date (default is today; move it if the job won't run today), and set quantity.
Choose how to finish:
Publish and return to account — stays on the account; you then route from the calendar.
Publish now — opens the service so you can route it right away in Map & Routing.
Create draft — saves without scheduling.
Either publish button works. Pick one habit and stick to it.
Repeat jobs on the same container. After the first delivery, the swap or final service stays on the account. For the next swap, click the + next to that existing service, click the date first, then schedule it. You do not add a new service each time.
Workflow 2: Assign every stop to a route
An unassigned stop never reaches a driver's tablet, so assign it before you leave the account. On the service calendar an orange cone (or a "U") marks a day that still needs a route.
Four ways to assign a stop (all reach the same result; use whichever fits the moment):
Where | Steps | Best for |
Account calendar | Scroll to the calendar → click the day with the orange cone → Assign stop → pick a route → enter sequence → save | One-off jobs right after publishing |
Work order row | Click the three dots next to the work order → Assign stop | Same, from the work order list |
Service → Map & Routing | Choose By nearest stop (system suggests a neighbor) or By route → sequence → save | New recurring services, picking a spot near neighbors |
Routes → Advanced Board | Turn on Unassigned stops, then drag a stop onto a route (or onto "assign by nearest stop") | Clearing the day's leftovers in bulk |
Sequence number = the stop's place on that route. If a route already has 3 stops and this one goes last, enter 4. Nearest-stop suggestions are a guide; override them when you know the road better.
Save current day vs. save permanent. Every routing save asks which one (Daily vs. Master route):
Save current day changes only that date's route. Use it for one-time jobs and same-day shuffles.
Save permanent / Publish Master Sequence changes the standing route for every future occurrence. Use it for recurring services and permanent day or route changes.
A save that is grayed out usually means a stop is missing a sequence number.
The unassigned bucket is your safety net. Anything published but not routed lands in Unassigned on the Advanced Board for its date. Check it for today and tomorrow at the start and end of every day.
Workflow 3: Add, move, or cancel events
All schedule changes happen from the service's + button on the account's Services tab.
Add another event (another swap, an extra pickup): click + next to the service → click the date → schedule → then assign the new stop to a route.
Cancel an event ("the container is only half full, skip Tuesday"): click + → click the date → trash can → the event shows Pending deletion → Save.
Move an event: cancel the old date and add the new one, then route it.
Find the right service first. If two services look alike, hover or expand them to check the action and date before deleting. This is why action-named services matter.
Recurring stop not happening one week? Change that work order's status to Canceled rather than leaving it scheduled. A skipped stop is still treated as completed work; a canceled one is not.
Customer moving day for good? Update the service's schedule, then re-route with Save permanent so every future week follows.
Work orders are not created for past dates, so a service started mid-week only shows future days. Use the calendar's week arrows to view the next week when the current week looks partial.
Workflow 4: Manage routes in bulk
When many stops need to move, use the blue Bulk button (top right of the Board or List view) instead of dragging one at a time (Bulk actions). Always confirm the date at the top first; routing views show one day at a time.
Bulk action | When to use it | Watch out for |
Assign / unassign stops | Clear a pile of unassigned stops onto a starting route | Filter first (for example by service type) so only the right stops are selected |
Move between routes | Rebalance two routes on a map: Shift + drag to lasso stops | Stops must already be on a route; assign them to a starting route first |
Change route sequence | Fix stop order one stop at a time on the map | Save permanent to keep it for every week |
Move between recurring days | Shift a group of stops to another weekday, temporarily or permanently | Pick temporary vs. permanent deliberately |
Optimize route | Get a shortest-distance draft order | It doesn't know one-way streets, school hours, right-side-only pickups or dump runs; review before saving |
Moving stops without losing the order: after Move, enter a Starting position (for example 1) and choose Preserve sequence. Leaving it blank or choosing Reset sequence clears the numbers, and the save stays grayed out until every stop has one.
Temporary mode (orange bar on the Board) makes drags apply only to that date. With it off, changes go to the master route.
One driver per route works best. Several drivers can run one route, but each tablet shows every stop on it. If a section is always run by a different driver, make it its own route. Name routes so anyone can read them (for example "Mon Commercial 1"); your company decides the convention.
Route looks out of order? Fix the master in Master Sequence, publish, then resync the daily routes. You can also import a driver's actual sequence from a past day, or restore an earlier version from Activity History (Route out of order). After any change made in another browser tab, refresh before saving.
Workflow 5: Monitor the day
Three views answer three different questions; use the one that fits.
Question | View | What to look at |
Who is on which route, and what's left? | Advanced Board | Route cards with stop details (customer, address, container); unassigned bucket; card fields are customizable |
How far along is each route? | List | Status per route (Not started, In progress, Complete), stop counts; filter count shows total routes |
Where is the truck, and where has it been? | Advanced Map | Stops, unassigned pins, and the Driver path layer |
Reading an in-progress route card. It shows Completed and Remaining miles, an estimated finish time, and percent of stops finished (serviced or skipped). Miles are straight-line between stops and skip the yard trip, so they read low; the finish estimate is optimistic and shows a dash when the truck is stopped (Today's routes).
Driver path (breadcrumbs). Routes → Advanced Map → open the Control panel → toggle Driver path on. Hover a line to see driver, time stamp, and speed; the blinking end is the truck's last reported location. Use the Filters button at the top to show one route. Change the date to review a past day.
Use it to:
Answer "you missed me" calls: confirm whether and when the truck passed the address.
Find a driver's last location after a breakdown or accident.
Spot unassigned stops still sitting on the map.
If the Advanced Map won't load, have the user finish any pending browser update and refresh; then contact Support.
Workflow 6: Tell drivers what they need to know
Put each instruction at the narrowest level that covers it. Too broad and drivers see stale notes every week; too narrow and they miss it (Notes article).
Note type | Applies to | Where to add | Example | Driver sees it? |
Location note | Every service and work order at that address | Services tab → location → three dots → Location notes | Gate code; don't service before 7 AM; use the back lane | Yes, if Show on mobile is on |
Configured service note | Every occurrence of that one service | Service detail → Configured Service Notes + | "Cans are behind the garage"; "Bin has a lock" | Yes, if Show on mobile is on |
Work order note | One job only; drops off after | Work order → notes icon + | "Place in driveway, ASAP"; "Extra box out this week" | Yes, if Show on mobile is on |
Account / Billing notes | Office only | Account or Billing tab | Call history, internal reminders | Never |
A note on a swap service repeats on every swap you schedule from it. If the instruction is for next Tuesday only, put it on that work order.
To check exactly what a driver will see, open the work order and click the Notes icon (top right). Toggle Show on mobile per note there.
Tags flag a location or service for quick scanning (gate code, aggressive dog, low wires, special price). A tag reaches the tablet only if it was created with Mobile checked; account-level tags are office only. Your admin creates tags; you apply them.
Workflow 7: Confirm completed work and disposal tickets
On-request work orders stay out of billing until someone marks them ready, so a regular review keeps the office from facing hundreds at month end. If your company assigns this to dispatch, this is where your job ends and billing's begins.
Billing → Review → Work Orders. Stay on the Not ready tab.
Set the date range to the past (yesterday, or the last week). It defaults forward, where nothing has happened yet.
Hover the icons on the right of each row to find disposal tickets, fees, PO numbers, and notes. Rows with a disposal ticket are highlighted.
Open the ticket and compare it to what the driver reported: disposal site, material, tonnage, included tons, rate.
Fix anything wrong and save, or cancel if it's correct. Check with the driver when numbers don't match.
Select the row's circle → Ready for invoice.
Recurring services are marked ready automatically, so they don't appear here by default. If your company adds disposal tickets to recurring work (compactors, for example), filter to recurring services and check those tickets too.
How often to review is your company's call: daily for busy roll-off operations, weekly or less for low volume. Stop at Ready for invoice; creating and sending invoices belongs to billing.
Workflow 8: Support drivers on the tablet
Drivers use the Hauler Hero Road app, each with their own login. Most "where's my stop?" calls are fixed with a sync (Tablet Training 101).
Recommended settings (tap initials, top left → Settings):
Setting | Recommended | Why |
Follow Me | On, always | Records the order the driver actually ran, which you can import to fix a route |
Autocomplete | On | Completes stops when the truck stops at the pin |
Autocomplete radius | 30–100 ft | Close enough to the pin to count |
Autocomplete timer | 15–25 sec | Gives the driver time to tap the red X first |
Max speed | 3–5 mph | Prevents false completes from GPS drift |
Right-side only | On for side-load; off for rear-load | Matches how the truck services |
Marker clustering | Off | Shows each pin separately on the map |
Common calls and fixes
Driver says | Fix |
"The new stop isn't on my tablet" | Confirm it's assigned to their route on that date, then have them tap Quick Sync (blue) |
"No signal out here" | Before leaving coverage, Full Application Sync (orange); they can complete stops, notes, photos offline |
"Pin is in the wrong spot" | Driver: red X → Adjust Location → move pin → save. Office: correct the location address |
"Stops won't complete" | Check autocomplete settings and speed; complete manually |
"Can't log in" | Verify their email; admin can resend the invite or reset |
"I can't see that route" | Routes assigned to specific drivers are hidden from others; ask your admin to add them |
"Turn-by-turn isn't showing" | Confirm the setting is on, then log out and back in |
Exceptions. The red X records why a stop wasn't serviced (cart not out, blocked, unsafe, access issue), and partial service records which container was missed. Review them when a customer calls about a miss.
End of route. Ask drivers to Finalize and leave unfinished stops unfinished rather than bulk-skipping them, so you can move those stops to the next day. Ask them to give you the work order number first when they call.
Containers and inventory
If your company tracks inventory, the container on a service is what the driver sees and what the yard count relies on. Keep it accurate as jobs happen.
Linking a container: open the service (click its white space) → Details & Pricing → Containers. Remove the placeholder container, click Inventory, and pick the serial number. The list filters to the service's size.
Quantity: one stop can carry several containers. Set the quantity on the service rather than adding duplicate services; the driver sees one stop with each container listed.
Container tags drivers rely on (for example "long-term metal") show on the account and tablet. On the office work order view they may not show, so confirm the container before entering a ticket when a site has several.
After a final: a final pickup does not end the service or return the container. Deactivate the service and move the container back to the yard (or to its next customer), or your inventory will still show it on site.
Swaps: if drivers record swaps on the tablet, the container change follows automatically; if not, update it in the office the same day.
Ask your manager whether your company tracks serialized containers before changing any of these.
Daily checklist and common pitfalls
Start of day
Unassigned stops for today and tomorrow are cleared
Route changes are done before drivers leave the yard
Drivers are logged in, synced, and on the right truck and route
During the day
Every new job is published and assigned to a route
One-time instructions are on the work order, not the service
Drivers are told to Quick Sync after same-day changes
Progress checked on List view and the Advanced Map
End of day
Unfinished stops moved to the next day
Unassigned stops checked again for tomorrow
Completed on-request work and disposal tickets reviewed and marked ready (if assigned to you)
Pitfalls to avoid
Mistake | What happens | Prevent it |
Publishing without routing | Stop sits in Unassigned; driver never sees it | Assign before leaving the account |
Save current day on a recurring change | Next week reverts to the old route | Use Save permanent for standing changes |
Wrong date on the routing view | Changes land on the wrong day | Check the date before every edit |
Typing an address without picking the dropdown | No pin, or a pin far away | Always select from the dropdown |
Generic service names | Wrong service deleted or scheduled | Name services with action and size |
Bulk move without a starting position | Save stays grayed out | Enter 1 and Preserve sequence |
Two browser tabs open | Stale data overwrites a change | Refresh after working in another tab |
Leaving a skipped recurring stop as-is | Treated as completed work | Set the work order to Canceled |
