Every notification the platform sends goes through one dispatcher and lands in the email audit — full content, every recipient in its proper field, the reason it was sent, and a deep link back to the ticket or agreement that caused it.
Ticket updates, project updates, agreements, payroll remittances, and invites all leave through a single dispatcher that owns templating, tenant-branded sending, deliverability headers, unsubscribe footers, and suppression.
One audit row per message — inbound and outbound alike — with the body, the To/Cc/Bcc split, the sender, the direction, the tenant, the brand, and a machine-readable reason code you can filter on.
Redacting a message archives a rendered copy, a JSON dump, and every recoverable attachment before scrubbing the content — and refuses to scrub anything it could not first archive.
Searchable by direction, date range, sender, any recipient, subject, brand, and reason. Every accepted inbound message and every outbound send.
Outbound mail leaves from the customer-facing brand with a working reply-to, falling back to a platform-managed sender when a tenant has no config of its own.
Per-tenant email templates per notification kind, so system mail sounds like you and not like a vendor.
Bring your own relay, use per-customer inbound addresses, and thread replies back onto the original ticket automatically.
Per-tenant suppression lists, bounce handling, and blocked-sender rules that stop abusive inbound mail from opening tickets.
An immutable administrative audit log alongside message-level redaction with S3 archival, for the compliance requests that eventually arrive.
Modern ticketing with custom workflows, saved views, and a white-label client portal.
See HelpdeskScheduled external and internal vulnerability scanning, per-agent CVE findings, and identity verification on the service desk.
See SecurityMulti-tenant by design, with per-brand portals, senders, domains, and a per-tenant switch for every feature in the product.
See White LabelYes. Bodies are stored inline with a byte cap and attachments are offloaded to object storage, so a large message is fully recoverable without breaking the record.
Not through any supported path. Capture happens at the transport boundary, so any notification the platform sends is recorded by construction rather than by remembering to log it.
Indefinitely by default for compliance, with an optional retention window if your policy requires messages to age out.
Deploy your first agent in minutes. See the platform in action — book a walkthrough or kick the tires on a free trial.