Persistent local queue
Manual fields, qualification, notes, timestamps and pending images survive app restarts on the same signed-in device.
ExpoCollect treats unreliable connectivity as a normal exhibition condition, not an exceptional error. Supported capture work remains visibly pending on the phone until the server confirms it.
Manual fields, qualification, notes, timestamps and pending images survive app restarts on the same signed-in device.
Every local capture has a stable client identifier so a safe retry does not create another server lead.
Staff can distinguish pending, synchronised and conflicted work instead of relying on a generic success message.
A queued edit does not silently overwrite a newer server version; the conflict is surfaced for deliberate resolution.
Select the assigned exhibition before the floor gets busy and check that a first test record synchronises.
Continue adding leads and qualification details even when the device reports that it is offline.
Keep the same account and app installation in place until the queue reaches the server.
Use Sync Status for validation failures or version conflicts instead of re-entering the same visitor blindly.
Keep the capture flow available when crowded networks slow down at peak hours.
Work across changing venues without redesigning the capture process for each network.
See what has reached the server and what still needs action on a device.
Supported local capture includes manual contact fields, card photos awaiting upload, interests, priority, notes and the captured time.
No. Until synchronisation succeeds, the record exists only on the originating device and is labelled accordingly.
Do not sign out, uninstall ExpoCollect or clear its app data. Reconnect and use the sync controls first.
The backend uses the client-generated UUID as an idempotency key, while duplicate-candidate checks provide an additional review layer.