SupportHubCX Platform Docs
v1.0.0 Public Support Open App

Delivery Diagnostics

Delivery Diagnostics unifies email delivery logs, queued notification evidence, webhook delivery status, failure reasons, retry counts, and related records.

Diagnostic Data

  • Email and notification delivery logs show direction, channel, status, address, subject, event, related record, response excerpt, retry count, and retry status.
  • Webhook deliveries show subscription, endpoint, event, HTTP status, response body, success state, replay count, and last replay time.
  • Inbound mailbox records show received webhook messages, normalized message IDs, dedupe hashes, processing attempts, related tickets/requesters, failure reasons, retries, and attachment metadata.
  • Filters support search, delivery type, channel, status, and simulated demo mail.

Demo Mail Center

/operations-center/demo-mail is the buyer-safe email evidence page. It shows simulated outbound emails, real SMTP test emails, inbound webhook emails, failed parses, retry evidence, ticket links, requester links, and mailbox links in one timeline.

BadgeMeaning
SimulatedDemo evidence was logged without contacting SMTP.
Queued / Sent / FailedSMTP delivery was attempted or queued by the configured mail transport.
ReceivedInbound webhook evidence was stored.
RetriedA retry or diagnostic replay was recorded.

Default Demo Mail Mode is log_only. Use log_and_send_test for capped proof emails to the current admin or whitelisted demo recipients. Use smtp_live only when you intentionally want normal transactional mail behavior.

Retry Actions

Users with retry deliveries can replay failed webhooks. Delivery logs without a full original transport payload are marked with retry metadata so support teams can see the retry attempt without pretending the message was re-sent. Simulated demo mail retry records a diagnostic retry only; it does not send a real SMTP message.

Google and Production Mail

Google Workspace or Gmail is acceptable for a few proof emails during a demo, but it is not a good dependency for repeated buyer demos or production transactional volume. Production deployments should use a transactional provider such as Postmark, Mailgun, Brevo, SendGrid, or Amazon SES, then monitor Delivery Diagnostics for failures and retries.

Operations Health

The Operations Center includes health cards for storage, recording storage size, scheduler heartbeat, mail configuration, failed jobs, webhook failures, inbound mailboxes, and queue worker signals.

Permissions

  • view delivery diagnostics allows viewing diagnostics.
  • retry deliveries allows retrying or replaying failed deliveries.
  • view operations health covers operations health visibility.