Regular visit planner helps your sales or service team plan regular visits to your customers, partners, points of sales, construction sites, social services, or any other locations saved in your CRM as records of any objects, based on a variety of parameters such as required visit frequency and duration, which can vary between records, sales reps’ working schedule, planning period, and others.
The Planner produces daily routes for each sales rep weeks or months ahead, ensuring minimal travel time across the team, thus boosting your sales team’s efficiency.
Regular visit planner can be used in all industries that require recurring visits to locations of service, sales or inspection, including:
For simplicity, in the description below we’ll be calling traveling employees sales reps, and their team – sales team. But all features described below also apply to service and inspection teams just as well.
Regular visit planner plans visits to CRM records of any object. You may set a condition that must be met for a record to be selected for planning, the desired frequency of visits and the desired duration of a visit.
Visits are planned within the configurable working hours of your sales reps, overlapping with the business hours of your organization.
Optionally, you may map a CRM field that contains the visit frequency for a particular record and another CRM field with the visit duration for a record. When filled in, values from these fields will override the default frequency and duration.
When planning optimal routes, Mapsly also accounts for live and historic traffic data to ensure the minimal possible travel time.
In the Individual mode Mapsly will plan daily routes for an individual sales rep that will contain CRM records pre-assigned to this sales rep and will aim at minimizing their drive time thus maximizing the number of visits they can make per day.
In the Team mode:
Planning jobs can be executed in one of the two ways:
When re-planning, you can ’ll be able to also indicate whether you’d like to preserve planned visits for a certain number of days ahead and start re-planning only after that, for example since TODAY + 2 days – to always preserve today’s and tomorrow’s visits.
You may configure multiple planners, if you need to plan visits to several objects at once, or when you need the planner to work based on different parameters for different subsets of records or different groups of sales reps.
A planner can produce routes – daily traveling schedules for a sales rep – or a record of a certain type, like a Meeting or an Event, or both at once. This allows you to adjust planning deliverables to match your business processes.
Mapsly uses a commercial highly-optimized traffic-aware Vehicle Routing Problem solving API with a proprietary algorithm introducing recurrence to efficiently plan recurring visits for a sales team at once – to minimize the combined travel time and maximize the capacity of the team.
To use the Regular visit planner, you need to subscribe to a monthly package of Routing credits. Each time the Planner is executed, it consumes the amount of credits that equals to the number of locations that need to be visited multiplied by the size of the traveling team.
Example: When you execute a Planner that plans visits to 100 records for 5 users, you consume 500 routing credits.
The size of the routing credit package you’ll need depends on your forecast usage of the Planner. For example, if you’re planning to run the kind of planning mentioned in the example above every working day, ~20 days a month, you’ll need to purchase 500 * 20 = 10,000 monthly routing credits.
As your usage changes, you may upgrade to a higher or downgrade to a lower package size – to better match your needs.
The routing credit package is automatically replenished on the 1st day of every month.
Contact us in chat or at [email protected] to get a quote, schedule a demo, or to learn more about Mapsly and the regular visit planner.
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. |