Configure customer notification recipients

Send relevant job or POD communications to the approved list.

What this guide covers

Send relevant job or POD communications to the approved list. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Exact step-by-step process

1. Enter the primary customer email.
2. Add approved notification email addresses in the supported field.
3. Save.
4. Create or resend a delivery note and verify the recipient list.

Fields, choices and supported possibilities

This action uses the values already stored on the selected source record. Review that record before continuing.

Code-backed validations and workflow rules

• Notification recipients can merge customer email, customer notification list, receiver, driver, operations and explicit POD recipients depending on the event.
• Use valid, authorised addresses only.

Expected result and verification

• The source record, status/history and any downstream notification, provider, POD or finance record should agree after the action.

Security, audit and operational checks

• Use the exact record and least-privilege role before changing any state.
• Verify the saved record after every action; a browser message alone is not evidence that every downstream step completed.
• Use protected document and image routes rather than exposing server filesystem paths.
• Keep customer, driver, provider, financial and credential data within the authorised workflow.
• For provider, finance, employment, transport and compliance decisions, follow the organisation’s authorised professional process.

Related Courier guides