Get notified — push and email

When dispatch assigns, unassigns, or retimes you on a leg, or re-nudges you about an unacknowledged assignment, the platform tries to reach you two ways.

Steps

1. Register your device for push. See get the app and register your device — this is the prerequisite. No registered crew_device, no push.
2. Push is tried first. Every device you've registered gets a push notification with the trip/leg/role and a deep link straight to the assignment's acknowledge/decline screen. If you have the app on two devices, both get it.
3. A stale token is pruned automatically. If a device's push token is no longer valid (app uninstalled, token expired), it's dropped from your registered devices on the spot — you won't keep "succeeding" against a dead token.
4. Email is the fallback — not a duplicate. Alongside the push attempt, the same notification is durably queued as an email to the address on your account. It sends through the same outbox every operator email goes through, not a fire-and-forget send, so it's not silently lost if the mail provider is briefly down. If you have no email on file, that's recorded honestly as skipped — never faked as sent.
5. Nothing here is a compliance verdict. A notification is an operational receipt only — what changed, and a link to act on it — never a §135 compliance claim.

Being re-nudged

If you leave an assignment unacknowledged, a periodic scan can re-nudge you with another push/email reminder — see acknowledge or decline an assignment for what that looks like from your side and why acknowledging matters.