Notifications
Marketing Email posts to its Slack channel when a draft is ready for review, when a compliance flag is raised, and when a send completes. Each notification is scoped to the draft it refers to.
Draft Ready for Review
When: The agent has finished writing the subject, preheader, and body, and the draft has passed the compliance gate without flags.
What it contains:
- The subject line and preheader
- The full email body (condensed to the first paragraph in the card; full text in the web app)
- The audience segment the draft is written for
- The "grounded on" note listing the brand knowledge sources the draft drew from
- Approval buttons: Approve, Edit, Redraft, Skip
Action required: Read the draft and choose an action. Nothing is sent until you approve.
Compliance Flag Raised
When: Marketing Brand Guard's review of the draft found an issue that must be resolved before the draft can be approved.
What it contains:
- The specific flag type (for example: a claim that cannot be verified, missing unsubscribe language, or a subject line that overpromises)
- A plain-English description of what triggered the flag
- The portion of the draft where the issue appears
Action required: Review the flag. If you want the agent to fix it, use the Redraft button and describe what to change. If you believe the flag is incorrect, contact your administrator to review the brand configuration.
Draft Blocked
When: The compliance gate encountered an error that prevented it from completing its review. The draft is held and not available for approval until the issue is cleared.
What it contains:
- A note that the draft is blocked pending a compliance review
- A prompt to contact your administrator if the block persists
Action required: Contact your administrator. Do not attempt to approve or send a blocked draft.
Send Confirmed
When: An approved draft has been dispatched through the email connection.
What it contains:
- The subject line that was sent
- The audience segment or recipient count
- The timestamp of the send
- A send reference number for your records
Action required: None. Keep the reference number if you need to follow up on delivery.
Frequency Cap Conflict
When: You requested a send, but queueing it would exceed the send frequency limit configured for that brand.
What it contains:
- The name of the frequency rule that was hit (for example: no more than two sends per week to this segment)
- The next available send window that falls within the limit
Action required: Either wait until the next available window, or contact your administrator to review the frequency cap for that brand.