# Give field support a recovery path before the first lost connection

The operating handover should explain pending states, safe diagnostics and who can resolve work that never reached the server.

By Cobnex editorial. Published 2026-09-10. Updated 2026-09-11.

## Put the useful facts on the device

A support screen should expose the app version, last confirmed sync, pending count and a command reference for each blocked item. Use readable state descriptions alongside technical identifiers.

The worker should be able to distinguish an expired session from a conflicting report without opening developer tools. These labels also reduce the chance that support recommends a network fix for a business validation problem.

Provide a privacy-conscious diagnostic export if needed. It should exclude customer notes and photographs by default, with a separate controlled process when content is essential to investigation.

## Assign authority for difficult cases

Support can guide reconnection and collect identifiers. A job owner may need to decide between conflicting observations. Security or an authorised administrator may need to handle a revoked account with unsent work.

Document those boundaries and the expected response path. A technician at a site should not have to discover which team owns an unresolved command by repeating the same explanation to several people.

Use a synthetic handover exercise where a report has reached the server but its phone still says Waiting to send. The incoming team should recover the receipt without manually creating another report.

## Write down actions that destroy evidence

Clearing site storage, removing an account's local records or replacing a device can remove unsent work. The procedure should establish whether a recoverable copy exists before any of those actions.

Explain the supported backup or export path, if one exists, and who may use it. Do not suggest copying a browser profile or emailing customer photographs as an improvised default.

If recovery is impossible, record the affected report and its business consequence honestly. A deleted queue entry is not a completed task.

## Maintain the handover as the app changes

Include offline schema changes, supported browser changes and new conflict states in release notes for support. Rehearse the significant changes with a populated test device.

Review recurring cases after launch. If workers repeatedly leave the app before the required foreground transfer finishes, improve the screen and workflow rather than relying indefinitely on support reminders. Ownership includes reducing the conditions that create lost or ambiguous work.

## Sources

- [MDN: browser storage quotas and eviction](https://developer.mozilla.org/en-US/docs/Web/API/Storage_API/Storage_quotas_and_eviction_criteria)