Use Mapsly to plan optimized routes for multiple users and/or multiple days at once, for up to 1000 locations (“route jobs”) at a time, based on various job constraints and vehicle parameters, and adjustable optimization goals.
To account for job constraints of individual route jobs, like duration or required skills, simply map the fields where these parameters are stored in your CRM records or spreadsheet columns — and Mapsly will use their values when routes are built.
Vehicle parameters can be entered manually in Mapsly, or mapped on fields of any CRM object or a sheet in your spreadsheet, thus controlled directly from your CRM/spreadsheet as well.
Mapsly supports the following job constraints:
The supported vehicle parameters are:
In advanced routing, you are planning jobs. Depending on the job type, a job may result in one or two locations in the resulting routes. There are 4 types of jobs in Mapsly:
While pickup, delivery and pickup-delivery jobs can be planned without using capacity, these types of jobs are typically used in scenarios where vehicles have limited capacity and jobs have non-zero capacity (their cargo takes up certain space in vehicles).
Capacity can be one-dimensional, or can include multiple dimensions each being expressed by an integer number.
When planning routes for the current day, Mapsly will use your users’ real-time location, their today’s working schedule and the information about their planned routes for today to show their availability and suggest their starting time and location. (Learn more about user location tracking in Mapsly.)
You may assign “skills” that represent driver abilities or vehicle chacacteristics to individual Mapsly users and jobs — and Mapsly will be assigning a Mapsly user to a job only if the user has all the skills required by the job.
A skill is simply a text variable. You can store skills in your CRM as comma-separated text values in a text field, or in a single- or multi-choice picklist.
Since job constraints and vehicle parameters are pulled from the fields of your CRM records or spreadsheet rows, you can easily implement variable job constraints and vehicle parameters based on a condition — by adding new custom fields (columns) and filling them in with workflows using Mapsly automation suite or your CRM/spreadsheet capabilities.
You can also access your route data programmatically with the Mapsly automation suite, for example to send routing data to your CRM in real-time when a dispatcher publishes a route.
With the upcoming Spring & Summer 2023 updates we’ll be introducing more routing features and improvements:
routing-powered calendar that will allow you to see traveling time between meetings and plan your calendar events directly in Mapsly to avoid scheduling conflicts (Mapsly calendar will automatically sync with your CRM’s or Google calendar);
multi-day planning “around” existing calendar meetings and (bulk-)exporting route activities to the calendar as new meetings;
real-time replanning of today’s routes for your drivers, with new routes pushed to their mobile devices;
continuous (long-haul) routes: plan multi-day routes that start and end at specified locations with night breaks planned along the route;
offline capabilities for the Mapsly mobile apps;
app builder for creating customer-facing web apps, like an Uber-style interactive map showing the courier’s real-time location and their movement toward the recipient, order information and various buttons like Leave feedback, Update destination, etc.
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |