Scheduled Visits and Accounts: All your upcoming visits (for the day or for however far ahead data is synced) are stored on the device. This includes details like the account name, address, planned time/date, and any notes about the visit. You can open a visit offline and see all the info as if you were online. The account details (store information, contacts) associated with that visit are also cached offline. So if you need the store manager’s phone number or to check the address, it’s there.

Tasks and Surveys: Every task and survey assigned to your visits is downloaded beforehand. This means all the forms, questions, checklists, and instructions are available offline. You can complete surveys, enter data, and mark tasks as done without connectivity. For example, if a survey has a dropdown menu of options, those options are already loaded in the app. Even more complex question types like photo capture or signature blocks work offline because the app will save your input locally.

Reference Data: FieldKo might bring down additional reference data that’s linked to your tasks. For instance, if a task involves checking product stock, the relevant product catalog or list of SKUs might be stored offline. If you have a training document or planogram image attached to a task, that too can be available offline (assuming you synced while online). In short, anything that was part of your assignments is on your device after a sync.

Previously captured data: Any notes or photos you capture while offline are stored within the app as you take them. You can review them on your device. Additionally, if you had notes or photos from earlier (when you were online) attached to a visit, those should remain available for reference offline because they were downloaded as part of the visit record.

GPS and time-stamping: Your device’s GPS works offline (it doesn’t require internet to get satellites). FieldKo can record GPS coordinates for check-ins or photos offline just the same. It will tag the data and hold it until sync. The current date and time come from your device, so all timestamps (like check-in time, task completion times) are recorded accurately even offline.

Continue normal operations: You can open visits, check in, complete tasks, add notes, and check out just as you would online. There’s no special procedure for offline beyond knowing that data isn’t being sent to the server immediately. The app will save your inputs locally. For example, clicking Check In will timestamp your visit locally; the app knows to upload that later. Filling out a survey will store your answers on the device until sync. Essentially, operate as usual; FieldKo is built to handle it.

Indicators of offline: FieldKo might show a small icon (like a cloud with a slash or an “offline mode” banner) to remind you that you’re not connected. This is just informational. Also, if you try an action that strictly requires internet (like maybe pulling a real-time report or opening an external web link), it may prompt that you’re offline. But all primary visit functions won’t need such a prompt since they work offline.

Speed and performance: You might find the app actually faster offline for some operations, since it’s reading from local data. For instance, moving between tasks or saving a form happens instantly without waiting for network latency. This is a nice perk of offline mode. Just be mindful that this speed doesn’t mean it’s synced — it’s just local.

Capturing data offline: All types of data capture are available:

Offline edits and creation: If you update data, like editing an account detail or creating a new note, those are queued too. One thing to note: you generally cannot create new visits or accounts while offline (since scheduling a new visit usually requires saving to server). FieldKo’s offline design is mostly for executing your pre-planned visits. So, if an unplanned visit comes up and you’re offline, you might not be able to officially create it in the app until online. (However, you could use a workaround like noting it down and entering it later, or creating a “generic” visit note.) This mainly matters for unexpected changes – planned work is all doable offline.

Working through multiple visits: You can complete multiple visits in a row offline. Say you have 3 store visits back-to-back in a country town with no signal. You can do Visit 1 fully (check-in, tasks, check-out), then move on to Visit 2, etc. FieldKo will keep stacking the data for each visit. Each completed visit will sit in a queue waiting to sync. You might see a counter or notification like “3 visits pending upload” in the app, depending on design. But there’s no issue with doing a lot of work offline – the app can hold quite a bit before syncing. Just make sure to eventually connect and sync (the same day preferably) so that data isn’t delayed getting to the server.

No real-time updates: When you’re offline, the app isn’t receiving any new information. This means if your manager adds a new visit to your schedule or changes a task while you’re out of coverage, you will not see that change until you go online and sync. Likewise, if a colleague sends you a message through a FieldKo chatter feed or updates a store record that you didn’t download initially, you won’t get that until later. Essentially, your app is in a “snapshot” state of the last sync.

Manager visibility: FieldKo often allows managers to see where reps have checked in and the status of their tasks in near real-time. If you are offline, your manager cannot see your progress until you sync. For example, if they look at a dashboard at noon and you haven’t had connectivity all morning, it may appear as if you haven’t started your visits yet (even though you have). Once you go online and sync, all your check-ins and task updates will appear with their actual times. Just be aware that lack of connectivity can give a temporary impression of no activity – you might want to inform your team if you plan to be offline for long stretches, so they know the data will come later.

External links or online content: If any of your tasks include links to external content (perhaps a training video on YouTube, or a PDF manual stored online), those won’t open offline. You might click them and get an error or simply nothing happens. In such cases, note down to view that content later when you have internet, or see if it was supposed to be downloaded (maybe ask your admin if critical files can be made available offline in the future).

Maps and location services: The FieldKo app itself will show you the address of a location, but the actual map imagery or routing requires an internet connection (unless you have offline maps saved in your mapping app). So while offline, you won’t be able to load the map tile images in the app. If you tap “Navigate” while offline, apps like Google Maps can still open and show a route if you have pre-downloaded that map area or if GPS can guide you without new data. In dense areas, this might be a problem if you didn’t prepare. As a workaround, you can rely on the address text — you can still attempt to navigate by following road signs and the address, or reconnect to get the map. It’s wise to download offline maps in Google Maps (or similar) for your territory if you frequently have no signal.

Searching for un-synced info: Suppose you want to lookup a product or an account that wasn’t part of your downloaded assignments. Offline, the app can only search what it knows about. So if you type in the name of a store that wasn’t in your visit list (maybe you decide to do a surprise visit), FieldKo likely won’t find it because that record isn’t cached. Similarly, global search features are limited to your offline data. Plan ahead and sync any data you think you might need.

No new logins or password resets: If, for some reason, you got logged out or your session expired while offline, you will not be able to log back in until you have an internet connection (the app cannot authenticate you offline without a cached session). This is why we stress staying logged in if you know you’ll be offline. Also, if your password expires or you need to reset it, that must be done online.

Reporting and dashboards: FieldKo provides mobile access to reports and dashboards (since it’s Salesforce under the hood). These likely require an internet connection to query fresh data. If you go to a Reports section offline, you might either see nothing or just stale data from the last time you opened that report. Don’t rely on getting updated analytics offline. Inputting data (your visit results) is fine, but pulling analytics is mostly an online activity.

Error resolution requires online: If something goes wrong with a record (say a task won’t save due to a validation rule), you might not know until you sync. The app will usually allow you to enter anything offline, but the server might reject it upon sync if it violates a rule. In offline mode, you won’t receive that feedback. So an obscure limitation is that you could technically input something that later fails to sync (we’ll discuss what happens then below). It’s not really a limitation of using the app offline, but a limitation of not getting immediate server validation. The workaround is just to sync sooner rather than later so you can catch any issues. In practice, this is rare for field tasks because the forms are designed to be valid offline too.

Automatic sync: In many cases, FieldKo will detect a connection and start syncing automatically. For example, if you open the app after regaining signal, you might see it immediately uploading pending items. Some apps also periodically try in the background. If this doesn’t happen, you can manually initiate the sync. (Maybe tap a Sync button or pull-to-refresh on the home screen).

Data upload: The app will upload all your stored activities to Salesforce. This includes check-in/check-out times, task answers, survey responses, photos (these can take longer, given their size), notes, and any other updates you made. The time stamps and sequence will be preserved. So if you checked in at 10:00 AM offline, Salesforce will reflect a 10:00 AM check-in once synced, even if you only got online at 1:00 PM. In technical terms, the created timestamps might be later, but FieldKo likely has fields for “Actual Check-in Time” that you recorded. The important part: none of your work is lost, it just transfers now.

Data download: At the same time, FieldKo will fetch any new or updated information from the server. This could be new visits assigned to you, changes to tasks, updated product lists, or general app configuration updates. After a period offline, it’s wise to let the app sync fully so you catch up on anything missed. You might suddenly see a new visit appear for later in the day that wasn’t there before (if someone scheduled it while you were out). Or a task might update (e.g., manager extended a survey with a new question – your app will download that for future visits).

Progress indicator: During sync, you’ll likely see a status bar or spinner. Some apps break down the steps (like “Uploading data...”, then “Downloading updates...” etc.). If you have a lot of offline data (say dozens of photos), be patient. Larger data may take a few minutes on cellular; if possible, use Wi-Fi for big syncs (for speed and to save your data plan).

Confirmation: Once sync is done, you might get a notification or just see that the “Last synced” time is now current. It’s a good practice to review and make sure everything went through. Check that your visits you completed are marked completed in the app. Perhaps even go into one and ensure your answers are showing up (they should). If something is amiss (like a note you wrote isn’t visible), it could mean it failed to upload – though this is uncommon. Usually, if sync finishes without error, you’re all set.

Partial sync / intermittent connection: If you’re on a flaky connection, the app will try its best to sync. It may upload smaller items first (like text data) and do photos last. If the connection drops mid-sync, no need to panic: the app will resume or retry when it can. Your data won’t be corrupted; at worst, it just remains on device until it gets a chance to send. You can help by finding a more stable connection or waiting until you have better coverage to sync a big batch of data.

Manual retry: In case some items didn’t sync (for example, one photo failed due to size/time-out), FieldKo may show an alert or list of failed items. You can typically hit a Retry Sync option. The app will then attempt just the failed items. This granular handling ensures one hiccup doesn’t block all your other data. Usually though, if one item fails, everything else still goes through; you just need to re-send that one item.

Common causes of sync errors: The most common issue is a validation rule or required field that wasn’t satisfied. For example, maybe a survey had a mandatory question that you skipped. The app let you save offline, but when syncing, Salesforce rejected the record because that question was empty. Another cause could be a data type issue (e.g., you entered text in a numeric field due to no immediate validation offline). Conflicts (two people editing the same thing) are less likely for field data, but if a manager edited something on the record while you were offline, there could be a conflict.

How you’ll know: FieldKo will alert you if something failed. You might see a notification like “3 items failed to sync.” There could be an error icon next to the visit or task that had an issue. Tapping that might give more details. For example, “Task XYZ – Required field not filled” or “Visit ABC – sync conflict, data out of date.”

Resolving on your own: If the error message is clear (like missing data), the solution is usually in your hands. You can open the record in question while you’re now online, fill in the missing info or correct the erroneous data, and then attempt sync again. FieldKo will then send the updated data which should pass the server rules. Another scenario: if a conflict occurred, FieldKo might have taken the server’s changes and merged them. You may need to review the visit to see if all your info is intact or if you need to re-enter something. Modern apps often handle merging, so possibly no action is needed besides confirming.

When to involve an admin: If the error is technical or unclear (e.g., “Sync error code 500” or something about a server issue), or if your retries keep failing, it’s time to reach out for support. Your Salesforce/FieldKo administrator can check backend logs. FieldKo being on Salesforce means every attempted data upload likely left a trace (maybe an error log or failed record in Salesforce). Admins can often find what went wrong – maybe a new field was added that your app didn’t know about, etc. Provide them any error details you see. They might guide you to do something like reinstall the app (only after ensuring data is backed up) or they might fix a backend setting and ask you to retry sync.

Data safety: Importantly, as long as you don’t uninstall the app or log out, your offline data stays on the device until it successfully syncs. Even if there’s an error, the data isn’t deleted – it’s just in a pending state. So you can attempt fixes and re-sync. If you were to uninstall or clear app data before syncing, that data would be lost. So avoid drastic actions. 99% of sync issues can be resolved without losing info.

Partial success: You might notice that even if one task failed, other tasks from the same visit synced fine. So you’re only troubleshooting the part that failed, not the entire visit. FieldKo is capable of syncing at a granular level. Use this to your advantage by not redoing everything – just fix the piece that needs fixing.

Train users on offline usage: Make sure your field team understands how offline mode works and the importance of syncing. Provide them with a checklist (similar to the one above) to sync each morning and whenever possible. Emphasise not logging out while in the field. A little training goes a long way to prevent avoidable issues.

Monitor sync logs: FieldKo’s robust sync can be monitored on the backend. Salesforce might have records of last sync time per user or any sync errors. Keep an eye on these, especially for users who work offline frequently. For instance, if you see a user hasn’t synced in 3 days, you might want to remind them (or check if they’re having issues). If you see repeated sync errors in logs, be proactive in investigating and reaching out before the user even reports it. This proactive support can prevent data from getting stuck for too long.

Encourage frequent syncs: Culturally, encourage a practice of “always be syncing.” Perhaps set expectations that reps sync by lunchtime and at end of day. This ensures data flows steadily. It also means if an issue arises, it’s caught while the day’s context is fresh (the rep can remember and fix a missing answer the same day, rather than a week later).

Assist with device issues: Sometimes “offline problems” are actually device problems (like a phone’s GPS not working properly, or a device setting that prevents background sync). Be ready to troubleshoot basic device settings: location services should be on, battery saver modes can sometimes pause background sync, etc. Ensure users know to keep the FieldKo app updated to the latest version, as updates often improve offline sync efficiency.