eLogii + Verizon Connect: When to Add eLogii to Verizon

Where each platform leads

Verizon Connect and eLogii do different jobs in the same field-service and distribution stack. Verizon Connect is the telematics platform: the system of record for vehicle GPS, ELD logs, driver behavior, dashcam footage and asset trackers, with a route planning module and Field Service Dispatch sitting on top of the same hardware estate. eLogii is the routing engine for operations where the optimizer needs to do the heavy lifting across multi-day, multi-depot and constraint-heavy plans, and where the planner needs the engine to decide assignments rather than steer them in a drag-and-drop calendar.

The combined deployment pattern: Verizon Connect stays the system of record for the GPS trail, ELD log, driver behavior data, dashcam record and asset tracker estate. eLogii reads stops, vehicles, drivers and depots from the operational systems, runs the optimization across the routing horizons the Reveal route planner and Field Service Dispatch are not designed to lead on, and writes optimized routes and ETAs back. The driver opens Reveal Driver or Verizon Connect Navigation in the cab; the route they take is the one eLogii planned. Verizon Connect keeps the telematics record, hardware estate and compliance log it owns end to end; eLogii owns the optimization decision layer.

What eLogii adds on top of Verizon Connect

Verizon Connect is the telematics platform. eLogii is the routing engine for the optimization-driven side of the problem. The table below isolates where each side leads.

Sources: Verizon Connect route planning, Verizon Connect Reveal apps, Tech.co Field Service Dispatch review; eLogii optimization engines. Verified June 2026.

API surface and developer experience

Sources: eLogii API documentation; Verizon Connect API integration page. Verified June 2026.

Scale, security and commercial

Sources: Verizon Connect route planning, Verizon Connect API integration, Geotab press release: international acquisition, Tech.co Reveal review, Tech.co Field Service Dispatch review, Spytec pricing teardown. Verified June 2026.

Route optimization, in detail

Verizon Connect’s route planner is built around the vehicle and the day’s stops, surfaced as a drag-and-drop calendar with cloud optimization assistance. The Reveal route planning page documents time windows, vehicle capacity, driver certifications and overnight trips as supported constraints, and claims the planner “analyzes millions of route options”. What the public product page does not surface is multi-depot rebalancing as a single optimization input, recurring or template routes as a named capability, named multi-day or month-long horizons, or a public REST surface for the optimizer itself with named assignment and load-balancing modes. eLogii’s optimizer covers exactly that side, callable over REST.

eLogii’s routing scope

eLogii’s optimizer is built around two engines and six configurable modes, all callable via REST and exposed to the dispatcher as controls they can see and adjust.

• Two engines. The Default engine optimizes 100 tasks in under 10 seconds for high-throughput daily planning. The Advanced engine takes more factors into account and is the choice for multi-depot, multi-day, long-haul and constraint-heavy operations.
• Three assignment modes. Optimize Everything (creates fresh routes including all assignments), Add to Routes, Keep Existing Assignments (incorporates new tasks into existing routes while preserving driver assignments), and Add to Routes, Keep Existing Assignments and ETAs (inserts new tasks into available slots without modifying existing stop sequences or ETAs).
• Three load-balancing modes. Most Efficient Routes (fewest vehicles), Balance the Minimum Number of Routes (across load, time, distance or job count), and Use All Vehicles / Finish as Soon as Possible (maximize speed).

Beyond the modes, eLogii ships the operational surface the Reveal route planner isn’t designed to lead on: multi-day and long-haul routing (“plan a single day or an entire month in one run”), multi-depot (“route across multiple depots, branches, or home start locations in a single run”), recurring service patterns via task and route template groups (weekly, monthly, quarterly, bespoke cadences modeled as inputs to the optimizer), multi-technician crew jobs with skills, capacity and SLA constraints, and rule-based re-optimization the operator can see and steer.

What this means in practice

If the planner’s morning routine is “open the Reveal route planner, confirm today’s stops on the calendar, drag the visit to the driver in the right area, let the planner optimize within the day”, Verizon Connect is the right tool and adding eLogii would be over-engineering. If the planner’s morning routine is “run the optimizer against today’s open jobs across three depots, balance against next week’s recurring service book, protect the SLA-locked priority bookings, route around the driver who’s off Tuesday”, the Reveal route planner is being asked to do a job it wasn’t built for and Field Service Dispatch’s drag-and-drop calendar is being stretched past its sweet spot. eLogii covers that side via REST API; Verizon Connect stays in place for the GPS, ELD, driver behavior and dashcam record.

When eLogii’s depth starts to matter

Verizon Connect covers the telematics-anchored fleet workflow well across light commercial, services and distribution. The signal that the routing problem has grown past what the Reveal route planner and Field Service Dispatch were designed for tends to be operational rather than headcount-based. Three patterns show up:

• Optimizer-driven assignment under heavy constraint. When the planner is spending the morning hand-balancing jobs across drivers, territories and skill sets, the optimizer should be making those calls. The Reveal route planner is designed as a drag-and-drop calendar with cloud assistance; once the placement itself is the bottleneck and the planner’s optimization assistance isn’t closing the gap, a dedicated routing engine needs to step in.
• Multi-depot rebalancing as a daily input. A regional service organization with three or four depots, or a distribution arm running parallel to the field-service business, needs the optimizer to see all depots as part of the same problem. The Reveal route planning product page does not document multi-depot as a supported constraint; cross-depot rebalancing as a single optimization input is left to the planner.
• Recurring service programs at thousands of stops. Quarterly preventive cadences, monthly inspection rounds, contract-driven recurring visits across a large customer base. Recurring or template routes are not surfaced on the Reveal route planning page; the optimization across the recurring book, interacting with reactive break-fix work, is the part that needs the engine.

Where any of these is the dominant shape of the work, eLogii is the routing layer. Where none of them is, the Reveal route planner with Field Service Dispatch on top is the right tool and adding eLogii is over-engineering. The honest answer for many Verizon Connect customers is “you don’t need eLogii.” The honest answer for the operations where the optimizer is the bottleneck is that eLogii is built for exactly that.

What changes once eLogii is in place

Verizon Connect continues to do the telematics work it’s built for: GPS trail, ELD compliance, driver behavior scoring, dashcam record, asset tracker estate. The difference shows up where the routing problem used to dominate. Brymec lifted productivity 30% and routing efficiency 20% on eLogii. ATS Building Products improved deliveries per route by ~98%. Porcelanosa runs eLogii with 95%+ ETA accuracy on daily distribution. Unimasters runs eLogii across a multi-country operation and achieved 50% less planning time and 49% fewer service calls. These are operational outcomes that come from moving the assignment problem from the planner’s morning into the optimizer:

• Slot booking co-pilot. When a customer is offered a time window, eLogii’s slot availability returns only slots that already fit the current optimized plan. Cuts failed visits ~35%. Plugs into whichever booking layer is in use over REST.
• Customer-driven rescheduling. Around 70% of reschedule requests handled without coordinator involvement. The customer picks a slot that already fits the plan and the route re-optimizes.
• Branded customer tracking pages. NPS surveys, safety briefings, access codes, treatment instructions, pushed onto the tracking page itself rather than handed off to a separate channel. Verizon Connect’s public product pages do not document branded tracking links as a named capability.
• Multi-brand tracking. Three brands run from one dispatch desk, each with its own logo, colors and layout.
• Map-native dispatch ops. Drag-and-drop reassignment with automatic ETA recalc on both routes; polygon, freehand and rectangle map selection; bulk actions on hundreds of stops; Gantt-style route timeline alongside the map; 13 historical segments refreshed overnight.
• Rule-based exception handling. Reroute a no-access visit to the nearest driver with the right skill, but don’t move any customer-confirmed bookings in the next 90 minutes. Visible to the planner, not buried in a black-box optimizer.
• Workflow analytics. Average time per step, skip rates, error patterns, completion data. Where driver hours actually went, not just where the vehicles went.

Running eLogii alongside Verizon Connect and the wider stack

The typical Verizon Connect-anchored stack: telematics for the vehicles (Verizon Connect Reveal for GPS and ELD, Coach for driver scoring, dashcams, asset trackers), an FSM or operational system of record (Salesforce Field Service, ServiceTitan, BigChange, Joblogic, Microsoft Dynamics 365 Field Service, or an ERP-anchored operational module), an ERP for finance and customer master data (Microsoft Dynamics 365 Business Central, Microsoft Dynamics 365 Finance & Operations, SAP, NetSuite), and a routing decision layer alongside the Reveal route planner for operations where the optimizer is the bottleneck.

eLogii is built for that shape. It plugs into Verizon Connect, leaving the GPS trail, ELD log, driver behavior data, dashcam record and asset tracker estate where they already are. The driver opens Reveal Driver or Verizon Connect Navigation in the cab; eLogii plans the route they take to get there, surfaces the live ETAs, picks up GPS, and pushes completion back into the operational system. The common patterns:

• Verizon Connect Reveal + eLogii. Verizon Connect owns the GPS, ELD, driver behavior and dashcam estate. eLogii owns the optimization layer where dispatch is dominated by multi-depot regional teams, recurring service programs at scale, or constraint-driven assignment across multi-day plans. Integration runs over the Reveal API and eLogii’s REST API; an iPaaS like Workato or MuleSoft is a common middleware choice.
• Verizon Connect + Field Service Dispatch + eLogii. Field Service Dispatch handles the dispatch board, drag-and-drop calendar and technician communication for small and mid-size service operations. eLogii sits as the routing engine for the multi-depot, multi-day, recurring-program horizons, called via REST and writing back the optimized routes Field Service Dispatch then enforces.
• Verizon Connect + FSM + eLogii. Salesforce Field Service, ServiceTitan, BigChange, Joblogic or Microsoft Dynamics 365 Field Service is the FSM. Verizon Connect provides the telematics. eLogii routes across the FSM’s jobs and the Verizon Connect fleet in one optimization run.
• Verizon Connect + ERP + eLogii. When the financial system of record sits in Business Central, Finance & Operations, SAP or NetSuite, eLogii reads operational data from the ERP and runs the optimization, writing routes back for execution. The Verizon Connect integration stays where it is for telematics.

What makes the stack pattern straightforward:

• 70+ REST endpoints across Tasks, Routes, Drivers, Vehicles, Depots, Zones, Schedules, Forms and Optimization, designed for clean integration into a wider stack.
• Full-parity sandbox at api-sandbox.elogii.com so integration work can run in parallel with the existing telematics and FSM rollout.
• Webhooks with live driver GPS and ETA stream push real-time state back to the FSM, the dispatcher view or the customer-facing app. No polling, no cron jobs, no stale data.
• Bulk operations. POST /tasks/createOrUpdateMany handles hundreds of tasks per call, built for high-volume ingest from any FSM or ERP.
• Telematics, FSM and ERP independent. Customers running Verizon Connect, Samsara, Geotab or TomTom on the telematics side, and any FSM or ERP on the operational side, use eLogii for the optimization layer alongside whichever stack they already chose.

Verizon Connect exposes a Reveal API through its developer portal for downstream subscribers. The two APIs combine cleanly: eLogii reads stops, vehicles, drivers and depots from the operational source-of-truth (FSM, ERP or Verizon Connect directly), runs the optimization across the routing horizons the Reveal route planner and Field Service Dispatch are not designed to lead on, and writes optimized routes and ETAs back. Verizon Connect picks up the in-cab GPS, ELD, behavior and dashcam stream; the optimized route is what the driver follows. Completion data flows back into the operational system for the work record, asset history and reporting.

API surface, side by side

Both sides expose APIs. Verizon Connect’s is the integration surface for the telematics data model, reachable through the Reveal developer portal and described as using “commonly accepted standards”. eLogii’s is the integration surface for a routing and optimization engine, with the optimizer itself callable as REST endpoints.

eLogii API

• 70+ REST endpoints across Tasks, Routes, Drivers, Vehicles, Depots, Customers, Zones, Forms, Schedules and Optimization. Full reference.
• Authentication: ApiKey header, generated in Dashboard > Configuration > API Keys. Machine-to-machine without an OAuth round-trip.
• Sandbox: api-sandbox.elogii.com, full parity with production at api-35.elogii.com.
• Bulk operations: POST /tasks/createOrUpdateMany handles hundreds of tasks per call, built for high-volume ingest from any FSM or ERP.
• Optimization callable via REST: all six modes available programmatically; dispatchers can lock specific routes, manually reorder stops, or re-run with new constraints.
• Seven webhook event types, including Driver/Task Tracking Update with live GPS stream and Route ETAs Update. No polling, no cron jobs.
• Custom fields end-to-end through driver app, webhooks and reporting.
• FSM, ERP and telematics independent via REST API, including SAP, Oracle NetSuite, Microsoft Dynamics 365 Business Central, Sage, Acumatica, IFS, Infor, Joblogic, BigChange, Simpro, ServiceTitan, FieldRoutes, Salesforce Field Service, Samsara, Geotab and Verizon Connect.

Verizon Connect API

• Reveal developer portal as the documented entry point for telematics data integration, described as using “commonly accepted standards”.
• Downstream integration patterns: Verizon Connect’s public API page describes pushing route information, start and stop times and ETAs to billing, payroll, HR, maintenance, CRM and finance systems for downstream customer billing or notification.
• What’s not surfaced on the public page: REST architecture confirmation, named webhook event catalogue, sandbox URL, bulk operation endpoints, or pre-built FSM connectors (no ServiceTitan, Salesforce Field Service, Microsoft Dynamics 365 Field Service, SAP or NetSuite logos named on the page).
• What’s not externally callable as named optimization modes: the Reveal route planner is positioned as a user-facing planner with cloud assistance, not as a documented set of optimization endpoints with operator-facing controls.

For an integration team, the typical pattern when Verizon Connect and eLogii are both in the stack: Verizon Connect owns the system of record for GPS, ELD, driver behavior and dashcam; the operational system (FSM or ERP) owns the work record; eLogii reads stops, drivers and depots from the operational source-of-truth and pulls vehicle and live-position data from Verizon Connect, runs the optimization across the horizons the Reveal route planner and Field Service Dispatch are not designed for, dispatches the route into the eLogii driver app, and writes the optimized routes, ETAs and completion data back to the operational system for the work record, asset history and reporting. Verizon Connect continues to capture the in-cab stream alongside.

Pricing and time to live

eLogii runs alongside Verizon Connect; it does not replace what you’re paying Verizon today. The question is what eLogii adds on top, and what it costs to add it.

eLogii pricing starts from $3,000 per month as a platform fee, banded by field staff, drivers, jobs per day and the modules required. Each band includes a quota; cost steps up when the operation crosses a band, not when you add an individual seat. Customers typically report 3 to 4× return on investment within 6 months, and combined Verizon Connect + eLogii rollouts complete in 3 to 5 weeks including the connector build.

Verizon Connect does not publish list pricing; the contract is per-vehicle, hardware-tied and quote-only, on multi-year terms with early termination charged against the remainder. The pricing models compose: Verizon Connect charges per vehicle for the telematics layer (with hardware fees), eLogii charges a platform fee for the routing layer. There is no per-seat or per-vehicle cost from eLogii.

When eLogii on top of Verizon Connect starts to pay off

Adding eLogii alongside Verizon Connect

Three steps for Verizon Connect customers whose planning problem has grown past what the Reveal route planner and Field Service Dispatch are designed to solve. Verizon Connect stays in place for the telematics; eLogii layers on as the routing engine.

Unimasters runs eLogii across a multi-country operation and achieved 50% less planning time and 49% fewer service calls. Multi-country rollouts deploy in weeks, not quarters.

Each pattern, in depth

The Reveal route planner is a useful planner inside Verizon Connect. Five patterns where the optimization decision layer alongside it is the bottleneck, each with its own deep dive:

Frequently asked questions

Is eLogii a Verizon Connect alternative or a complement?

Complement, in most cases. Verizon Connect is the telematics platform built from the Fleetmatics, Telogis and Networkfleet acquisitions, rebranded in 2018: Reveal for GPS and ELD, Spotlight as the manager app, Reveal Driver, Coach driver scoring, ELD LogBook, Navigation, dashcams, asset tracking, plus a route planning module and Field Service Dispatch as the FSM add-on. eLogii is the routing and optimization layer that runs alongside Verizon Connect when the planning problem starts to dominate: multi-depot field-service and distribution operations, dense same-day plans with hundreds of competing time-window constraints, optimizer-driven assignment across crews, recurring service programs at thousands of stops. Verizon Connect stays the system of record for the vehicle, GPS trail, ELD log and driver behavior data. integration runs over the Reveal API on one side and eLogii’s REST API on the other.

When does adding eLogii on top of Verizon Connect make sense?

When the Reveal route planner stops being the right place to solve the optimization problem and Field Service Dispatch’s drag-and-drop calendar is not closing the gap. Verizon Connect’s route planning module supports time windows, vehicle capacity, driver certifications and overnight trips, and is a useful planner for small and mid-size fleets running a handful of vehicles. eLogii layers on when the operation needs constraint-aware assignment across multi-day, multi-depot and recurring patterns in one optimization run, programmatic re-optimization with operator-visible rules, and slot booking that respects the current optimized plan.

Does Verizon Connect handle multi-resource crews, multi-day plans and multi-depot routing?

Partially. Verizon Connect’s route planning page documents time windows, vehicle capacity, driver certifications and overnight trips. Multi-depot is not explicitly listed as a supported constraint on the public product page; recurring route templates and named multi-day horizons are not surfaced either. Field Service Dispatch is reviewed 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. The Reveal Driver mobile app help center documents that for fleets over 500 vehicles drivers cannot use auto-suggested vehicle assignment and must search and assign manually. That’s the band where eLogii’s two engines and six configurable modes add depth, with Verizon Connect staying the system of record for GPS, ELD and vehicle telematics.

How does eLogii integrate with Verizon Connect?

Integration runs over the Reveal API and eLogii’s REST API. Verizon Connect’s API page describes a telematics API published through a Reveal developer portal that can push route information, start and stop times and ETAs to billing, payroll, HR, maintenance, CRM or finance systems; the page does not document REST architecture, webhook events or named pre-built FSM integrations. eLogii’s REST API has 70+ endpoints, ApiKey auth, a full-parity sandbox at api-sandbox.elogii.com and seven webhook events including live driver GPS and Route ETAs Update. The typical pattern, Typically: eLogii reads stops, vehicles, drivers and depots from the operational systems; runs the optimization across the routing horizons the Reveal route planner and Field Service Dispatch are not designed to lead on; writes optimized routes and ETAs back. Verizon Connect keeps the GPS trail, ELD log, driver behavior data and dashcam record.

How does pricing compare?

Verizon Connect prices per vehicle on multi-year hardware-tied contracts; pricing is quote-only and not publicly published. Early termination is charged against the remaining contract value. eLogii is a platform fee, banded by field staff, drivers, jobs per day and modules, from USD 3,000 per month. The pricing models compose: Verizon Connect charges per vehicle for the telematics layer, eLogii charges a platform fee for the routing layer. Customers typically report 3 to 4× return on investment within 6 months on eLogii.

How long does adding eLogii to a Verizon Connect stack take?

Typically 3 to 5 weeks from kickoff to a phased go-live, including building the custom connector against the Reveal API. eLogii reads stops, vehicles, drivers and depots from the operational systems; routes, ETAs and completion data flow back. Most teams start with the business unit where the Reveal route planner and Field Service Dispatch are leaking the most: usually a multi-depot regional book, a recurring service program at scale, or the part of the operation where the planner is hand-rebalancing every morning. Verizon Connect stays in place for everything telematics-related: GPS trail, ELD log, driver behavior, dashcam, asset tracking.

What happened with Verizon Connect’s international business?

Verizon sold Verizon Connect’s commercial operations in nine countries (Australia, UK, Ireland, Italy, France, Portugal, Poland, Netherlands and Germany) to Geotab in October 2025; the deal excluded product, engineering and non-sales teams. Verizon retains the North America business and the global product and engineering organization. eLogii integrations with Verizon Connect deployments remain technically the same; commercial relationships in those nine countries now sit with Geotab.

Why would a Verizon Connect customer add a routing engine instead of using the Reveal route planner and Field Service Dispatch?

Three reasons. First, the Reveal route planner and Field Service Dispatch were built as drag-and-drop dispatch surfaces with optimization assistance, tuned by Verizon’s own positioning toward small and mid-size fleets. Once the operation needs constraint-heavy multi-day, multi-depot optimization as the daily input, that surface is not the tool. The Reveal Driver app’s documented 500-vehicle threshold (manual vehicle search instead of auto-suggest) is one example of where the surface is built around a smaller fleet shape. Second, eLogii customers at scale report operational outcomes that go past what fleet routing alone delivers: Brymec 30% productivity and 20% routing efficiency; ATS Building Products 98% improvement in deliveries per route; Porcelanosa 60%+ planning time cut; Unimasters 50% less planning time and 49% fewer service calls. Third, eLogii exposes the optimizer itself as REST endpoints with seven webhook events, so the routing layer integrates cleanly into the Verizon Connect stack via the Reveal API.

Is eLogii enterprise-grade?

Yes. eLogii runs operations at scale: J-Club (9,000+ stores), NHS, Belfast City Council, Vergo Pest Management (400 technicians, Tyro Group), Bristow & Sutor (200+ enforcement agents, 200,000+ case visits routed annually), Porcelanosa, Caldic and Berkmann Wine Cellars. ISO 27001 and SOC 2 Type 2 certified.