Send Delivery: Notifying the Client

Triggering a formal delivery is done through the Deliver Job dialog, which you open by clicking the 'Deliver' action button on a job. This dialog is available to company staff with delivery management permissions — Owners, Admins, Project Managers, and Editors. The dialog combines three actions in one step: composing the delivery email, enabling the delivery link for the client, and optionally advancing the project status to Delivered. This means you do not need to touch multiple settings separately; everything happens in a single, intentional step.

The dialog's left column contains the message composition area. At the top is a Message Template dropdown that pre-loads any saved templates your organization has created. Selecting a template fills the message body automatically. The default template (marked with a '(default)' label in the dropdown) loads automatically when the dialog opens, so for a standard delivery you may need to do nothing more than read the pre-filled message and click Deliver. If you write a custom message, you can click 'Save as template' to store it for future use — enter a name in the inline field that appears, then click Save.

Below the message area are two checkboxes that control the delivery action. 'Notify via email' (checked by default) sends the composed message to the client's email address wrapped in the organization's branded email shell with a 'View Your Media' CTA button. When enabled, a live email preview renders in the dialog's right column — it refreshes 350ms after each keystroke so you can see exactly how the email will look before sending. The preview is faithful to the user-editable portion; the final send also includes a project-details block injected server-side. 'Mark the job as delivered' (also checked by default) advances the project status to Delivered. Unchecking this lets you enable the delivery link without formally closing the job — useful when you want to share a preview before final approval.

There are several edge cases the dialog handles transparently. If the client has no email address on file, the delivery goes through but a warning toast appears: 'Delivery link enabled — customer has no email on file, email skipped.' Similarly, if your organization has email notifications turned off at the org level, the notification is silently skipped and the toast reflects this. The dialog also supports template management: selecting a saved template shows a 'Delete template' link at the bottom of the template section, letting you prune outdated messages without leaving the flow. After clicking the Deliver button, the dialog closes and the job's status reflects the choices you made.

When a delivery is enabled, the client receives an email with a 'View Your Media' button that leads to the delivery page. From that page they can browse photos, download files, and interact with the approval section. Back in the job detail on the webapp, the DeliveryPanel's Client Approval Status badge updates in real time as the client takes action. On the iOS app, a push notification is sent to the agent (via the existing notification infrastructure) when the delivery is enabled; tapping the notification deep-links to the OrderDetailView's Deliverables tab, where they can view the approval status and all delivered media. The job status progression is Booked → Shooting → Editing → Delivered, and the Deliver Job dialog is the action that moves a job into the Delivered state.