Skip to main content
Open Products → Dispatching. Dispatching appears when it is enabled for the team and your role has access to it.

​
Board

The Board is the live operating view for technician schedules and unassigned jobs. Use it to:
  • Review the selected day’s technicians, jobs, arrival windows, and unassigned work
  • Inspect eligible technicians and assignment reasoning when those details are available
  • Preview auto-assignment results before accepting them
  • Assign or unassign jobs and review the resulting route
  • Publish an approved board change
Refresh the CRM data before making a time-sensitive decision, and review any conflict or eligibility warning rather than forcing an assignment around it.
A published dispatching change can affect live technician schedules and customer commitments. Confirm the date, technician, job, arrival window, and CRM result before publishing.

​
Assignment setup

Available tabs depend on the team’s rollout:
  • Tiered Groups organizes technicians with related skills into ranked groups.
  • Batting Order controls the order in which eligible technicians are considered when that feature is enabled.
  • Technician Settings manages customer-editable technician constraints and options, such as supported on-call, pairing, ride-along, or alternation settings.
  • Technician Performance reviews the performance data used by supported dispatching decisions.
  • Priority settings lets an authorized team admin configure job-type, tag, and scoring priorities.
Make structural changes outside active dispatching hours when possible. After changing a group, technician setting, batting order, or priority, preview a representative assignment on the Board.

​
ETA messages

Use ETA to configure automated customer SMS for supported dispatching events.
  1. Keep the master Enabled switch off while drafting.
  2. Add the required message types and triggers.
  3. Apply only the intended job-type or tag filters.
  4. Review the message copy and any overlap warning.
  5. Save, run an approved test, and then enable delivery.
Some teams also see dispatching message settings inside Outbound → Customer Notifications. Treat the dashboard’s overlap warning as authoritative and avoid enabling two configurations that send the same customer event. Customer documentation intentionally excludes Avoca’s internal dispatching administration and diagnostic controls. If setup prerequisites are missing, contact Avoca rather than copying another team’s hidden settings.