How to set up route planning in Salesforce

Adding route planning to Salesforce does not require custom development. With a managed package from AppExchange, you get a Lightning Web Component that plugs into your existing org. This guide walks through the full setup using Tourvia as the example, from installation to a working route on screen.

What you need before you start

Before you begin, confirm you have the following:

• A Salesforce org with API access. Enterprise, Unlimited, and Developer Editions include API access by default. Professional Edition requires the API add-on.
• System Administrator profile (or equivalent permissions) for the person doing the installation and initial configuration.
• Accounts with addresses. The component geocodes your account addresses to plot them on the map. If your accounts have blank or incomplete addresses, they will not appear. Clean up your data first.
• About 30 minutes. Installation takes roughly 10 minutes. Configuration and verification take another 20.

If your org uses a sandbox, consider installing there first to test before deploying to production.

Step 1: Request trial

Request a 30-day trial through the contact form. We qualify the Salesforce org, confirm the trial scope, and then guide your admin through access and first setup.

During installation, you choose whether to install for all users, specific profiles, or admins only. For a first install, "Install for Admins Only" is the safest option. You can extend access later through permission sets.

The managed package deploys the following to your org:

• Permission sets for granting user, manager, and admin access levels.
• Custom Metadata Types for org-wide configuration defaults.
• Lightning Web Components that you will place on Lightning pages using App Builder.
• Custom objects and fields for visit tracking and route storage.

Installation typically completes in under 5 minutes. You will receive a confirmation email from Salesforce when it finishes. For detailed steps, see the Setup Guide.

Step 2: Assign permission sets

Tourvia creates permission sets during installation. These control which users can access the component and which features they see.

There are two levels:

• 30-day trial access. Lets qualified Salesforce teams validate map visualization, account plotting, and route planning before subscription.
• Paid access. Adds route optimization (automatic stop sequencing), advanced filters, and reporting features. Requires an active subscription.

To assign permission sets:

1. Go to Setup > Users > Permission Sets.
2. Find the Tourvia permission sets in the list.
3. Open the permission set you want to assign.
4. Click Manage Assignments, then Add Assignment.
5. Select the users who need access and save.

If you installed for "Admins Only" in Step 1, this is where you grant access to your field reps and managers. Assign the free permission set first, verify everything works, then add paid access once your subscription is active.

For teams using permission set groups (recommended by Salesforce for scalable access management), you can add the Tourvia permission sets to an existing group rather than assigning them individually.

Step 3: Add Tourvia to a Lightning page

The component is a standard Lightning Web Component. You place it on any Lightning page using App Builder, the same drag-and-drop editor you use for other page layouts.

Common placement options:

• Home page. Reps see the map and their planned route as soon as they log in. Good for teams that plan routes at the start of each day.
• Account record page. The map appears in the context of a specific account, showing nearby accounts. Useful for reps who want to add visits around a specific location.
• Dedicated app page. Create a standalone "Route Planning" page in a custom Lightning app. Best for teams that want a full-screen map experience.

To add the component:

1. Open Setup > Lightning App Builder.
2. Edit the page where you want the component (or create a new one).
3. In the component panel on the left, search for "Tourvia".
4. Drag the component onto the page canvas.
5. Save and activate the page.

If you are placing it on a record page, make sure the page is assigned to the correct record type and profile. If reps cannot see the component after activation, check the page assignment in App Builder.

Step 4: Configure filters and defaults

Tourvia supports two layers of configuration:

Org-wide defaults are set through Custom Metadata Types in Salesforce Setup. These apply to every instance of the component across your org. Use them for settings like default map center, distance units, and which Salesforce objects to display.

Page-specific settings are configured through App Builder component properties. When you select the Tourvia component on a Lightning page, the right panel shows configurable properties. Use these to override org-wide defaults for a specific page, for example, setting a different default filter on the Home page than on an Account page.

The Configuration Guide includes 4 copy-paste presets for common scenarios:

• Field sales team with daily route planning
• Account management with territory-based filtering
• Service team with appointment-based scheduling
• Manager view with team-wide route visibility

Start with a preset, then adjust the filters and defaults to match your team's workflow.

Step 5: Verify and go live

Before rolling out to the team, run through this checklist:

1. Open the component. Navigate to the page where you placed it. The map should load and display your accounts as pins.
2. Check geocoding. Verify that accounts with valid addresses appear on the map in the correct locations. If accounts are missing, check that their addresses are complete and correctly formatted.
3. Test route creation. Select a few accounts and create a manual route. The component should draw a path between the selected stops.
4. Test route optimization (premium). If you have an active subscription, click the optimize button. The stops should reorder to minimize travel time.
5. Create a test event. Plan a visit to an account and confirm that it creates the expected Salesforce event or task record.

If something is not working as expected, the User Guide covers common issues including missing map pins, geocoding errors, and permission problems.

Once verified, communicate the rollout to your team. Share the page location, explain what the component does, and point them to the User Guide for self-service help.

What comes next

With a 30-day trial, your team can validate the Salesforce-native workflow with your own data before moving to the paid subscription.

Tourvia Pro costs EUR 30/user/month (excl. tax) per licensed user. Pricing is €30/user/month, billed annually. As your team grows, add licensed users at the same €30/user/month public price. Larger enterprise deployments can be quoted separately when needed.

Two setup paths are available:

• Self-setup (EUR 0). Follow this guide and the Configuration Guide. Most admins complete it in under 30 minutes.
• Fully managed setup (EUR 3,000). Tourvia handles installation, configuration, data validation, user training, and go-live support. Best for teams that want a hands-off deployment. Learn more about consulting.

Frequently asked questions

Do I need API access?

Yes. Tourvia requires a Salesforce edition with API access. Enterprise, Unlimited, and Developer Editions include it by default. Professional Edition works only if you have purchased the API add-on. The component uses API calls for geocoding account addresses and for route optimization calculations.

Can I test before subscribing?

Yes. A 30-day trial can be requested through the contact form for qualified Salesforce orgs. The trial scope is confirmed before activation, then the paid subscription covers route optimization and field execution. Request a 30-day trial, verify it works with your data, and move to the subscription when you are ready.

How long does setup take?

About 30 minutes total. Installation from AppExchange takes roughly 10 minutes (most of that is waiting for Salesforce to process the package). Assigning permission sets, placing the component in App Builder, and configuring defaults takes another 20 minutes. The biggest variable is data quality: if your account addresses are incomplete, you will need additional time to clean them up before accounts appear correctly on the map.