Dispatch
Dispatch troubleshooting
The five things that most often go wrong, and what each refusal actually means.
Last updated
Troubleshooting#
"Dispatch" is missing from the sidebar. Check the plan first, then the role. Dispatch is a plan feature: installing it puts a Dispatch toggle in your plan editor under Add-ons, and the row is hidden for every sub-account whose plan does not have it ticked. A plan with every feature ticked shows Dispatch straight away, but a plan you have tailored stores an explicit list, and a list saved before you bought the add-on cannot contain Dispatch. Tick it on each plan that should have it, save, and reload. If the plan is right, check the role holds the Technicians permission. Also check you are in a sub-account rather than the agency administration view.
The plan toggle hides the sidebar row only. Who can open a dispatch page is decided by the role.
A technician cannot finish a job. The refusal names what is missing. Two switches on the dispatch Settings page can gate a finish: required worklist items, and a photo on the visit. Named photo categories are not a third switch - they narrow what the photo requirement asks for, so they only apply while the photo switch is on.
Photos will not upload. The role needs the CRM's Files permission.
No payment or signing buttons on the job page. For an office user those follow the CRM's Invoices permission. For a technician, turn on On-site billing instead, and check all three conditions above are true.
Customers are not receiving anything. Nothing is sent until the Customer Experience Settings card is turned on. If you chose Text, the CRM needs an SMS connection under Settings, Integrations. Without one the message appears in the customer's conversation thread and is never delivered, so the thread is not proof of sending.