For sales managers and regional heads
See your field team live, and step in while the day can still be saved.
F1 Agent gives sales managers a live console of who is working, where, and what is happening in every visit. Lumina then points out who needs attention and sends the nudge for you, all inside Salesforce.
Built natively on Salesforce · by Cloud Ingenious, a Salesforce Summit Partner
In short
F1 Agent for sales managers is a Salesforce-native field sales management console with a mobile app for the team. It shows which reps are present, absent or disconnected, their live location and route, anyone who has stopped moving unexpectedly, and visit completion with cancellation reasons. Managers approve beats and expense claims, measure territory coverage and use reports, dashboards and leaderboards on Salesforce data. Lumina, the built-in AI, answers questions about team performance and bottlenecks and can send an email or notification to the right rep from the same conversation.
The manager's blind spot
You know the plan. You find out about the reality on Friday.
A manager knows a rep was supposed to visit eight outlets today. That number on its own says nothing about whether the day started, which eight were actually seen, how much of it was spent in traffic, or why three were skipped.
So the job becomes phone calls and WhatsApp check-ins, and the real picture arrives days later in a spreadsheet, when nothing can be done about it.
Questions most managers cannot answer at 11 AM
Who actually started work today?
Whose phone has gone silent, and why?
Who has been stuck in one place for an hour?
Were the skipped visits the customer's choice or the rep's?
Did any visit today produce an order?
Which important customers have not been seen in a month?
Which territory is quietly under-covered?
Whose expenses are drifting past policy?
The hidden cost: every unanswered question becomes a lost day. Ten incomplete meetings could be a performance problem or ten customer cancellations, and without reasons on record the two look identical.
What good field management looks like
Tracking is not managing. Four levels of field visibility.
Many teams buy GPS tracking and stop there. A dot on a map tells you where someone is standing, not whether the day is going well. Use this ladder to see where your team sits today.
Record
Attendance in an HR tool, orders on WhatsApp, a monthly sales report. You know what happened, weeks later.
Track
Live location on a map. You can see where reps are, but not which customer they are with or what came of it.
Understand
Location joined to customer, visit, territory and outcome. Check-ins, tasks, cancellation reasons and orders explain the day.
Intervene
The system flags stagnation, silence and slipping coverage while it is happening, and AI recommends and sends the intervention.
Measure outcomes, not visit counts
A rep with six visits and three solid orders beats one with ten empty visits. Visit tasks and orders make that difference visible.
Insist on reasons
Missed, cancelled by customer and cancelled by salesperson are different management problems. Your system should never let them blur.
Shorten insight to action
If spotting a problem and messaging the rep happen in two different tools, half the problems never get a message.
Which level is your team at today?
In a 30 minute field visibility review we map your current reporting against the four levels and show what Level 4 would look like for one of your regions.
A day in the life
A regional sales manager's day, run from one console.
Meet the manager of a 24-rep team across Delhi NCR North. Same team, same targets. Very different day.
Morning
Is the day starting?
09:00 to 10:30
09:15 · Attendance at a glance
Today's Overview shows 19 present, 3 absent, 2 disconnected. Punch-in time, assigned meetings and travel mode are on each rep's row.
09:20 · Bring disconnected reps back
One rep has location services off, another has no internet. The console shows the reason; one tap sends an alert asking them to go live again.
09:40 · Approve next week's beats
Two reps submitted multi-day beat plans for approval. The manager checks the customer mix against territory and approves one, sends one back.
10:10 · Coverage check
Territory reports show which high-priority customers in each territory have not been visited recently, and which rep owns them.
Midday
Is the plan holding?
11:00 to 15:00
11:42 · Stagnation alert
A rep has not moved for 52 minutes and the next visit is overdue. A quick call: the bike has a flat tyre. The manager moves two visits to a nearby colleague while it still matters.
12:30 · Visits with reasons
71 of 168 visits done. Of the 9 cancellations, 6 were by customers. One rep has 3 "cancelled by salesperson", which is worth a conversation.
13:15 · Ask Lumina
"Who is behind on visits today and why?" Lumina names two reps in Rohini, explains the pattern and drafts a notification. The manager sends it from the same chat.
14:30 · Route check
The route travelled by each rep is visible against planned customer locations, so a long detour is a question asked today, not a mystery at month end.
Evening
What did today produce?
17:00 to 18:30
17:10 · Expense approvals
Claims within policy flow through. Three crossed a soft limit and arrive flagged. The manager approves two and asks a question on the third; the rep sees the comment in the app.
17:40 · Outcomes, not just activity
Orders, return orders, shelf audit results and competitor notes from today's visits sit on Salesforce records, ready for the dashboard.
18:00 · Leaderboard
Reps see their own dashboard and rank in the app, so the manager's review starts from shared numbers rather than an argument about them.
18:20 · Plan tomorrow
Assign a beat to the colleague who covered today's gap, and ask Lumina to flag any territory that has dropped below its visit frequency this week.
Lumina Manager Action Planner
AI that does not stop at "Representative X has a problem."
Ask Lumina about performance, bottlenecks or who needs attention. It explains why, recommends what to do, and sends the email or notification to the right person from the same conversation.
"Which reps need attention this week?"
Lumina scans visits, completion, cancellations and orders across the team.
"Ankit's completion is 54%."
Most misses are salesperson cancellations on Thursday afternoons in one territory.
"Rebalance the Thursday beat."
Lumina suggests moving four outlets and checking in with the rep.
"Notify Ankit."
Notification sent with the context. The conversation and the action happen in one place.
What managers get
Control in the moment, clarity over the month.
Live team control
What it is: the Today's Overview console with present, absent and disconnected status, live location, route travelled and stagnation detection.
Why it matters: problems surface while they are happening, and the console can alert a disconnected rep to go live again. It works as a control layer, not a passive dashboard.
Outcome: fewer lost afternoons, and help that reaches reps on the same day.
Neha R.
Punched in 09:04 · 5 of 7 visits · 31 km
Rahul M.
Stagnant 52 min · Rohini Sec 7
Priya S.
Location services off since 11:05
Visits this week · Delhi NCR North
Plans, coverage and the reasons behind them
What it is: beat approval, territory hierarchy and coverage, visit completion and mandatory reasons for every cancellation or reschedule, with full visit history on each customer.
Why it matters: you govern the plan before it runs, and you can tell a customer-side problem from a performance problem after it does.
Outcome: fair reviews, and no important customer slipping through a territory.
Expense control without the chase
What it is: expense policies by category, city tier, local or outstation, with limits per user, role or profile. Hard limits block over-claims; soft limits let exceptions through for your review. Travel is calculated by odometer, mapped distance or the lower of the two.
Why it matters: you only look at the exceptions, and the comment thread with the rep stays inside the app.
Outcome: approvals in minutes, and spend that follows policy.
Hotel · Tier 1 · Outstation
₹4,800
Soft limit ₹4,000 · needs your approval
Travel · own vehicle
62 km
Odometer 78 km · mapped 62 km · lower reimbursed
Food · Local
₹1,240
Within policy · bill read by AI
Orders per productive visit, this month
Reports on Salesforce data you trust
What it is: reports and dashboards for rep performance, attendance, visits, expenses and field execution, plus a leaderboard reps see on their phones.
Why it matters: every visit, order and claim already sits on Salesforce records, so there is no export, cleanup or second version of the truth.
Outcome: reviews about outcomes, built on numbers both sides already see.
Use cases
Where managers feel the difference first.
| Scenario | Problem | Situation | With F1 Agent | Outcome |
|---|---|---|---|---|
| FMCG outlet coverage | Key outlets go unvisited for weeks | 200 reps, beats unchanged for a year | Territory coverage reports, beat approval and AI recommended beats | 40% more outlets covered with the same team |
| Distribution team performance | High visit counts, flat orders | Reps judged on visits logged | Visit tasks and orders per visit on the dashboard; Lumina flags low conversion | Coaching aimed at the right reps |
| Expense discipline | Travel claims well above mapped routes | Kilometres self-declared at month end | Odometer scan plus mapped distance, lower of two reimbursed; soft limits for exceptions | 18% lower travel reimbursement in a quarter |
For FMCG and consumer goods managers the focus is outlet coverage and merchandising execution; for distribution managers it is dealer coverage, order conversion and expense control across wide territories.
Why F1 Agent
What each option gives a manager.
| For the manager | Spreadsheets and WhatsApp | GPS tracker or field app outside Salesforce | Custom build in Salesforce | F1 Agent |
|---|---|---|---|---|
| Live status of the team | Phone calls | Location, often without visit context | Needs mobile tracking build | Present, absent, disconnected, stagnation, route |
| Why visits were missed | Rep's explanation | Varies by tool | Possible with custom fields | Mandatory reasons for cancel and reschedule |
| Outcomes per visit | Collated by hand | Synced to CRM, sometimes delayed | Yes, after build | Orders, returns, audits and forms on Salesforce records |
| AI that acts | No | Analytics, rarely action | Significant AI project | Lumina finds the issue and notifies the rep |
| Expense governance | Manual checks | Separate expense tool | Complex policy engine to build | Tier, role and limit rules with hard and soft limits |
| Trade-off | Free, but blind | Fast start, a second system to reconcile | Full control, long build and upkeep | Configured product on your org; follows your Salesforce setup |
"We used to find out on Friday what went wrong on Monday. Now I see the whole team live, and Lumina tells me who needs help before the day is over."
Low-risk start
Start with one region and compare.
Built by Cloud Ingenious, a Salesforce Summit Partner, F1 Agent runs on the Salesforce org you already have.
Pilot one team
Run one region or territory on F1 Agent and measure it against the rest.
Your rules, configured
Territory hierarchy, beat approvals and expense limits set to your policy.
No new database
Your existing Salesforce reports and dashboards keep working with the new data.
Phased rollout
Add regions and Lumina once the first team is running well.
Questions sales leaders ask.
What does the manager console show in real time?
Today's Overview shows each rep as present, absent or disconnected, their live location and route travelled, reps who have been stagnant for an unusual period, and progress on scheduled visits. You can send an alert to a disconnected rep from the console.
What does "disconnected" mean?
F1 Agent is not receiving live location from that rep, usually because internet is unavailable or location services are switched off. The console shows the relevant reason so you can ask the rep to fix it.
How does stagnation detection work?
When a rep stays at one location for an unusual period, F1 Agent surfaces it to the manager. It could be a long meeting, a vehicle problem or a customer-side delay; the point is that you can call while it still matters, not discover it at the end of the day.
Can I approve beats before reps follow them?
Yes. Single-day and multi-day beats can go through an approval process, so a rep's proposed coverage plan for the coming week reaches you before it becomes final.
How do I tell a performance problem from customer cancellations?
Every cancellation or reschedule can require a reason, such as missed, cancelled by customer or cancelled by salesperson. Reports split visits by reason, so the two situations no longer look identical.
What can I ask Lumina, and what can it do?
You can ask about field-agent performance, operational bottlenecks, users who need attention and execution issues. When you identify a problem, Lumina can send an email or notification to the relevant rep from the same interaction.
How are expense exceptions handled?
Hard limits stop a rep from submitting above the threshold. Soft limits allow the claim but flag it for approval and notify you. You can request changes with a comment that the rep sees and answers in the mobile app.
Can I measure coverage by territory?
Yes. Customers, users and beats are linked to a territory hierarchy, so you can see which important customers in each territory are being covered, how often, by whom, and which have not been visited recently.
Will my existing Salesforce reports still work?
Yes. F1 Agent is built natively on Salesforce, so visits, orders, attendance and expenses are Salesforce data. Your team can report on them with the same reports and dashboards they already use, alongside F1 Agent's own.
Will reps see this as surveillance?
The app gives reps a lot back: a planned beat, optimized routes, a Lumina brief before each visit, automatic travel expenses and their own dashboard and leaderboard. Reasons on cancellations also protect reps from being blamed for customer-side problems. Most teams find adoption follows when the app saves reps time.