When you click Send, a batch of checks runs against your compose state and the recipient's CRM record before anything leaves the composer. The same checks run on a reply you write in the reply box under a message, not only in the compose window. 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 never holds the message up: above the composer in the compose window, and a short notice when you send from the reply box.

• 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.
• Unanswered question (replies only): the message you are answering asked something your reply does not mention. The note quotes it, for example They asked: "Can you send the deck by Friday?", with up to three questions. It reads only the message as it is already stored in Laureo, never your mailbox, and it is a soft note: the reply still sends.

A new message needs a subject: in the compose window, Send stays off until you add one.

Admins maintain the competitor watch-list at /admin/email/brand-tone. Once you answer the confirm dialog, that compose window (or that reply) 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. The checks are free: none of them uses your AI credits.