Tourviaformerly RouteForce

Free admin utility Browser-only CSV check

Screen Salesforce data before you plan a route.

Read a Salesforce CSV in this browser for recognised address fields, usable coordinate pairs, GeocodeAccuracy, owner coverage and territory coverage. The checker reports aggregate counts only. Your file never leaves this browser tab.

  • Local: no CSV upload or server-side processing
  • Count-based: no record values, file names or raw headers appear in the result
  • Vendor-neutral: this is not a Tourvia compatibility verdict

Local workspace

Inspect an export without sending it anywhere.

Choose a CSV exported from Salesforce, or run the synthetic demonstration file. The scan checks field presence and simple data-quality signals; it does not prove that an address or a geocode is correct.

Choose a Salesforce CSV

Drop a .csv export here or select it from your device. The file is read with your browser’s local FileReader; it is not uploaded, stored or displayed as record values, file names or raw headers.

No CSV selected. Choose an export or run the synthetic demonstration.

Privacy boundary: page analytics may record a page visit, but this checker sends no file, row, header, file name or result to Tourvia. Use a redacted export if your internal policy requires it.

Interpret the result

A coordinate is not the whole decision.

Route planning depends on the records you intend to visit, the address source you trust, your territory model and the operational constraints for a field day. This screen helps start that review; it cannot replace it.

01

Confirm the address source

Accounts can carry more than one address. Make sure the export uses the address that represents the visit location, not simply the first address available.

02

Sample the map

Open a representative sample in Salesforce. A pair can be in range and still point to an old address, a postcode centroid or the wrong site.

03

Test the field-day rules

Only then validate visit duration, time windows, breaks, existing Events and territory coverage with the people who plan the work.

Privacy

The CSV remains local to your browser.

This page has no upload endpoint. The checker reads the selected file in browser memory, generates aggregate counts, and clears its local result when you choose “Clear local result”, reload or close the page.

Do not treat this screen as a data-processing agreement. Your own Salesforce export, browser and device policies still apply. For Tourvia’s route-calculation data boundary, read the Privacy Policy and DPA.

Questions

Before you inspect an export

Does the checker upload my CSV?

No. The selected file is read in browser memory. The checker has no upload endpoint and does not send rows, headers, counts or downloaded summaries to Tourvia.

Which Salesforce fields does it recognise?

It looks for common Billing, Shipping, Mailing, Other and generic address headers; latitude and longitude pairs; GeocodeAccuracy; owner; and territory fields. Custom field labels and exports vary, so the recognised category counts are always part of the review.

Does a clear result prove that records are accurate?

No. It means the screen found usable coordinate syntax according to the checks shown. It cannot establish that coordinates represent the intended visit location, that a geocode is current, or that a route will be feasible.

Does this prove Tourvia compatibility?

No. This is a vendor-neutral CSV data screen. A Tourvia trial evaluates the actual Salesforce objects, configuration and field workflow in your own org.

Next field check

Once the records are mapped, test the workflow.

Tourvia turns selected Salesforce records into an optimised route, timed Events, field visits and reporting. Validate that workflow during the complete 30-day trial.

Continue the evaluation

See how route planning stays connected to Salesforce records and Events, then use the trial to test it in the target org.