Field sales route optimization software for Salesforce teams

The field sales routing challenge

Field sales teams decide which accounts to visit and in what order while accounting for travel time, working hours, customer availability and business priorities. Tourvia calculates a workable sequence from those constraints.

Most field reps solve this puzzle manually, using experience and intuition. While experienced reps develop good instincts, manual planning has inherent limitations:

• Time-consuming: account selection, route sequencing, and Event creation are repeated manually
• Suboptimal sequences: Humans struggle to find the best visiting order when more than 5-6 stops are involved
• No constraint handling: Factoring in lunch breaks, time windows, visit durations and return-to-base constraints simultaneously is extremely difficult mentally
• Static plans: Manual plans don't adapt easily when a meeting is cancelled or a new priority appears mid-day

Manual planning vs. algorithm optimization

How most field reps plan today

1. Open Salesforce, check which accounts need a visit
2. Open Google Maps in another tab
3. Manually enter each address
4. Try different orderings to minimize drive time
5. Go back to Salesforce, create events for each visit
6. Enter account, contact, time and address for each event

This process takes significant time and produces results that are far from optimal, especially for routes with more than a handful of stops.

How algorithm-powered optimization works

1. Select accounts to visit on an interactive map (inside Salesforce)
2. Set constraints: start time, end time, lunch break, visit duration
3. Click "Optimize route": the algorithm calculates the best sequence
4. Review the optimized route on the map
5. Click "Create events": all Salesforce events are created in one click

The rep reviews one route that accounts for the configured working hours, visit durations, breaks, and time constraints before creating Salesforce Events.

Check the coverage capacity behind a visit policy before you optimize. The local calculator compares your own demand and time assumptions; it does not predict route results.

• Salesforce teams

  Teams already working in Salesforce

  Planning, visit execution, and reporting stay inside the CRM.

• Why it moves

  Time saved becomes extra visits

  Less manual planning and less re-entry in Salesforce gives reps more field time.

• Next step

  Validate the workflow during the trial

  Test installation, route planning, mobile visits, reporting, and the annual seat cost.

When teams evaluate a switch

Field sales teams switch when manual planning wastes rep time, visit coverage becomes inconsistent, or route data has to be copied between Salesforce and another tool.

• For reps

  Too much morning planning and re-entry

  The pain is not just building a route. It is rebuilding the day across Google Maps, Salesforce, and manual Event creation.

• For managers

  Coverage varies too much by rep

  When planning quality depends on territory memory alone, visit density, repeat coverage, and reporting discipline drift fast.

• For finance and ops

  Annual cost is easy to calculate

  Each licensed user costs €360 excluding tax per year. Ten users cost €3,600; twenty cost €7,200.

How route optimization works

Tourvia operates a constraint-aware routing engine designed for field sales workloads. It handles:

• GPS coordinates: Each Salesforce account's Latitude/Longitude (geocoded in Salesforce)
• Time windows: Start time, end time, appointment slots
• Service duration: How long each visit takes
• Break constraints: Lunch break timing and duration
• Travel time matrix: Realistic driving times between all points

The engine combines road travel times and distances with the constraints configured for the field day.

Tourvia operates the routing infrastructure in France (OVHcloud Gravelines). This means:

• No dependency on Google Maps or any paid third-party service
• No per-calculation charges
• Worldwide coverage, from Europe to Asia, Africa, Americas and Oceania
• EU-hosted routing infrastructure for organizations that care about data residency

Why CRM integration matters

Route optimization in isolation, without CRM integration, solves only half the problem. The real value comes from connecting route planning with your customer data.

CRM-aware filtering

Before planning a route, filter accounts by any Salesforce field: last visit date, account type, revenue, territory, owner. This ensures you're visiting the right accounts, not just the nearest ones.

Automatic event creation

The biggest time saver is creating Salesforce Events in bulk. After optimizing a route, one click creates all calendar events with the correct account, contact, time slot and address. No manual data entry.

Visit history and coverage analysis

When route data lives in Salesforce, managers can build reports and dashboards showing visited accounts, visit frequency, under-covered territories, and field-time allocation.

Permission-aware access

A native Salesforce route planner respects your org's security model. Reps see only the accounts they have access to. Sharing rules, profiles and field-level security all apply.

Mobile optimization for the field

Field sales reps work on smartphones and tablets, not desktop computers. A route optimization tool must work well on mobile to be useful in the field.

Key mobile capabilities

• Responsive interface: Map and controls adapt to smaller screens with a bottom-sheet panel design
• GPS geolocation: Tap a button to see all Salesforce accounts within a configurable radius around your current position
• Navigation handoff: Send the optimized route to Google Maps or Waze for turn-by-turn navigation
• Works in Salesforce Mobile: Teams can use it inside the Salesforce mobile environment instead of rolling out a separate field sales app

Nearby accounts: the impromptu visit feature

One of the most valuable field features is finding nearby accounts. When a meeting finishes early or gets cancelled, reps can instantly see which Salesforce accounts are nearby and add a spontaneous visit to their day.

Field service route optimization vs field sales

The terms "field service route optimization" and "field sales route optimization" are sometimes used interchangeably, but they describe different workflows with different priorities.

Field service: technicians, SLAs, and emergency dispatch

Field service teams send technicians to customer sites for installation, maintenance, or repair. Their scheduling is driven by service-level agreements (SLAs), equipment availability, and skill-based assignment. A broken HVAC unit in July cannot wait until Thursday because the route looks better that day. Dispatchers need to handle emergency calls mid-day, reassign jobs when a technician runs late, and track parts inventory per van.

Dedicated field service platforms like ServiceTitan and WorkWave are built for exactly this. They include dispatch boards, work order management, parts tracking, and customer self-service portals. If your team's primary job is reactive maintenance with strict SLA windows, those tools are worth evaluating.

Field sales: account visits, relationships, and territory coverage

Field sales teams visit prospects and existing customers to build relationships, close deals, and ensure account coverage across a territory. Their planning is driven by pipeline value, visit frequency targets, and geographic density. A rep might need to visit 8 accounts in Lyon this week, prioritized by deal stage and days since last contact. There is rarely an emergency dispatch scenario.

When one tool can serve both

Some organizations have hybrid teams. A medical device company might send the same rep to both sell new equipment and check on installed units. A building materials distributor might combine sales calls with delivery coordination. If these teams already use Salesforce as their system of record, a single route optimization tool inside the CRM can handle both visit types. Tourvia works for any Salesforce account-based visit planning, whether the visit is a sales call, a service check, or a delivery confirmation. The key requirement is that the accounts and contacts live in Salesforce.

Measure the result against your own baseline

Tourvia does not publish a universal ROI benchmark. Territory density, current planning habits, visit duration, and customer availability all affect the result.

Use the 30-day trial to compare four measures before and after deployment:

• weekly planning time per rep;
• distance driven per completed visit;
• visits completed per rep;
• time spent creating and updating Salesforce Events.

For 10 licensed users, Tourvia costs €3,600 excluding tax per year. Compare that fixed annual budget with the measured time, mileage, and visit-capacity changes from your pilot.

The Tourvia approach

Tourvia is delivered as a Salesforce managed package. Reps plan and execute visits in Salesforce, while route calculations are processed by Tourvia infrastructure hosted in France.

The workflow keeps route planning, Event creation, mobile execution, and reporting attached to the Salesforce records that drive the day.

What makes it different

• Salesforce workflow: Lightning components, Salesforce records, Events, reports, and Permission Set Groups
• Per-user pricing: €30/user/month billed monthly at €360/user/year per licensed user.
• Tourvia routing service: Routing infrastructure hosted in France, with processing described in the DPA
• International routing: Availability depends on the road-data coverage for the relevant territory
• Multi-language: Interface available in French, English and Spanish
• EU-hosted routing infrastructure: Route calculations run on infrastructure hosted in France, which supports EU data residency goals

Getting started

1. Install the 30-day trial from the AppExchange listing. Validate fit inside your Salesforce org first
2. Configuration: Your Salesforce admin installs the managed package and configures filters and permissions
3. Adoption: Your team uses the included documentation
4. Subscribe to continue: Keep the complete feature set after the trial

The customer controls the rollout timeline. Installation and configuration are documented for the Salesforce admin.

Who Tourvia is built for

Tourvia is built for Salesforce-led field sales and recurring customer visits. It is not a technician dispatch or service appointment orchestration product.

• Salesforce field sales

  Account-based field sales inside Salesforce

  Reps plan visits from Salesforce accounts, create Events, log outcomes, and give managers reportable CRM data.

• Predictable pricing

  Teams that want predictable rollout economics

  Public per-user pricing lets managers, admins, and finance calculate the yearly cost directly.

• Use a different category

  Emergency dispatch or field service SLAs

  If you need live dispatching, technician skills matrices, or service appointment orchestration, use a dedicated field service stack instead.

Frequently asked questions

• Execution

  Can the optimized route turn into a usable Salesforce day without re-entry?

• Economics

  What is the yearly cost for every licensed user who needs Tourvia?

• Team fit

  Is this a Salesforce-led field team, not a dispatch-first service operation?