Visits and Beat Planning
Stop counting visits. Start counting what they achieved.
Build reusable beats by territory, send them for approval, and give every rep a timeline of visits with check-in, check-out, tasks and reasons. Every visit leaves a record on the Salesforce account, so the next one starts where the last one ended.
Built natively on Salesforce · by Cloud Ingenious, a Salesforce Summit Partner
Check out
Disposition: Order placed
"Wants Diwali display stand next visit. Ask about 500g pack."
In short
F1 Agent Visits and Beat Planning is a Salesforce-native module for scheduling, executing and recording customer visits by field sales teams. It supports planned and unplanned visits, reusable single-day and multi-day beats, manager approval of beats and a territory hierarchy that links customers, users and coverage.
Reps work from a mobile visit timeline with navigation, check-in and check-out. Each visit can carry tasks such as orders, returns, competitor analysis, custom forms and AI shelf audits, and every cancellation or reschedule records a reason. The full visit history appears on the Salesforce account.
The real problem
Ten missed visits can mean ten different things. Your report shows one number.
What the report says
10
incomplete visits this week
Is that a rep who is not working? Or a market where shops were closed for a local holiday? Without reasons, both look identical.
What actually happened
Only three of the ten are a performance conversation. The rest are customer behaviour you can plan around.
Beats rebuilt every week
The same Monday outlets selected one by one, every Monday, in a spreadsheet that never reaches Salesforce.
"Visited" means "arrived"
A check-in proves presence, not progress. Nobody defined what the visit was supposed to achieve.
Memory as the CRM
What the shopkeeper asked for last time is in the rep's head. Change the rep and you start from zero.
Territories nobody checks
Important customers in one area go unvisited for weeks, and no report shows it until the order drops.
What good visit management looks like
Six visits that sold beat ten that didn't.
Most visit tracking measures activity: how many check-ins. Mature teams measure outcomes: what each visit was meant to accomplish and whether it did. The shift starts with defining tasks before the rep leaves.
Rep A
Activity view
10 visits. Nearest outlets, quick check-ins, no tasks defined. Order value: ₹6,200.
Rep B
Outcome view
6 visits. 4 orders, 1 return, 2 shelf audits, 1 competitor report. Order value: ₹41,800.
Plan the who, not just the when
Beats should be built around territory and customer value, then reused. Rebuilding lists weekly invites drift toward convenience.
Define success before the visit
Attach tasks to the visit: order, return, form, audit. A visit is complete when the tasks are, not when the rep leaves.
Make every miss explain itself
Require a reason for every cancellation and reschedule. It turns a performance argument into a planning conversation.
Want to see what your beats are really covering?
Send us one territory's account list and current beat plan. We will show coverage gaps and how the same week would look as reusable F1 Agent beats.
Planning
Beats: build once, approve, reuse every week.
A beat is a reusable visit plan: a set of customers grouped by territory and assigned to a rep. It can cover one day or a range of days.
Pick from the hierarchy
Customers and users are already mapped to territories with operating hours.
Group customers into a beat
Single day or multi-day range. AI can suggest high potential customers to include.
Send to the manager
A rep's proposed week goes through approval before it becomes final.
Lands on the rep's timeline
Every Monday, automatically. No rebuilding.
Multi-day beat · Jaipur and Ajmer tour
Assigned to Priya Nair · 14 customers · Rajasthan North territory
Day 1 · Tue
Jaipur Malviya Nagar · 5 dealers
62 km · local
Day 2 · Wed
Jaipur Vishwakarma Industrial · 5 dealers
48 km · local
Day 3 · Thu
Ajmer · 4 dealers
138 km · outstation
Territory management underneath it all
Maintain a territory hierarchy. Associate customers and users with territories, manage operating hours by territory, plan beats around them and measure coverage territory by territory.
Managers can finally answer: are all important customers in Territory A being covered? Who owns this area? Which customers have not been visited recently?
Execution
One visit, from timeline to customer history.
See the day on the timeline
Today's visits, with the option to switch dates and check past or future schedules. Planned visits come from beats or individual scheduling on the account.
Navigate to location
One tap opens maps with the customer location, route and estimated travel time.
Check in
Marks when the customer interaction actually started. Lumina can brief the rep with past meetings, orders and outstanding amounts.
Complete visit tasks
Take an order, take a return, record competitor analysis, fill a custom visit form or run an AI shelf audit. You decide which tasks each visit carries.
Check out
Capture meeting notes, disposition, photographs and anything else you configure.
History on the account
All visits, completed and cancelled, with reasons and outcomes, build a chronological record on the Salesforce account. The next rep starts with context.
Cancel or reschedule, with a reason
Missed, cancelled by customer, cancelled by salesperson or your own configured reasons. Reschedules capture why the visit moved.
Planned and unplanned, both captured
Schedule a visit from any account record, or log an unplanned visit when the rep spots an opportunity in the area. Both carry the same tasks and history.
Custom visit forms
Picklists, multi-select picklists and other configured questions, assigned to the right reps. A retail audit and a site survey can live in the same app.
Use cases
How teams use visits and beats.
FMCG weekly beats
From Excel lists to reusable beats
Problem: 120 reps, beats rebuilt every week. Solution: One beat per rep per weekday, assigned once, with order and shelf audit tasks. Outcome: planning time cut to exceptions only.
Distribution governance
Approve the week before it starts
Problem: senior reps chose their own dealers. Solution: Proposed beats go to the area manager for approval every Friday. Outcome: neglected dealers back on the plan.
Territory handover
A new rep who already knows the customer
Problem: a resignation took two years of context with it. Solution: Visit history, notes and dispositions live on the account. Outcome: the replacement picks up mid-conversation.
Industries
Different visits, same discipline.
FMCG and consumer goods
Dense daily beats, high frequency. Visit tasks for order, shelf audit and competitor check turn each outlet stop into a merchandising and revenue record.
Distribution
Dealer visits with approval governance and returns. Cancellation reasons separate dealer-side issues from rep performance.
Equipment, machinery and durables
Multi-day outstation beats, custom forms for site assessments, and account-level history across long sales cycles.
Compare approaches
Where each approach to visit planning holds up.
| F1 Agent | Excel beat lists and WhatsApp | Generic field app | Salesforce Events and Tasks | |
|---|---|---|---|---|
| Reusable and multi-day beats | Yes, with approval | Rebuilt manually | Often single day | Not natively |
| Check-in and check-out at location | Yes, with notes, disposition, photos | No | Yes | Custom build |
| Visit tasks with outcomes | Orders, returns, forms, shelf audit, competitor | No | Forms, sometimes orders | Custom build |
| Cancellation reasons | Required, configurable | Rarely | Sometimes | Picklist you maintain |
| Honest trade-off | Needs Salesforce and some setup of territories and tasks | Zero cost, zero visibility | History lives outside your CRM | Native, but no field workflow |
Why F1 Agent
Visits that belong to the account, not the app.
Because F1 Agent is built natively on Salesforce by Cloud Ingenious, a Salesforce Summit Partner, every beat, visit and outcome sits on the records your sales, finance and leadership teams already use. Actions are also available on the standard Lightning record page.
Plan a beat planning pilotStart with one territory
Convert one team's beats and compare coverage after a month.
Your tasks and forms
Configured to what your visits need to achieve.
Existing accounts and territories
Nothing to migrate from a second system.
Phase in AI later
Add AI recommendations and route optimization once beats are stable.
"Once every cancelled visit had a reason, our Monday review changed. We stopped arguing about effort and started fixing the outlets that kept cancelling."
FAQ
Visits and beats, answered.
What is a beat in field sales?
A beat is a reusable visit plan: a set of customers or locations, usually grouped by territory, assigned to a rep for a day or a range of days. Instead of selecting customers one by one each week, the same beat is reused.
Can a beat cover more than one day?
Yes. F1 Agent supports a beat range across multiple days, which suits large territories and outstation tours.
How does beat approval work?
A rep can prepare a proposed beat, for example next week's coverage plan, and send it to a manager for approval before it becomes final. You decide where approval is required.
What is the difference between planned and unplanned visits?
Planned visits are scheduled in advance from an account or through a beat. Unplanned visits are logged when a rep meets a customer or prospect they spot while in the area. Both are recorded with the same check-in, tasks and check-out.
What are visit tasks?
Visit tasks define what should happen during a visit: take an order, take a return order, perform competitor analysis, complete a custom visit form, perform an AI shelf audit or other business-specific activities.
Can we configure cancellation reasons?
Yes. Reasons such as missed, cancelled by customer and cancelled by salesperson are available, and you can add your own. Reschedules can also require a reason.
Where does visit history show up?
On the Salesforce account: all visits, completed and cancelled visits, cancellation reasons, outcomes and notes, in chronological order. It is also available to reps on mobile before the next visit.
Can users check in from Salesforce on desktop?
F1 Agent actions can be exposed on the standard Lightning record page, so users can access field workflows, navigate to the location or check into a meeting from the Salesforce context.
Does it use our existing Salesforce territories?
F1 Agent maintains a territory hierarchy that associates customers and users with territories and operating hours. During setup we map it to how your territories are organised today.