For a general description of Mapsly's routing capabilities, please take a look at the Routing overview page on our website.

Use Mapsly’s web and mobile apps to build optimal routes via multiple locations, with live and historical traffic data taken into account.

With the Mapsly Routing feature, you can:

NOTE: You'll need the Pro or Enterprise plan to plan routes for multiple users and/or multiple days at once, or to use job/vehicle parameters.

You can plan a route for 4 types of jobs: service (which is the default type), pickup, delivery, and pickup-delivery. All input jobs are planned as activities in the resulting routes.

A service, pickup, and delivery job produces one activity in the resulting route, while a pickup-delivery job produces two activities: one for the pickup, and one for the delivery — so we use two different terms to refer to input jobs and resulting activities.

A job may be represented by a record of any object with a defined location fields, or as a manually added location on a map. A job represented by a record may be any of the 4 types, while a manually added location is assumed to be service.

With Mapsly Routing you can plan optimal routes for multiple users and/or days at once. The planning is executed within a routing session which takes a list of jobs and a list of users as an input and produces one or multiple routes as a result.

A routing session is a system object, so you may view your Routing session records in the table view.

A routing session starts in the design stage, so you can add/remove jobs and participating Mapsly users. When you click the Build button, your routing session moves to the draft stage, and you'll be able to see the resulting routes that are in the draft status.

From the draft status, you may return to the design stage to add/remove jobs, add/remove users, or change some of the routing session's settings and re-build routes.

Once you're satisfied with the draft routes (while in the draft stage), you may click Save to publish the resulting routes for your users. Published routes will become visible to your users and can be loaded into the Route panel for execution.

Since in Mapsly each route, both in draft and publish state, is represented by a record in the Route system object, Mapsly users with access to the Route object may view all routes in the Table view and perform group actions on them, like their re-assigning to other users and bulk-deletion. Assigning a route to a user is done by updating the route's Owner field.

A Route viewer tool allows you to see one or several routes at a time including those belonging to multiple users and/or multiple days at once.

When in the draft stage of a routing session, the Route viewer will also allow you to see your draft routes, or a combination of the draft and published (live) routes at the same time.

To address the highly varying nature of routing workload between Mapsly clients, we introduced daily routing credits that are consumed when your team clicks Build in the Route panel.

For example, when your routing session contains 100 jobs and 5 users, clicking Build will consume 500 routing credits (the number of jobs multiplied by the size of the traveling team).

However, unlike visit planner credits (which are monthly and are not included in your plan by default):

Additional packages of routing credits are available for an additional fee — to modify your daily routing credit package please contact us in chat or at [email protected].

Using the Routing session object you can:

Please select the topic you'd like to learn more about:

See also: