Help Center

Docs

Pre-send guardrails

The CRM-aware mistake-defense bundle that runs the moment you click Send.

What runs on Send

A ≤200 ms set of checks tied to your CRM state.

When you click Send, a batch of checks runs against your compose state and the recipient's CRM record before anything leaves the composer. What happens next depends on the check. A confirm-level finding opens a dialog: go back and fix it, or send anyway. A soft finding is a note that appears above the composer and never holds the message up.

  • Missing attachment — body mentions “see attached” but no attachments are queued.
  • Closed-lost deal — recipient's most recent deal is closed-lost. Confirm before re-engaging.
  • Stale contact — last contacted with this company was > 60 days ago. Soft hint to add a re-engagement opener.
  • Open ticket — contact has an open support ticket. Soft warning to tone-check the email.
  • Competitor mention — body mentions a competitor name from your org's configured list. Soft warning, never blocking.
Severity tiers
Confirm: a dialog you answer before the send proceeds. Soft: a note above the composer; the message goes out either way.
Guardrails never hold up your mail
If the checks themselves cannot run, your email sends. A mistake detector that can block your outbox when it is having a bad day is worse than no detector, so an unreachable or overloaded check is treated as nothing to report rather than as a reason to stop.

Configuration

Per-org and per-user controls.

Admins maintain the competitor watch-list at /admin/email/brand-tone. Once you answer the confirm dialog, that compose window stops asking; closing it and starting a new message runs every check again from scratch. Cancelling the dialog does not count as an answer, so the checks run again on your next Send.