The call cycle template: a 4-week A/B/C visit plan you can copy, with the math to route days.

The call cycle template: account list

One row per account. Tier and rhythm are set by the manager for the whole team, the rep fills in the last visit, and the next due date follows from both. The five rows below are example accounts; replace them with your own.

In a spreadsheet, the next due date is one formula: =G2+7*D2 (last visit plus the rhythm in weeks). Sort by that column every Friday and the rep's next week is the top of the list. In Lead Mapper the rhythm sits on the account itself, the overdue ones are red on the map, and the AI builds the week from them, so nobody sorts anything.

The 4-week call cycle planner: one grid per rep

The list says who is due; the grid says where the rep is each day. One area per day, so the A, B and C accounts of that area share one drive. The grid repeats every four weeks.

Week 4 keeps one day open on purpose: every cycle loses visits to sick days and cancellations. Lead Mapper moves a missed visit into the next open slot in the same area automatically.

Does your call cycle fit the week? The calculation

This is the step the templates we read leave out. A cycle is only a plan if the visits it creates fit into the days a rep has. Example for one rep with 120 accounts, split with the ABC example Portatour publishes (A "15% of your total customer base but account for 70% of sales", B 25 percent, C 60 percent; portatour.com, read 11 November 2026). In Lead Mapper the tier is a field on the CRM account.

At 6 visits a day (an example; Repsly's field data puts U.S. reps at "7.32" visits per rep per day, repsly.com, read 11 November 2026), 22.5 visits a week are 3.75 route days. That leaves 1.25 days a week: the office Monday and a few hours of prospecting. For a team of 40 reps the same cycle is 3,600 visits every four weeks. If the result is above four route days, the cycle does not fit, and the fix is a decision, not more hours: C to every 16 weeks, part of C to phone calls, or fewer accounts per rep, which Lead Mapper rebalances on the map.

M-Assist writes that consumer goods field reps "typically manage 80 to 150 outlets per beat cycle" (blog.massistcrm.com, read 11 November 2026). At 150 accounts the same rhythm needs 4.7 route days a week, with no office day left. Lead Mapper runs this check per rep on the live account list, before the cycle goes out.

Customer call cycle template versus customer visit plan

A customer visit plan template is the monthly view of the same data: the dates the cycle produces, written into the calendar. Lead Mapper reads the rep's Google or Microsoft calendar, keeps the meetings already booked, and fills the open hours with the accounts due nearby.

Three rules that keep a sales call cycle template alive

• The manager sets tier and rhythm, the rep never does. A rep who sets their own rhythm visits the friendly accounts first. Lead Mapper stores tier and rhythm as fields on the CRM account, editable only by the manager role.
• Measure coverage, not visits. The number that matters each Friday is the share of A accounts visited inside their rhythm. Lead Mapper shows it per rep on the manager map, overdue accounts in red.
• The visit is logged where the account lives. A spreadsheet next to the CRM is out of date after the first week. Every Lead Mapper visit is written to the CRM as an activity with time and place, and the next due date moves on its own.

Upload this template as a CSV or connect your CRM, and every rep's cycle runs on the map the same day, with each rep's week built for them: start the 7-day free trial. More: sales route planning, sales territory plan, sales call report template and sales ride along checklist.