For operations leaders and Salesforce admins
Run field operations by your rules, not the app's.
Territories, expense policies, travel modes, visit forms, work types, skills and inventory locations are all configured in F1 Agent, inside your own Salesforce org. When a policy changes, an admin changes a rule, and nobody waits for a release.
Built natively on Salesforce · by Cloud Ingenious, a Salesforce Summit Partner
In short
F1 Agent for operations and admin teams is the configuration layer of a Salesforce-native field sales and field service platform. Administrators set up territories and the territory hierarchy, operating hours, expense categories, limits, hard and soft limits and policies, travel modes and who can use them, user, role and profile-specific rules, visit forms and visit tasks, work types, skills and required products, inventory locations and units, service territories and maintenance processes. All of it is stored in the company's own Salesforce org, so field apps, consoles and reports follow the organisation's real operating model instead of a fixed template.
The admin's reality
Every field app works. Until your policy is different.
No two field organisations run the same way. One reimburses odometer kilometres, another the mapped route. One allows hotels by city tier, another by grade. One needs a retailer form with twenty questions, another needs a skills matrix for medical devices. Fixed apps make operations teams bend the business to fit the software.
Policy lives outside the system
The expense policy is a PDF. Managers enforce it from memory, inconsistently, one claim at a time. Exceptions are discovered at audit.
Every change is a ticket
A new travel allowance or an extra question on a visit form means a change request, a developer and a release cycle. The field waits weeks.
Two systems, two truths
Territories in Salesforce, a different copy in the field app. Users, roles and customers drift apart, and someone spends Fridays reconciling them.
What to look for
Five questions to ask any field platform before you buy.
Configurability is the difference between a tool that fits for a year and one that fits as you grow. These are the questions that separate the two.
1. Can rules differ by user, role and profile, with a sensible default?
Seniority, geography and job type change entitlements. F1 Agent applies travel modes and expense limits at user, role or profile level, with a default for everyone else.
2. Can policy block some things and only flag others?
Legitimate exceptions happen. Hard limits stop a claim above the threshold; soft limits let it through for approval with the manager notified.
3. Do your words become the app's words?
Your travel modes, your cancellation reasons, your visit forms with picklists and multi-select picklists, your units such as cartons or bags.
4. Is the configuration on the same records as your CRM?
Territories, users, accounts and assets should be one set of data. F1 Agent stores everything in your Salesforce org, so there is nothing to sync.
5. Can one platform hold both sales and service rules?
Beats and expense tiers on one side, work types, skills and inventory on the other. One admin, one setup, one place to look.
Send us your expense policy PDF.
We will show it back to you as F1 Agent rules: categories, city tiers, role limits, hard and soft limits and travel distance method, ready to test.
The configuration map
Everything an admin can shape, and who it changes the day for.
Structure
- Territories and territory hierarchy
- Operating hours
- Service territories
- User, role and profile-specific rules
Changes the day for: managers, dispatchers, every field user
Money and travel
- Expense categories
- Expense limits and buckets
- Hard and soft limits
- Expense policies by city tier, local or outstation
- Travel modes and travel-mode allocation
- Distance method: odometer, mapped or lower of two
Changes the day for: reps, managers, finance
Visits
- Visit forms with picklists and multi-select picklists
- Visit tasks: order, return, competitor analysis, shelf audit
- Cancellation and reschedule reasons
- Beat approval
- Object created from a visiting card scan
Changes the day for: reps, sales managers, brand teams
Service work
- Work Types
- Skills
- Required products per work type
- Case statuses driven by work orders
- Dispatch mode: recommend or auto
Changes the day for: service agents, dispatchers, technicians
Inventory
- Inventory locations: warehouse, van stock, customer location
- Units: pieces, cartons, bags and others
- Warehouse links for product requests
Changes the day for: warehouse teams, technicians
Maintenance and more
- Maintenance plans and recurring schedules
- Maintenance processes per asset type
- Other business-specific configurations
Changes the day for: service managers, customers
A day in the life
Four requests from the business. Four rule changes. No code.
Meet the Salesforce admin for a company running 300 sales reps and 60 service technicians on F1 Agent. Here is a normal Tuesday.
One setup, every experience
Configure once in Salesforce. Every app, console and report follows.
Your Salesforce org
F1 Agent configuration
Territories · policies · forms · work types · skills · inventory · plans
Rep mobile app
Travel modes, visit tasks, forms, expense limits
Technician app
Work types, required parts, van stock, units
Manager console
Territory coverage, approvals, exceptions
Dispatch
Skills, service territories, operating hours
Lumina AI
Recommendations on the same data and rules
Reports
Standard Salesforce reports and dashboards
Use cases
Same platform, very different operating models.
| Business | Problem | Situation | Configuration | Outcome |
|---|---|---|---|---|
| FMCG, national | Expense rules differ by grade and city | Policy enforced by managers from a PDF | City-tier categories, role limits, hard limits for food, soft for hotels | Claims follow policy automatically; managers see exceptions only |
| Distribution | Returns in cartons, orders in pieces | Field app forced one unit | Dynamic units, return order task, cancellation reasons | Clean stock and return data without conversions |
| Medical equipment service | Strict skills and recurring maintenance | Schedules tracked in spreadsheets | Skills per device family, work types with parts, maintenance plans | Certified technicians only, preventive visits generated on time |
See how configuration plays out in FMCG and consumer goods, distribution and medical equipment service.
Why F1 Agent
What each approach asks of your admin team.
| For operations and admin | Spreadsheets and WhatsApp | Field app outside Salesforce | Building it yourself in Salesforce | F1 Agent |
|---|---|---|---|---|
| Policy enforcement | By people, inconsistently | Within the vendor's options | Whatever you build | Tier, role and limit rules built in |
| Making a change | Send a new message | Vendor settings or a request | Developer and release cycle | Admin configuration |
| Data location | Phones and files | Vendor database, synced | Your org | Your org |
| Sales and service in one setup | No | Often two separate products | Two large builds | Yes, one platform |
| Trade-off | No cost, no control | Fast start, integration to maintain | Total control, long build, ongoing upkeep | Product roadmap plus your configuration |
Low-risk start
Configure for one team. Copy it for the rest.
F1 Agent is built by Cloud Ingenious, a Salesforce Summit Partner, so it respects how admins already work: your org, your users, your profiles and your reports.
Pilot one territory
Set up one region's rules, prove them in the field, then extend.
Your existing org
No separate database; F1 Agent works with your accounts, users and territories.
Start with defaults
Default rules for everyone, then add role and user overrides as you learn.
Phased modules
Go live with visits and attendance, add expenses, service and Lumina in phases.
Questions admins and operations heads ask.
What can an admin configure in F1 Agent?
Territories and territory hierarchy, operating hours, expense categories, limits, hard and soft limits and policies, travel modes and their allocation, user, role and profile-specific rules, visit forms, visit tasks, work types, skills, required products, inventory locations, units, service territories, maintenance processes and other business-specific settings.
Do we need developers to change rules?
Day-to-day changes such as expense limits, travel modes, visit forms, work types and territories are configuration, handled by an admin. Larger extensions to your Salesforce org can still be built the normal Salesforce way.
Can different roles have different expense limits?
Yes. Limits can be set for an individual user, a role, a profile or as a default for all applicable users, and can vary by city tier and by local or outstation travel. You can also give each user an expense bucket.
What is the difference between a hard and a soft limit?
A hard limit prevents the employee from submitting above the threshold. A soft limit lets the claim through, makes the exception visible and sends it through approval, with the manager notified.
How is travel distance reimbursed?
You choose the method: odometer distance, Google API-based mapped distance, or the lower of the two. Travel modes are configurable and can be allocated by user, role or profile, because the mode affects how reimbursement is calculated.
Can we build our own visit forms?
Yes. Custom visit forms support picklists, multi-select picklists and other configured questions, and can be assigned to reps as a visit task alongside orders, returns, competitor analysis and AI shelf audits.
Which Salesforce object does a visiting card scan create?
You decide. The backend can be configured to create a contact, a lead or another standard or custom object from the scanned card, depending on your process.
How are inventory locations and units set up?
Admins define warehouses, technician van stock and customer locations, link vans to warehouses for product requests, and set units of measure such as pieces, cartons or bags to match how you handle stock.
Does F1 Agent work with our existing Salesforce setup?
Yes. F1 Agent is built natively on Salesforce and runs in your existing org with your accounts, users, profiles and reports. F1 Agent actions can also appear on standard Lightning record pages.
Who helps us with the initial setup?
The F1 Agent team at Cloud Ingenious, a Salesforce Summit Partner, works with your admin to translate your territories, policies and service processes into configuration during onboarding, so your team owns it afterwards.