Overview
Auto Mode is the state where Dispatch Pro takes the wheel — assigning, reassigning, and rescheduling jobs every 10 minutes during business hours without manual review. Most shops don't flip to Auto Mode all at once. They move into it deliberately, watch how it behaves against their real bookings, and adjust the settings underneath it as patterns emerge.
This guide is for shops that already have Dispatch Pro live in ServiceTitan and are ready to expand their use of Auto Mode, stabilize it, and tune it over time. It covers three things in one place:
When and how to enable Auto Mode — the readiness signals, the per-day mode controls, and the principles for moving from Assist Mode into Auto Mode.
What to monitor during the transition — the signals on the Dispatch Board, in the Dispatch Pro Console, and in the supporting reports that tell you whether Auto Mode is working as intended.
How to adjust settings based on performance — using the alert-to-setting framework so changes to Routing, Prioritization, Technician Ranking, and other settings respond to evidence, not hunches.
In ServiceTitan, Auto Mode doesn't run in isolation. Bookings reach the Dispatch Board through Contact Center and Scheduling. Tags applied at intake — including the Voice Agent tag the Contact Center AI Voice Agent applies to after-hours bookings — feed your Prioritization rules. Technicians receive their assignments through the ServiceTitan Field Mobile App and execute work with Atlas and Field Pro. Fleet telematics validate the technician location data that Dispatch uses for routing decisions. Pricebook Pro estimate and ticket data flows back into the Technician Ranking that decides who gets the next high-value lead. Auto Mode works because all of that data lines up — and breaks down predictably when any one part doesn't.
Who uses this feature
Administrators and office managers expanding Auto Mode after go-live
Operations managers reviewing dispatch outcomes and tuning settings
Dispatchers who need context on what to watch when Auto Mode is on
Primarily for Residential Service and Replacement business types
Things to know
In Auto Mode, the Dispatch Board is optimized automatically every 10 minutes during business hours and every hour outside business hours.
Auto Mode applies per day. You set the Running Mode (Assist or Auto) and Solving Mode (Light or Full) for today and the next three days. You don't have to use Auto Mode for all four days.
Auto Mode does not eliminate the dispatcher role. As the dispatcher who monitors and guides Dispatch Pro, the final dispatching decision always rests in your hands.
Dispatch Pro is as effective as the data it has access to. Expect an adjustment period while you manage and revise your data and settings. The accuracy of Dispatch Pro increases with the amount of historical data in ServiceTitan.
Dispatch Pro must already be live in your account. If you're not yet live, complete the Dispatch Pro setup check first and resolve any Off-icon warnings on the Dispatch Board.
Dispatch Pro only works with managed technicians. Validate technician home addresses and assign technicians to zones and skills before relying on Auto Mode.
You need the Access settings and Edit Dispatch Pro settings permissions to change any of the settings referenced in this guide. Contact your account administrator.
Step 1: When and how to enable Auto Mode
How Auto Mode fits with Assist Mode
Auto Mode and Assist Mode are not a one-time choice. They're a per-day setting in Setting 7.1 (Adjust Dispatch Pro Modes Settings) — meaning for today and the next three days, you decide independently whether each day runs in Assist or Auto.
Assist Mode — Dispatchers generate, review, and approve each Dispatch Pro suggestion before it goes live. Use Assist Mode when you want transparency and control over individual changes.
Auto Mode — Dispatch Pro automatically assigns the most optimal technician to Dispatch-Pro-enabled jobs, eliminating the need for manual review. Dispatchers still oversee the board.
Solving Mode pairs with Running Mode and controls which jobs Dispatch Pro touches each day:
Full Mode — Dispatch Pro optimizes all Dispatch-Pro-enabled jobs, including reassigning already-assigned jobs when needed.
Light Mode — Dispatch Pro only assigns unassigned Dispatch-Pro-enabled jobs. Existing assignments remain unchanged.
Together, these four levers give you a graduated way to expand automation: more Auto, more Full, on more days, as your confidence grows.
Readiness signals — when your data and settings are ready for Auto Mode
Auto Mode performs as well as the data feeding it. Confirm the items below before you turn it on for a given day or business unit. Each one corresponds to a setting area in the Dispatch Pro Settings Reference Guide in ServiceTitan Max.
Technician data is clean — Home addresses are validated, technicians are assigned to zones (Technician Setting 4.1), and skills are assigned to both technicians and job types (Setting 4.1 and Prioritization Setting 3.1). If a technician's home address isn't validated and their start/end location is not specified, Dispatch Pro falls back to the business unit address, which can produce routing decisions you didn't expect. Fleet is helpful here: if you're using Fleet telematics, recent GPS data gives Dispatch Pro a more reliable picture of where each technician actually starts and ends the day.
Job types are configured — Dispatch Pro Status is on for the job types you want automated (Prioritization Setting 3.1), and expected durations are set. Skills are linked to job types (run Generate Skills in Prioritization Setting 3.1 to apply ServiceTitan's recommendations).
Intake quality is high — Customer addresses entered through Contact Center or Scheduling have coordinates. Recurring No Coordinates alerts in your Job Tray are a sign that intake — not Dispatch Pro — is the problem to fix first.
Arrival windows are realistic — Scheduling arrival windows or business hours are wide enough that Dispatch has room to optimize. Very narrow windows produce No Availability and Arriving Too Late alerts that Auto Mode can't solve on its own.
Tags are in use — CSRs in Contact Center and the AI Voice Agent are applying tags consistently, and you've configured Prioritization Setting 3.3 (tag-based priority modifiers) and Technician Setting 4.2 (skill-to-tag associations) to use them. Without tags, Auto Mode can't elevate the right jobs or route to the right specialists.
Priority levels are deliberate, not blanket — Setting 3.2 has only the 5–10 most important job types ranked. Stacking too many job types at top priority creates Urgent Job Conflict alerts as soon as Auto Mode tries to fit them all in early arrival windows. Ensure job types are not urgent by default.
Tip: ServiceTitan recommends reviewing and adjusting Dispatch Pro settings during shoulder slow seasons to prepare for the busy season. The same applies to expanding Auto Mode — moving deeper into automation during a slow period gives you time to spot issues before they compound under volume.
Principles for moving from Assist Mode into Auto Mode
Move forward by days, not all at once. The per-day mode setting exists so you can extend automation incrementally. A common pattern is to leave Day 1 (today) in Assist Mode while running Days 2–4 in Auto Mode — protecting today's finalized schedule while letting Dispatch Pro plan the future hands-off.
Use Light Mode to protect a finalized schedule. If today's board is already dispatched and you don't want reassignments mid-day, Light Mode on today + Full Mode on future days lets Auto Mode plan ahead without disturbing what's already in motion.
Expand by job type when behavior is uneven within a BU. Setting 3.1 lets you enable or disable Dispatch Pro per job type. If recurring service calls run cleanly in Auto Mode but estimates produce too many exceptions, leave estimates manually dispatched and let Dispatch Pro handle the service work.
Pull back when the evidence says so. A spike in unassigned jobs, an unexpected drop in technician utilization, or a sustained increase in Max Drive Time or No Matching Technicians alerts is a signal to switch the affected day or BU back to Assist Mode while you investigate. Switching modes mid-day is supported — dispatchers receive a real-time alert on the Dispatch Board notifying them of the change.
How to set Running Mode and Solving Mode
Go to the navigation bar and click Settings.
In the side panel, go to Dispatch Pro > Settings.
Click the Dispatch Pro Modes tab.
In Setting 7.1, select the Running Mode (Assist or Auto) and Solving Mode (Light or Full) for each of the next four days.
Click Save.
Note: When you change the Running Mode, dispatchers on the Dispatch Board receive a real-time alert. Make sure your dispatch team understands the difference between Auto Mode and Assist Mode before you switch — Dispatch Pro behaves visibly differently on the board, and unprepared dispatchers may not know whether to intervene.
Turning Dispatch Pro off entirely
If you need to take Dispatch Pro fully offline — not just switch a day to Assist Mode — go to Settings > Dispatch Pro > Settings, click the Dispatch Pro dropdown, and select Turn Off Dispatch Pro. To turn it back on, repeat and select Turn On Dispatch Pro.
Step 2: What to monitor during the transition
When you expand Auto Mode, the right question isn't "is Dispatch Pro working?" — it's "is Dispatch Pro making decisions I would have made, or decisions I should adjust the settings to prevent?" Three surfaces give you that picture: the Dispatch Board, the Dispatch Pro Console, and the supporting reports.
Monitoring checklist — first weeks in expanded Auto Mode
Use this checklist daily while you're expanding Auto Mode, then shift to weekly once behavior stabilizes.
On the Dispatch Board
Confirm Dispatch Pro is live. A Check icon at the top of the Dispatch Board means Dispatch Pro is running every 10 minutes. An Off icon means setup-check warnings need to be addressed before Auto Mode can do anything.
Scan for lightning vs. lock icons on job appointments. A lightning icon means Dispatch Pro last touched that job. A lock icon means it was manually changed or auto-locked by Locking Jobs Settings. A board with mostly lock icons means dispatchers are overriding Auto Mode constantly — which is a signal to investigate why.
Check for the technician warning icon. A warning icon on a technician profile means the starting location address isn't validated. Flag this to the administrator so Auto Mode can route accurately. Fleet Pro GPS data can help confirm whether the validated address matches where the technician actually starts their day.
Hover over appointment bubbles. Predicted revenue (calculated by Titan Intelligence) and predicted drive time should look reasonable. Drive times near your maximum cap on multiple appointments is a sign that Setting 1.2 (max drive time) or Setting 1.3 (zone-specific overrides) need tuning.
Hover over technician names. Projected revenue for the day, current value collected, and the last time Dispatch Pro ran show whether the day is shaping up as Dispatch Pro predicted.
In the Job Tray (Unassigned and Alerts tabs)
Watch unassigned job volume. Jobs can move between assigned and unassigned as Dispatch Pro runs. Every unassignment comes with an alert explaining why. A small steady volume is normal; a sustained increase after expanding Auto Mode is a signal.
Read alert frequency, not just alert presence. A one-off Max Drive Time alert is an exception the dispatcher handles. The same alert recurring daily in the same zone is a setting issue (see Step 3).
Track which alerts dominate. The mix tells you what to investigate first. Persistent No Matching Technicians points to skills/zone setup. Persistent No Coordinates points to intake quality at the Contact Center / Scheduling entry point. Persistent Low Value Job points to the revenue/routing balance in Setting 1.1.
In Dispatch Pro Console
Dispatch Pro Console supplements the Dispatch Board with actionable tasks for all jobs and all technicians — not just Dispatch-Pro-enabled ones.
Workstream task volume. If a dispatcher's workstream suddenly fills up with Urgent tasks after you expand Auto Mode, the underlying rules may be firing on conditions Auto Mode introduced. Review which rules are triggering.
Voice Agent Booking Review tasks. If you've configured a console rule that surfaces Contact Center Voice Agent bookings (Job tag = Voice Agent + appointment date = Today), watch how many appear daily — this tells you both your after-hours booking volume and whether Auto Mode is handling those bookings as you'd expect.
Technician Late and Job Running Late tasks. Spikes here can mean Auto Mode is packing schedules too tightly or that drive-time settings need adjustment.
In the supporting reports
The dispatch decisions Auto Mode makes feed downstream reporting. Two reports are particularly useful during a transition:
Dispatch Pro Technician Performance report — Tracks how Dispatch Pro is ranking technicians based on conversion rate and average ticket. After expanding Auto Mode, check whether high-ranked technicians are receiving the leads you'd expect. If they're not, the issue is usually in Technician Ranking Setting 5.1 (short-term vs. long-term weighting) or 5.2 (Leads Created vs. Leads Sold). Managers also use this data to plan ride-alongs and Pricebook training inside Field — closing the loop between dispatch decisions and field execution.
Dispatch Pro Utilization report — Tracks how dispatchers are utilizing Dispatch Pro. High manual-override rates after expanding Auto Mode mean dispatchers are countering its decisions, which points to either a settings issue or a training gap.
What to watch during transition
Job-level monitoring
Each job record carries two Dispatch Pro toggles that change what Auto Mode is allowed to do with it:
Dispatch Pro toggle — On by default for job types that have Dispatch Pro enabled. Turning it off for a specific job removes that job from Auto Mode but doesn't unassign the technician or modify the job in any other way.
Technician-specific Job toggle — Off by default. Turning it on tells Dispatch Pro not to unassign or reassign the job. If turning it on creates a double-booking, Dispatch Pro shifts the start time within the arrival window to try to avoid overlap. If a manual assignment collides with a Dispatch Pro assignment at the same time, the manual job is kept and the Dispatch Pro job is removed (and the Dispatch Pro toggle is disabled on the record).
What to monitor: Track how often dispatchers are turning either toggle off in the first few weeks of expanded Auto Mode. A small volume is normal — those are the legitimate exceptions Auto Mode can't handle (multi-tech jobs, customer-requested technician requests, etc.). A high volume means dispatchers are losing confidence in Auto Mode's decisions, which is itself a signal to investigate the underlying settings.
For full details on the toggles and their interactions, see Manage jobs with Dispatch Pro Auto Mode.
Technician-level monitoring
Dispatch Pro lets you pause Auto Mode for a single technician without taking it offline for the whole team. If a technician calls in sick or is otherwise unavailable, click their name in the Dispatch Board side menu and select Pause Dispatch Pro, then manually unassign their remaining appointments. When they're available again, select Resume Dispatch Pro.
Pausing doesn't unassign jobs already on the technician's schedule — it only stops Dispatch Pro from making further adjustments. If the technician can't finish their commitments, unassign their remaining appointments manually after pausing.
What to monitor: Hover over each technician's name to see Current Value, Projected Value, and drive time between jobs. During an Auto Mode expansion, watch for technicians whose projected value drops significantly compared to their pre-transition baseline — that's often a signal that ranking or zone settings aren't matching them with the jobs they convert best.
For full details on pausing, resuming, and viewing technician performance, see Manage technicians with Dispatch Pro Auto Mode.
Step 3: How to adjust settings based on performance
When you expand Auto Mode, your alert mix shifts. Some alerts go down because Dispatch Pro is now resolving them automatically. Others go up because Auto Mode is making decisions Assist Mode used to filter out. Reading that shift — and knowing when to tune a setting vs. when to pull back to Assist Mode — is the part of adjustment that's specific to an Auto Mode transition.
For the general framework of how to read alerts as setting signals, the alert-to-setting map, and the rules of thumb for adjusting Routing, Prioritization, Technician Ranking, Business Units, and Locking Jobs settings, see the Dispatch Pro Alert Management and Settings Optimization Guide in ServiceTitan Max. This section covers only what's different when the adjustment is happening because of an Auto Mode expansion.
Reading the alert-mix shift after expanding Auto Mode
The first few business days after you expand Auto Mode will look noisier than usual. That's expected — Dispatch Pro is exercising decisions the dispatcher used to make manually, and every decision that doesn't fit cleanly surfaces as an alert. What matters is the shape of the shift, not the total volume.
Alerts that should go down. Unable to Assign and Start date outside arrival window typically decrease in Auto Mode, because Dispatch Pro is now reassigning and rebalancing rather than waiting for a dispatcher to pick things up. If they don't, intake quality (Contact Center / Scheduling ) is likely the bottleneck, not Auto Mode.
Alerts that often go up — and what each one means.
Max Drive Time rising in a specific zone usually means Auto Mode is reaching further than your max-drive-time setting allows. This is a Setting 1.2 or 1.3 conversation, not a reason to switch the zone back to Assist Mode.
No Matching Technicians rising on specific job types usually means the skills attached to those job types don't match the skills on your technicians. Run Generate Skills in Prioritization Setting 3.1 before assuming Auto Mode is the problem.
Low Value Job rising means Auto Mode is now seeing job-to-tech matches the dispatcher previously avoided. Decide whether your revenue/routing balance (Setting 1.1) needs adjustment, or whether those jobs need a higher priority level in Setting 3.2.
Urgent Job Conflict rising means too many job types are stacked at top priority, and Auto Mode can't fit them all in early arrival windows. Setting 3.2 needs pruning.
When to tune a setting vs. when to pull back to Assist Mode
Not every Auto Mode performance issue should be solved by changing a setting. Sometimes the right move is to switch the affected day, business unit, or job type back to Assist Mode while you investigate.
Tune a setting when the alert pattern is concentrated (one zone, one BU, one job type) and the setting that controls it is obvious from the alert-to-setting map. A spike in Max Drive Time in one zone is a Setting 1.3 fix, not a reason to pull back.
Pull back to Assist Mode when the issue is broad (many zones, many job types, no clear pattern), when dispatcher manual-override rates spike across the board, or when you don't yet have enough data to identify a single setting to change. Switch the affected day back to Assist Mode, let dispatchers approve decisions for a few days while the pattern clarifies, then re-expand.
Pull back at the BU or job-type level, not the account level, when possible. Setting 6.1 lets you switch one BU's behavior without affecting the rest of the shop. Setting 3.1 lets you disable Dispatch Pro for a single problem job type while leaving everything else automated. These targeted pull-backs preserve the automation gains in the rest of the business.
Switching modes mid-day is supported — dispatchers on the Dispatch Board receive a real-time alert notifying them of the change. Communicate the switch in advance so the team isn't surprised.
Tune Console Rules to match the new normal
Dispatch Pro Console rules generate dispatcher tasks based on conditions you define. When you expand Auto Mode, the volume and mix of those tasks shifts — and rules that worked in Assist Mode may now over-fire or under-fire.
Tighten rules that fire too often. If a rule like Dispatch Pro Unassigned Today Jobs fires hundreds of times daily after expanding Auto Mode, add conditions to scope it down — for example, limiting it to specific business units or job types where unassignment actually requires dispatcher attention.
Add rules to surface Auto Mode edge cases. Create a rule with conditions Job tag equals Voice Agent AND Job appointment date equals Today to surface every Contact Center Voice Agent booking from the last 24 hours for dispatcher review. This lets a human get the final say on AI-booked emergency jobs without slowing down after-hours bookings.
Match priority colors to your team's actual urgency model. Rename and recolor the four preconfigured priority levels (Urgent, High, Medium, Low) so dispatchers can scan the console at a glance without misreading what's truly urgent under Auto Mode.
Use the supporting reports and Supervisor Console as Auto Mode scorecards
The dispatch decisions Auto Mode makes feed downstream reporting and the Supervisor Console dashboard. After expanding Auto Mode, these surfaces become your scorecards for whether the transition is working — not just monitoring tools (covered in Step 2), but the evidence you use to decide what to tune next.
Supervisor Console — A customizable dashboard accessed from Dispatch > Supervisor Console or the Dispatch Pro dropdown on the Dispatch Board. Create workspaces filtered to the specific BU, zone, or technicians you expanded Auto Mode for, so the metrics reflect only the area you changed. The most useful Auto Mode widgets are the Automation Rate scorecard (confirms the expansion is taking effect), Assist Acceptance Rate scorecard (a leading indicator of dispatcher trust before you expand further), and the Dispatch Pro Utilization Impact and Dispatch Pro Revenue Impact donut charts.
Dispatch Pro Technician Performance report — If high-ranked technicians aren't receiving the leads you'd expect after the expansion, the issue is usually in Technician Ranking Setting 5.1 (short-term vs. long-term weighting) or 5.2 (Leads Created vs. Leads Sold). Managers also use this data to plan ride-alongs and Pricebook training inside Field Pro — closing the loop between dispatch decisions and field execution improvements.
Dispatch Pro Utilization report — Sustained high manual-override rates after expanding Auto Mode mean dispatchers are countering its decisions. That's either a settings issue (the alert-to-setting framework applies) or a training gap (dispatchers don't trust the new behavior yet). The report tells you which one.
How this fits the broader ServiceTitan Max workflow
Auto Mode doesn't exist in isolation — it sits in the middle of a connected workflow that starts at customer demand and ends at the technician's mobile app. Understanding where each product hands off to Dispatch Pro is what makes the alert-to-setting framework above work.
A homeowner books a job — either through Scheduling online self-scheduling or through Contact Center (CSR or AI Voice Agent). Tags applied at booking — including the Voice Agent tag for AI-booked jobs — flow into the job record.
The job lands on the Dispatch Board with Adaptive Capacity respecting your arrival-window rules.
Dispatch Pro picks it up on the next run (every 10 minutes during business hours). Prioritization Settings 3.2 and 3.3 boost the job's priority based on job type and tags. Routing Setting 1.5 narrows the candidate technician pool by zone or business unit. Technician Setting 4.2 filters further by skill-to-tag associations.
Technician Ranking scores the remaining candidates using conversion rate, average ticket, and short-term vs. long-term performance — fed by completed job and Pricebook estimate data.
In Auto Mode, the assignment is locked in. In Assist Mode, the dispatcher reviews and approves.
The ServiceTitan Field Mobile App shows the technician their next job. Atlas and Field tools support diagnostics and customer-facing presentation in the field. Fleet tracks the vehicle to the address and feeds telematics back. Customer Notifications sends the ETA.
The completed job's outcome — sold, not sold, ticket size — feeds back into Technician Ranking, sharpening the next dispatch decision.
Every setting referenced in Step 3 is a lever in that chain. Changing one — like flipping Setting 5.2 from Leads Sold to Leads Created — changes which technician sees the next high-value lead, which changes the customer experience, the technician's commission, and ultimately the data Dispatch Pro learns from. That feedback loop is why expanding Auto Mode is a multi-week process of monitoring and tuning, not a one-time switch.
Best practices for managing Auto Mode
Expand Auto Mode by day, by BU, or by job type — not all at once. The per-day, per-BU, and per-job-type controls exist so you can isolate where automation is working and where it isn't.
Read alerts as setting signals, not just exceptions. Every alert points back to a setting area. Patterns in the alert mix are the cheapest signal you have for what to tune next.
Use the Dispatch Pro Utilization and Technician Performance reports as your scorecards. They show whether expanded Auto Mode is producing the dispatching and revenue outcomes you expected.
Keep dispatchers in the loop on mode changes. A real-time alert appears on the Dispatch Board when Running Mode changes, but proactive communication beats reactive surprise.
Resist the urge to stack changes. One setting change per investigation cycle is the only way to attribute results to causes.
Plan major tuning during shoulder seasons. Busy season is for executing, not for experimenting with new Dispatch Pro settings.
Use Console rules to surface what Auto Mode can't decide. AI-booked Voice Agent jobs, technician-specific requests, and recurring exception patterns are all good candidates for dedicated console rules.