Verizon Connect Field Service Dispatch and the Reveal route planner: design ceilings and the optimization decision layer

What Verizon Connect does well, taken on its own terms

Verizon Connect is the unified brand built from the Fleetmatics, Telogis and Networkfleet acquisitions and rebranded as Verizon Connect on 6 March 2018. The surface area:

• Reveal core platform. GPS, ELD, vehicle telematics, geofencing, alerts, hours-of-service compliance. The system of record for the vehicle, driver and trip.
• Spotlight. Manager mobile app for iOS and Android. Surface for managers checking on the fleet on the go.
• Reveal Driver and Reveal Field. Driver and field-technician mobile apps integrated with the Reveal platform. Stop status, route review, vehicle assignment.
• Coach. Driver behavior scoring, gamified training, safety-event playback.
• ELD LogBook. Electronic logging device compliance for hours of service.
• Verizon Connect Navigation. Commercial navigation app with truck-legal routing.
• Dashcams and asset tracking. Vehicle cameras for safety and incident review; GPS trackers for non-vehicle assets.
• Reveal route planning. Drag-and-drop planner with cloud optimization assistance for the day’s stops; documented constraints span time windows, vehicle capacity, driver certifications and overnight trips.
• Field Service Dispatch. The FSM module. Third-party reviews describe it as a manager dashboard with a calendar view, drag-and-drop assignment and read receipts when the technician opens the job, designed for small and mid-size service operations.

For telematics-led fleet operations across light commercial, services and distribution, this is exactly the right product. Verizon Connect covers the vehicle, GPS trail, ELD log, driver behavior, dashcam and asset tracker estate end to end. The friction is in a specific decision layer alongside the planning surface, not in the telematics estate itself.

Four patterns where the planning surface reaches its design ceiling

Each pattern has its own dedicated sub-page in this cluster. Here they are in one view:

• Optimizer-driven assignment. The Reveal route planner is described as a drag-and-drop dispatch surface with cloud optimization assistance (RouteCloud) that “analyzes millions of route options.” When the planner is spending the morning hand-balancing jobs across drivers, depots and skills, the decision layer that needs to fill in is the optimization engine: a constraint-based assignment that takes stops, drivers, vehicles, depots, skills, time windows and SLAs as inputs and produces the assignments under an objective. That layer is what eLogii owns.
• Multi-depot rebalancing. The Reveal route planning product page documents time windows, vehicle capacity, driver certifications and overnight trips as supported constraints. Multi-depot is not surfaced. Regional service organizations with three or four depots, contractors with branch networks, and recurring programs across regions need the optimizer to treat all depots as a single problem. The output is one consistent plan across depots, not the sum of per-depot plans.
• Recurring service programs at scale. Recurring or template routes are not a named capability on the Reveal route planning page. At thousands of recurring jobs with SLAs varying by contract, with cadence drift to keep capacity balanced, calendar entries are no longer the same thing as optimization. The optimizer needs to model task and route template groups as constraint inputs, balance recurring against reactive break-fix, and protect SLA-locked stops.
• Reveal Driver fleet-scale limits. Verizon Connect’s help center documents that for fleets over 500 vehicles, Reveal Driver users cannot use auto-suggested vehicle assignment and must search and assign manually. The planner surface is built around fleet shapes below that threshold. What changes when a dedicated optimization layer slots in: the fleet shape stops constraining the routing decision, and driver-vehicle assignment becomes part of the constraint model rather than a manual lookup.

Each pattern is addressable on its own. Most operations start with whichever is leaking the most.

How to tell if your operation has hit one of them

The diagnostic signals are operational, not headcount-based. Some patterns from operations that have moved to a combined Verizon Connect + eLogii stack:

• The planner has become the optimizer. The planner spends the morning hand-balancing rather than reviewing. The bus-factor of the planning operation is one or two people, even with the Reveal planner’s cloud assistance running.
• SLA misses are concentrated in specific programs or depots. The recurring service book or the regional book is leaking against SLAs; the rest of the operation is fine.
• Cross-depot capacity drift. One depot runs hot, another runs underused, drive time creeps up. No one has time to spot it in real time.
• Recurring programs run as separate calendars. Quarterly preventive, monthly inspection cadences exist as their own calendar entries reconciled by hand against the day’s reactive book.
• Fleet has grown past 500 vehicles. Reveal Driver is asking drivers to search and assign vehicles manually instead of auto-suggesting; the surface is asking the operation to do work the optimization layer should be doing.
• Planning time grows faster than the operation. Doubling the driver count more than doubles the planner load.
• Cloud optimization assistance runs on a narrow scope. The Reveal planner runs against today’s shape because the constraint model needed to span multi-depot, multi-day, recurring programs is not the shape the planner is built around.

Each of these is a signal that the optimization decision layer alongside the Reveal route planner is the bottleneck. The right answer is to add the engine, not to replace the telematics estate.

At a glance: an 80-driver facilities service organization

A facilities service organization running HVAC, electrical and compliance work across a regional book. Eighty drivers in the field, four depots, two planners. Roughly 50% recurring compliance visits against SLA terms, the rest reactive break-fix coming in through phones, email and a customer portal. All four patterns hit at once.

Each pattern shows up in a specific place. The optimizer-driven assignment pattern shows up in the planning room each morning: two planners hand-balancing the daily mix instead of reviewing an optimized plan, with the Reveal route planner’s cloud assistance running on today’s shape because the full problem is too brittle to model. The multi-depot rebalancing pattern shows up when a driver at depot 3 is off sick and the day’s reactive work has to be redistributed to depots 1, 2 and 4 by hand. The recurring-program optimization pattern shows up as creeping SLA misses on the quarterly preventive book; calendar entries existed correctly, route-level routing wasn’t the bottleneck, but the interaction between contract preventive and reactive break-fix across the same drivers was. The fleet-scale pattern shows up as the operation grows past the 500-vehicle Reveal Driver threshold and drivers start spending time searching for their assigned vehicle in the app each morning. Each pattern is addressable on its own. Operations at this shape most often start with whichever is leaking the most visible cost, then expand on the same integration.

What eLogii adds, in one place

The constraint-based optimization decision layer that runs alongside the Reveal route planner:

• Two engines. Default engine for high-throughput daily planning (100 tasks in under 10 seconds). Advanced engine for multi-depot, multi-day, long-haul and constraint-heavy operations.
• Six configurable modes. Three assignment modes (Optimize Everything; Add to Routes, Keep Existing Assignments; Add to Routes, Keep Existing Assignments and ETAs). Three load-balancing modes (Most Efficient Routes; Balance the Minimum Number of Routes; Use All Vehicles / Finish as Soon as Possible).
• Multi-day, multi-depot, multi-driver in one run. Single optimization across the routing horizons the planning surface is not designed to solve.
• Task and route template groups. Weekly, monthly, quarterly and bespoke cadences modeled directly as constraint inputs.
• Rule-based re-optimization. Operator-visible rules; live re-optimize while protecting locked SLAs and customer-confirmed slots.
• Slot booking co-pilot. Route-aware availability that returns only slots that fit the current optimized plan.
• REST-callable. All six modes plus slot availability plus optimization triggers exposed as REST endpoints. Seven webhook events including live driver GPS and Route ETAs Update.

How the integration sits with Verizon Connect

Verizon Connect stays the system of record for GPS, ELD, driver behavior and dashcam record. The operational system (FSM or ERP) stays the system of record for the work record. The connector between eLogii and the stack is custom-built; there is no published eLogii to Verizon Connect integration on either side. Verizon Connect documents a telematics API through the Reveal developer portal.

1. Read from the operational source. eLogii reads stops, drivers, vehicles, depots and skills from the FSM, ERP or Verizon Connect directly via the Reveal API.
2. Optimize in eLogii. The run produces assignments and routes under the chosen objective, respecting SLAs and customer-confirmed slots.
3. Write back to the operational system. Optimized routes, ETAs and assignments are written back to the FSM / ERP. The route dispatches into the eLogii driver app; Verizon Connect continues to capture the GPS, ELD, behavior and dashcam stream on top.
4. Driver experience unchanged. The driver opens the same mobile app. The routing they follow is the one eLogii planned.

Most teams complete the connector build in 3 to 5 weeks. The most common first wave is whichever of the four patterns is leaking the most.

Frequently asked questions

Where does the Verizon Connect planning surface reach its design ceiling?

Four patterns. First, optimizer-driven assignment: when the planner needs to decide assignments under hundreds of competing constraints, not just drag jobs on the Reveal calendar. Second, multi-depot rebalancing: when work needs to flow between three or four depots based on capacity, skills and SLA (multi-depot is not surfaced as a documented constraint on the Reveal route planning page). Third, recurring service programs at scale: thousands of recurring jobs with interacting SLAs and cadences (recurring routes are not surfaced as a named capability on the Reveal page). Fourth, fleet-scale beyond the documented Reveal Driver 500-vehicle threshold, where drivers must search and assign vehicles manually. Each of these is a different facet of the same problem: the optimization decision layer alongside the Reveal planner and Field Service Dispatch.

Does this mean Verizon Connect is the wrong tool?

No. Verizon Connect is the telematics platform for the vehicle, GPS, ELD, driver behavior, dashcam and asset tracker stack. The Reveal route planner and Field Service Dispatch are useful surfaces for small and mid-size fleet operations on top of that telematics estate. For a wide band of fleet and field-service operations, this is exactly the right tool. eLogii is not a telematics platform. It is the constraint-based routing and optimization decision layer for operations where the assignment problem is the bottleneck.

How do I know if my operation has outgrown the Reveal route planner?

Diagnostic signals: the planner spends the morning hand-balancing rather than reviewing; SLA misses are concentrated in specific recurring programs or depots; the bus-factor of the planning operation is one or two people; cross-depot work feels like it should be balanced more but no one has time to look; recurring service programs run as separate calendars reconciled by hand; the fleet has grown past 500 vehicles and the Reveal Driver app is asking drivers to search and assign manually. Each is a sign that the assignment problem has grown past what the Reveal route planner (with or without Field Service Dispatch) is designed to solve. Adding eLogii is the answer to that specific layer; Verizon Connect keeps owning the GPS, ELD, driver behavior and dashcam record.

How does the integration work?

Custom integration against the Reveal API and the operational system of record (FSM or ERP). eLogii reads stops, drivers, vehicles, depots and skills from the operational systems; runs the optimization across the chosen pattern (multi-depot, recurring program, fleet-scale, all of them); writes optimized routes and ETAs back. The driver opens Reveal Driver or Verizon Connect Navigation in the cab; Verizon Connect captures the in-cab GPS, ELD, behavior and dashcam stream. Typical connector build: 3 to 5 weeks.

Can I start with just one of these patterns?

Yes, and that is how most teams start. The most common first wave is whichever pattern is leaking the most: multi-depot rebalancing for regional service organizations, recurring program optimization for compliance and preventive books, fleet-scale optimization for operations past the 500-vehicle Reveal Driver threshold, optimizer-driven assignment for any operation where the planner is the bottleneck. Once one pattern is live and the lift is visible, the others follow on the same integration.