Geo-fenced check-ins ensure your field team is at the right location when they start a visit. FieldKo can use GPS to verify if a user is near the account’s location when checking in, and alert them if they are too far away.
This helps drive compliance by discouraging off-site check-ins. Below we explain how administrators set up geo-fencing (e.g. defining a 100 m radius around each store) and what the mobile app does when a user attempts to check in outside that range.
Configuring a Geo-Fence for Check-Ins (Admin)
Administrators can configure geo-fencing rules in FieldKo via the Salesforce desktop interface. Setup involves defining the allowed distance for check-ins and ensuring account locations are recorded. Follow these steps to set up geo-fenced check-ins:
Ensure Account Coordinates Are Set: Verify that each Account (store or site) in Salesforce has accurate latitude and longitude values. FieldKo uses these coordinates as the centre of the geo-fence. You can populate coordinates by enabling Salesforce’s address geocoding or by manually entering the latitude/longitude for each store.
Open FieldKo Settings: In Salesforce (desktop), navigate to the FieldKo administration settings or configuration page. (This may be under a custom FieldKo app or in Setup – consult your FieldKo admin guide for the exact location.)
Enable Geo-Fencing and Set a Radius: Locate the setting for Visit Check-In Geo-Fence or similar. Turn it On if it’s not already enabled. Then enter your desired distance threshold for check-ins. For example, you might set 100 metres as the allowed radius around each account location. Users will then need to be within 100 m of the store’s GPS location to check in without a warning. (Tip: Choose a radius that balances accuracy with practicality – e.g. 50–200 m – to account for GPS drift while still keeping check-ins local.)
Save the Configuration: Save or deploy the updated settings. The geo-fence rule is now active. FieldKo will apply this rule on the mobile app for all visits moving forward. No mobile app update is required beyond the users’ regular sync, since the rule is enforced via the existing app’s functionality.
Mobile App Behaviour for Geo-Fenced Check-Ins
Once geo-fencing is configured, the FieldKo mobile app will check the user’s location each time they attempt to Check In to a visit. Here’s what field users can expect:
Normal Check-In (Inside Radius): If the user’s device GPS shows they are within the allowed radius (e.g. within 100 m of the account), the check-in proceeds normally. They tap the Check In button, and the app records their check-in as usual. The user likely won’t even notice the geo-fence, because they’re where they should be.
Warning When Outside the Geo-Fence: If the user tries to check in and their GPS location is outside the allowed radius, FieldKo will prompt them with a warning before completing the check-in. A pop-up message will appear saying something along the lines of: “You seem to be far away from the store location. Please confirm if you want to check in.”. This gives the user a heads-up that they are not near the expected location. The distance calculation is done on the device using the stored coordinates and phone GPS, so this works even if the user is offline or has limited connectivity.
Override Option: The geo-fence alert is a soft warning – the user can decide how to respond. If they have a valid reason to proceed (or if your organisation permits overrides), they can confirm to continue with the check-in despite the warning. In FieldKo, tapping “Yes” or “Continue” on the prompt will override the warning and immediately check them in to the visit. Alternatively, the user can tap “Cancel” or simply not proceed, which means no check-in will be recorded. For example, a rep who sees the warning might choose to stop and drive closer to the site, then attempt to check in again once within the allowed area.
Enforcement and Logging: FieldKo’s geo-fence does not hard-block the check-in; it relies on user judgment. The override is there because GPS isn’t perfect – the user might actually be at the store but GPS shows them 120 m away. The system allows them to continue if needed. However, the event is still logged with the device’s actual location. Managers can later see that the check-in was done far from the account (because the GPS coordinates and distance can be recorded for that check-in). This way, there is accountability even when overrides happen. We recommend instructing your team to only override in legitimate cases (e.g. minor GPS errors or special scenarios), and to otherwise make sure they are on-site before checking in.
Offline Usage: The geo-fencing check works offline. The mobile app has the account’s GPS coordinates and can compute the distance on the device without internet. If a user is in a remote area with no data, they will still get the warning prompt if they attempt to check in too far from the target location. They can still choose to override or wait until they are in range. The next time the app syncs, it will upload the check-in data (including the fact that an override was used, if applicable).
By setting up geo-fenced check-ins, admins create a gentle guardrail for their field team. The mobile app’s warning serves as a reminder to be at the correct store, while still giving flexibility to proceed when needed. This feature helps improve data accuracy and field compliance without heavily intruding on the user’s workflow. Field users will quickly become accustomed to the prompt appearing only if they are out-of-bounds. Overall, configuring a geo-fence of an appropriate radius will significantly boost the integrity of check-in data, ensuring check-ins happen where they’re supposed to – at the actual account location.