The dispatch board has org-wide settings that shape how Run a Call assigns and warns. Most live on the dispatch settings page; some on individual tech profiles.

Org-wide dispatch settings

Where: typically reached through the dispatch board (a gear icon in the corner) or settings.

Common knobs:

SettingWhat it controls
Customer favorite tech modeStrict (require it), Prefer (try it first), or Off.
Member favorite tech modeSame options, applied to membership visits specifically.
Require skills for dispatchWhen on, the system blocks an assignment if the tech doesn't have the required skill (instead of just warning).
Scoring weightsHow much weight to give to drive time vs continuity vs other factors when Runny ranks plans.

These settings apply to all dispatchers and to Runny. Change them once and the whole shop's dispatch math shifts.

Per-tech settings

On a tech's profile:

SettingWhat it does
Service areasRestrict which zip/city codes they cover.
SkillsCertifications and capabilities (read from the Skills & Certifications settings page).
Default shiftStart/end times.

The dispatch board reads these every time you assign or move a job.

What's not configurable (yet)

  • The columns/rows shown on the board (always tech × time).
  • The block size on the time axis.
  • Adding non-job blocks (lunch, meeting) is not supported via the board today; if you need time off blocked, schedule it as a no-tech job or talk to support.
  • Re-ordering the tech rows on the board (the current order comes from the team list).

Useful patterns

  • Two-tier service areas. Put your primary zip codes in tech service areas, then create looser org-wide service areas for the AI Receptionist to gate booking. This way Runny can spread within the loose zone but the AI can decline truly out-of-area bookings.
  • Skill-blocking only on high-stakes work. Turn Require skills for dispatch on for Installation jobs, leave it off for Service. The settings page supports per-job-type overrides.