Compliance & QA

Keep every send compliant.

QA runs before generated drafts are marked ready. Blocking issues must be resolved. Warnings and advisories explain the risk so operators can decide what to change.

Blocking
  • False or unverifiable claims
  • Missing sender signature or opt-out language
  • Overly aggressive CTA that misrepresents the offer
  • Spam-like subject language or misleading framing
Warning
  • Tone mismatch with sender profile
  • CTA too strong or too weak for the current stage
  • Excessive use of first-person language
  • Subject line is too long or unclear
Advisory
  • Opening line similarity to previous stage
  • Suggested personalization token unused
  • Draft is too dense for a cold outbound context

Review trail

Important draft actions such as approve, reject, edit, and override are designed to be traceable with reviewer and timestamp context where available.

Buyer trust safeguards

Reply stop

When a prospect replies, the outbound path pauses so the lead is not pushed through the same automated sequence blindly.

Suppression checks

Unsubscribed, bounced, suppressed, paused, and replied leads are checked before future sends.

Claim control

Unsupported exact metrics, fake proof, and aggressive claims are treated as risky copy unless the user has provided defensible context.