Keep working with no signal and reach the dispatcher

Goal

Finish the job in a dead spot without losing the record of what happened, and get hold of the dispatch desk when the job needs a decision.

Prerequisites

• You are signed in on the phone you drive with.
• The trip was already open on your phone before the signal dropped.
• You have the dispatcher's phone number saved for the times when data is gone completely.

Steps

1. Watch the banner at the top of the screen. When it says you are offline, Today and Schedule show the trips encrypted on this device. Other sections still need a connection.
2. Statuses, critical-instruction acknowledgements, stop checkpoints, incidents, waiting actions, proof photos and receipts are saved securely and queued. Tap each action once. Chat messages and assignment responses are not queued. GPS uses its own oldest-first queue while location sharing remains active.
3. Note the real times as you go: when you arrived, when the passenger boarded, and when you finished.
4. Once you have signal, watch the queue banner change from Queued to Syncing and disappear after the server confirms the actions. Then select Refresh once.
5. If the app shows Needs attention, reopen that trip, compare its current state and contact dispatch before repeating anything.
6. Leave location sharing on if the app is still capturing positions. When the connection returns, queued GPS fixes replay automatically. Do not start a second sharing session.
7. You can capture one proof photo or receipt while offline. Keep the app installed and stay signed in until the queued upload is confirmed.
8. To reach the office about this job, open the trip and use Message dispatch. The thread stays attached to that trip, so the desk knows which job you mean.
9. To reach the passenger about the pickup itself, use Call passenger on the trip.
10. When there is no data at all and the job cannot wait, phone the dispatcher directly.

Expected result

The trip actions replay in order after the connection returns, their original stop and waiting times are preserved, proof and receipts upload once, and the queue does not claim success before the server confirms it.

Troubleshooting

• A saved action shows Needs attention: reopen the trip, check the server state and contact dispatch before applying the next step once. Do not tap repeatedly.
• A message failed to send: reconnect and check the job thread before sending again. A lost response does not prove non-delivery. If the outcome remains uncertain, contact dispatch.
• The trip list will not load: select Try again. If it still fails on a good connection, sign out and sign in again.
• The app shows old information: use Refresh on the trips list rather than trusting what was loaded before you lost signal.
• Location sharing stayed on but the map has a gap: keep the app open until the connection returns. Queued fixes replay automatically. If sharing itself paused or the browser stopped capturing positions, reopen the app and start sharing again. Positions that were never captured cannot be reconstructed.
• You cannot reach dispatch at all: phone the number the company gave you. Chat needs data, a call does not.