Telling the technician the schedule changed, without letting a failed message undo the dispatch.
Status at ebf7cf0: Partial — mobile push and inbox delivery are real; portal and WhatsApp transports are later phase.
A Sales dispatch or an OE commit assigns, changes or removes a technician from a Job Log.
Story. As a Technician, I want a mobile assignment alert after OE commits, so that I know my schedule changed.
Acceptance. A real mobile push is generated for a new or changed assignment after commit.
Story. As the system, I want each channel attempt recorded separately, so that one transport failure does not undo the assignment.
Acceptance. Portal, mobile and WhatsApp attempts have independent status and retry history.
Story. As the system, I want unchanged assignments suppressed and practical batching by technician, so that duplicate noise is avoided.
Acceptance. A repeated commit with no assignment change does not reannounce the job.
Dispatch writes portal, mobile and WhatsApp queue rows. Mobile push and inbox delivery are real and fire after commit. Portal and WhatsApp transports are explicitly later phase, and Reply Box is not wired to this backend fan-out. Customer WhatsApp selection is currently stored in the queued payload rather than delivered by the Sales backend.
The system never calls the WhatsApp Business API for ad-hoc shares. Use the native share sheet for those. Only reply-box-routed dispatch notifications use the WhatsApp API. See Cross-cutting requirements.
New to these terms? See the Glossary.