Configure email delivery callbacks

1. An owner or admin opens Delivery callbacks and copies the displayed Callback URL. Use the supplied public HTTPS Desk address; ask the preview operator if a usable callback address is not available.
2. In the business Resend account, create a webhook for that URL. Select the seven event types listed in the Desk card: email.sent, email.delivered, email.delivery_delayed, email.bounced, email.complained, email.failed and email.suppressed.
3. Copy that webhook’s signing secret into Webhook signing secret and save. The field clears and the secret is never displayed again. Configured means the key is stored; it does not verify arrival or activate sending.
4. On an issued quotation, use Email status and Delivery events, then Refresh email status. Inspect both the provider event time and the time Desk recorded it. Later arrival can describe an earlier event.
5. When rotating the provider key, use Replace webhook secret. Old-key callbacks are refused afterward. Disconnect webhook secret removes the stored key while retaining recorded evidence. Reload settings if another manager changed them first.

Delivered to mail server means that server accepted the message, not that the customer read or accepted the quotation. Bounces, complaints and delays stay separate. No events does not prove failure. Staff can inspect the callback URL, guidance and saved status, but cannot change the signing key.

If a save result is uncertain, retry unchanged details to recover the receipt. This does not restore an older secret over a later change. Do not paste the secret into a support conversation; share the visible configuration status and event reference instead.