FieldKo is designed to support a wide range of field execution use cases. In essence, any scenario where you have people in the field performing structured activities (visits, audits, service calls, merchandising, etc.) can be managed with FieldKo. Below we outline the core use cases and features that FieldKo supports, explaining how the platform addresses each scenario:
Retail Visit Planning and Execution
One of FieldKo’s primary use cases is retail visit management – ensuring that field representatives (including sales reps and merchandisers) visit retail locations on the right schedule and execute their tasks efficiently. FieldKo provides a visit planning module where managers or team leads can set up call cycles (visit plans) for each field rep. For example, a rep might be scheduled to visit a set of grocery stores every week or month. Using FieldKo’s Visit Calendar, planners can allocate specific stores (Accounts) to a rep’s route, define visit frequency, and even create recurring visits automatically (e.g. Visit 'Store A' every 2 weeks).
On the field user’s side, the FieldKo mobile app shows their list of assigned visits (appointments) for the day or week. The app provides mapping and routing assistance: reps can see pins for their stores on a map. FieldKo integrates with Google Maps for route optimisation, allowing the user to click an “Optimise Route” button which will sequence their stops in the most efficient order (based on shortest time or distance). They can optimise for different criteria (earliest closing store first, minimal travel distance, etc.), and FieldKo leverages Google’s powerful routing algorithms behind the scenes. This is extremely valuable for teams trying to minimise travel time and fuel costs.
When arriving at a store, the rep will “Check-In” to the visit on the mobile app. FieldKo uses the device’s GPS to validate the rep’s location against the store’s known coordinates. If the rep attempts to check in while not physically near the store, FieldKo can issue a geofence alert – a popup warning that “you seem to be far from the store” and asking for confirmation. This gentle nudge helps drive compliance (ensuring reps are actually at the correct location) without completely blocking them – they can still proceed if, say, GPS is slightly off, but the system records that exception. The geofencing works offline as well, since the app stores the lat/long of each store and can compute distance on the device. Managers can configure the threshold (e.g. warn if more than 500m away). This use case of location-verified check-ins is crucial for companies to trust field data – FieldKo automates it, whereas previously a manager might have to cross-check time sheets and location manually.
During the visit, FieldKo can automatically track the duration of the visit (time spent). The moment a rep checks in, the system logs a start time; when they check out (upon finishing), it logs the end time. These timestamps feed into FieldKo’s Attendance Tracking feature to calculate total time worked. FieldKo essentially produces an automated timesheet for each field rep, derived from their visit check-ins. Managers no longer need to rely on self-reported hours; they get a reliable account of who was where, when, and for how long – all captured implicitly as reps do their jobs.
Key benefits for visit execution
FieldKo ensures field staff are visiting the right locations at the right frequency, reduces travel inefficiencies with optimised routes, and verifies that visits happen as planned (via GPS check-ins). It replaces manual route planning (often done on spreadsheets or Google Maps manually) with a dynamic system that can adapt to changes (e.g., adding a new store into a rep’s cycle is as easy as creating a new visit record and it will appear in their app). FieldKo’s model supports both manager-driven scheduling and self-planning by reps – some organisations have a central team plan every visit, others allow reps to schedule their own visits. FieldKo is flexible enough to handle both approaches. For instance, a rep could create an ad-hoc visit in the app for a store they decide to drop into, and still complete their tasks – all data will sync back and count toward their performance.
Task Management and Compliance Surveys
At the heart of FieldKo’s functionality is the ability to define and assign tasks, surveys, and checklists for field reps to complete during their visits. This use case covers things like: merchandising audits, store compliance checks, promotional execution surveys, competitor observation forms, and any other structured questionnaire or task list that a field team needs to carry out in-store.
With FieldKo, managers or administrators use a web interface (within Salesforce) to configure these tasks and surveys. FieldKo provides a library of question types (yes/no picklists, numeric fields, text fields, photo upload, date pickers, signature capture, etc.) so you can tailor each survey to your needs. You might create a “Store Visit Checklist” that includes questions like “Is the promotional display set up? (Yes/No)”, “Enter the number of facings for Product X”, “Take a photo of the endcap display”, and “Manager’s signature”. In FieldKo’s survey builder, an admin can create these questions with just point-and-click (no code). Questions can be grouped into sections or scorecards, and you can even assign scores/weights if you want to calculate compliance scores automatically.
Once the surveys and tasks are defined, you attach them to Visits. FieldKo allows each visit record to have multiple tasks or surveys associated. For example, a given store visit could have a “Promotion Compliance Survey” and an “Order Collection Task” attached. When the field rep checks in to that visit on the mobile app, they will see all the tasks and surveys they need to complete for that store. They work through each item, filling out responses. All of this works offline – the app will save the responses locally if the device is offline, and then sync to Salesforce when back online, preserving timestamps and data integrity.
FieldKo’s approach to task management covers both prescriptive tasks (assigned by management) and self-initiated tasks. Some organisations are very prescriptive – they define exactly what each rep must do at each store. Others give reps more autonomy to decide what to do. FieldKo supports both: managers can push tasks out to users, but reps can also pull down generic tasks or initiate certain surveys on their own if needed. For example, a rep might have an optional “Out-of-Stock Report” survey they can run if they notice something, even if it wasn’t explicitly assigned. FieldKo’s security model ensures that each user only sees relevant surveys/tasks – e.g., tasks meant for the “Merchandising” team won’t be visible to “Sales” team if those roles are different, thanks to Salesforce sharing rules and permission sets in place.
A concrete use case: Promotional Compliance. Let’s say a company launches a new promotion that should be in 100 stores. Using FieldKo, the admin can create a Field Campaign that generates a task for each store to check the promotion setup (there’s even a concept called Field Campaigns in FieldKo where you target a set of accounts over a time range for a specific activity). The tasks get assigned to the reps responsible for those stores. Each rep, when visiting their store, completes the promotion checklist (possibly taking photos of the display). Managers at HQ can then monitor completion in real-time – FieldKo’s dashboards will show, say, 90 out of 100 stores have completed the task, with scores on each question. This ensures compliance with promotions without endless email chains.
Another common use case is Merchandising Audits and Surveys. FieldKo is often used by Consumer Goods companies to ensure their products are properly displayed and priced in retail. A survey might include checking if correct pricing labels are present, if the product planogram is followed, if there are any competitor promotions, etc. The rep records all of this in FieldKo. The data (perhaps a compliance percentage or noted issues) is immediately available for the Key Account Manager or management to see in Salesforce reports. FieldKo leverages Salesforce’s reporting engine so you can slice the data by region, by rep, by product line, etc., and identify where compliance is lacking. Without FieldKo, these audits might be done on paper or Excel and only compiled weeks later; FieldKo accelerates that feedback loop to real time.
In summary, FieldKo’s task and survey management use case ensures field compliance and execution standards are met. By guiding field reps with clear digital checklists and capturing their inputs on the spot, FieldKo helps organisations enforce standard operating procedures in every location. Everything is documented – if a store fails a check, it’s recorded; if a follow-up is needed, the data is there to trigger one (via a workflow or follow-up task). This not only improves compliance but also provides a wealth of data for continuous improvement (for example, you might discover via reports that a certain region consistently struggles with shelf compliance, and can then train or intervene accordingly).
Photo Capture and AI-Powered Visual Analysis
Photo capture is a crucial part of field execution in many industries (especially retail merchandising). FieldKo makes photo capture easy and valuable. Using the FieldKo mobile app, reps can snap photos as part of their survey responses or tasks – e.g., taking a photo of a store shelf, a promotional display, a competitor’s product, or even a storefront. All photos taken are automatically tagged to the right record in Salesforce (such as attached to the Visit or the specific Survey response) along with metadata like time, location, and any comments the rep added. This creates a visual audit trail for each visit. Managers can later review these images in Salesforce to verify how things looked in the field.
But FieldKo goes a step further by incorporating Artificial Intelligence (AI) for image recognition. This is an emerging, powerful use case: FieldKo can utilise Salesforce’s AI capabilities (like Einstein Vision or integrated OpenAI models) to automatically analyse the photos taken by field reps. For example, FieldKo can be configured to detect product placements or count items on a shelf from a photo. In a demo, the FieldKo team showed how the system could recognise promotional shelf tags in a supermarket photo. By training an AI model on what the company’s promo tags look like, FieldKo can scan a shelf image and tell if the correct tags are present and how many, etc. This sort of automation means reps don’t have to manually count facings or out-of-stocks – the AI can do it, saving time.
Another example: A fast-food franchise uses FieldKo for quality inspections. A field auditor takes photos of how food is refrigerated or how the restaurant kitchen is organised.
The practical workflow in FieldKo is: a rep completes their survey, including taking required photos. Once those photos sync to Salesforce, an AI service can run to analyse the image. The results (such as “5 facings of Product X detected” or “Promotional display found: YES”) can be fed back into FieldKo records. You could even set up Salesforce Flow automation such that if a photo analysis indicates a critical issue (e.g., new competitor promotion alert), it triggers an alert to a manager. FieldKo’s integration with Salesforce platform makes this kind of extensibility possible – the photo gets analysed and the outcome can start a workflow (Flow) for follow-up actions.
Even without advanced AI, just having photos organised is a big win. Previously, field teams often resorted to sending photos via messaging apps or email, which made it hard to relate them to specific visits or stores. FieldKo centralises photo evidence. Need to see what Store #123’s dairy fridge looked like on last Friday’s visit? It’s a couple clicks away in FieldKo’s records. Photos can also be included in reports – e.g., a manager can generate a Salesforce dashboard that shows before/after photos of a promotion across all stores, etc.
In summary, the photo capture use case in FieldKo covers both basic documentation and advanced AI analysis. The platform significantly reduces manual effort (no more separate camera uploads or manual counting in images) and improves insight. It helps ensure visual standards (like branding, planogram compliance) without managers physically traveling to each site – they can audit via photos, and even leverage AI to scale that oversight.
Automated Attendance and Time Tracking
Field teams often have the challenge of tracking their working hours and attendance in the field. Traditional methods might involve employees clocking in/out via a separate system or simply trusting them to report hours. FieldKo streamlines this through automated attendance tracking, utilising the data already being captured during visits.
Here’s how it works as a use case: Every field rep uses FieldKo to check in when they start a store visit and check out when done. These check-in/out events (with timestamps and GPS coordinates) essentially act as punch-in/punch-out times for their workday. FieldKo can automatically identify the first check-in of the day as the “start work” time and the last check-out of the day as the “end work” time. With that, the system computes the total hours worked that day without the rep needing to do anything extra. In effect, the rep is “on the clock” during their visits, and FieldKo knows when they started and stopped.
This addresses a major pain point: inaccurate or forgotten time entries. If a rep forgets to manually log their hours, FieldKo’s got it. If there was concern that someone might claim 8 hours while only doing a few short visits, FieldKo’s data provides accountability (since all visits are geo-tagged and timed). The result is essentially an automated timesheet for each field user. Managers and HR can get reports of hours worked per day/week, which could be used for payroll or just management insight.
Moreover, because FieldKo logs where the person checked in, companies get an extra layer of compliance: was the person at the correct location when they said they were working? FieldKo’s data can show if someone checked in at an unexpected location or if they have large gaps in the middle of the day. In the demo, one customer specifically requested this feature to eliminate a manual process where they were asking people to text in or call in their start/end times.
The attendance tracking runs silently in the background. There’s no extra button the rep has to press for clock-in; it’s all inferred. And importantly, it works offline too – the app will capture timestamps even if not connected, and sync later. FieldKo does allow some configuration: for instance, if a rep has no visits on a given day (maybe they were doing administrative work), there could be ways for them to log that, or a manager could enter a manual adjustment. But for normal field days, this feature dramatically reduces administrative overhead.
From a use case perspective, companies use this to ensure productivity and accountability. It’s not about micromanaging every minute, but rather having an accurate record and being able to identify exceptions. For example, a manager might review a report and see that one rep’s average workday duration is significantly lower than others – that could prompt a discussion or investigation (maybe their territory has fewer stores – or maybe they’re not fully utilising their day).
FieldKo’s attendance data can be rolled up into Salesforce dashboards or reports just like any other data in the system. You could have a dashboard showing total visits and total hours per rep for the week, or a compliance report showing the percentage of days reps checked in. Additionally, since FieldKo is on Salesforce, this data can integrate with HR systems or payroll if needed (via APIs or reports).
Time & attendance tracking is a core use case that FieldKo simplifies by piggy-backing on field activity data. It eliminates manual time sheets, improves accuracy, and gives management insight into field operations efficiency. One FieldKo client scaled to thousands of users and noted how seamless this process was compared to their old methods – the platform simply kept up as they grew, providing trustworthy data on everyone’s field hours.
Reporting and Analytics for Field Operations
Collecting all this field data is valuable only if it can be turned into insight and action. A major use case for FieldKo is to serve as the system of record for field performance, which can then feed robust reporting and analytics. Because FieldKo is built on Salesforce, all the data (visits, task results, photos, time stamps, etc.) is stored in standard or custom Salesforce objects. This means Salesforce’s native reporting tools can be used to analyze it.
For example, a Salesforce admin or report analyst can create reports on FieldKo objects just as they would for Opportunities or Cases. Users can use the Lightning Report Builder to drag-and-drop fields, add filters (e.g. show me all visits last month where compliance score < 80%), and create charts. Salesforce’s reporting is known to be user-friendly yet powerful, and FieldKo fully benefits from that. Many other field solutions require exporting data to Excel for analysis; with FieldKo, a manager can log into Salesforce and view a dashboard in real time.
Common analytics use cases include:
Field Team Performance Dashboards: e.g., a dashboard showing each merchandiser’s visits completed, average compliance score, total hours, and maybe sales uplift in their stores. This gives sales managers a quick view of who’s excelling or who might need help.
Store Compliance Reports: e.g., a report of all survey questions that were answered “No” (meaning a compliance failure) across all stores, to identify frequent problems. If “Planogram followed?” is “No” in 30% of visits for a certain product line, that’s actionable intelligence.
Photo Review Galleries: While not a standard “report,” some managers might use Salesforce list views or custom Lightning pages to review photos coming in from the field, perhaps filtering by date or by specific campaign.
Attendance and Coverage Reports: e.g., a report to ensure every planned visit was executed, or to see any stores that haven’t been visited as scheduled. Because FieldKo stores planned visits and actual visits, you can easily report on planned vs actual and find gaps.
Integration to BI Tools: FieldKo data can also flow into external BI systems. In fact, all data can be accessed with Power BI, and many FieldKo customers use a mix of Salesforce dashboards and tools like Power BI for analysis. This is possible via Salesforce connectors or by exporting data. FieldKo doesn’t lock your data; if your analytics team wants to join FieldKo data with, say, sales revenue data in a data warehouse, it’s straightforward through Salesforce’s APIs or reports.
One very powerful aspect is the ability to build automated workflows (Salesforce Flow) off of FieldKo data insights. For instance, you could set up an alert workflow such that if a critical survey question is answered negatively (like “Store missing promotional display”), Salesforce automatically creates a “Follow-up Task” for the account team or sends an email to a supervisor. FieldKo’s data can drive active operational responses.
In summary, the reporting use case for FieldKo turns the wealth of field execution data into actionable business intelligence. Stakeholders from team leads up to executives can get a clear picture of field execution effectiveness. Because it’s all on Salesforce, they have a single source of truth: no more merging spreadsheets from different regions or wondering if data is up to date. Everything captured by FieldKo is available in real time. This flexibility ensures that no matter your analytics preference, FieldKo can feed it.
The end result is better decisions – companies can correlate field activities with sales outcomes, identify best practices, and react faster to issues in the field.
Additional Use Cases and Flexibility
Beyond the core scenarios above, FieldKo’s versatility on the Salesforce platform allows it to support many additional use cases. Some examples:
Order Collection: FieldKo can be used by field sales reps to take product orders from stores during visits. This means a rep could not only do an audit but also create a new Order record (which could integrate back to an ERP) if the store wants to place a restock order. This bridges sales and execution in one app.
Field Marketing and Promotions: If a company runs field marketing events or sampling in stores, FieldKo can schedule those visits and capture event data (e.g., number of customers engaged, feedback collected). Essentially, any event-based activity in the field can be treated as a “Visit” with tasks to complete.
Service and Maintenance Checks: Although FieldKo is primarily positioned for merchandising and retail execution, it could be used for light field service scenarios (inspections, maintenance checklists) since it allows custom surveys and tasks. Because it’s built on Salesforce, it could even tie into Service Cloud or work orders if needed.
Training and Onboarding in the Field: Managers could assign surveys that are actually quizzes or checklists for reps to ensure they understand new procedures. For example, after a new product training, a rep might have a “Post-Training Quiz” to do in FieldKo on their next store visit, reinforcing their knowledge. This isn’t a primary use case, but shows the flexibility of having a mobile form/survey platform in the reps’ hands.
External Partner Collaboration: Use FieldKo’s Experience Cloud portal to let partners (like third-party brokers or distributors) log their own visits or view tasks. For instance, a distributor rep might do visits to stores that your direct team can’t cover; they could enter their visit results through FieldKo’s portal. This way, you capture a 360-degree view of field execution, even when some work is outsourced. Experience Cloud makes it possible to expose just the right data to these externals with Salesforce’s robust sharing settings.
Multi-Channel Data Integration: FieldKo can take data from IoT devices or other channels. This is forward-looking, but imagine fridge sensors at stores sending data to Salesforce (e.g., temperature logs). FieldKo could integrate that info so that when a rep visits, they see an alert “Fridge was out of temp range yesterday” and have a task to check it. Because FieldKo sits on Salesforce, it’s not limited to manual inputs – any data integrated into Salesforce can potentially be used to generate field tasks or insights.
In essence, FieldKo is a platform, not just a fixed-purpose app. Its core use cases revolve around field visits, tasks, data collection, and reporting. However, since it leverages Salesforce’s low-code customisation, customers often extend it to fit their unique processes.