Schedule
Brand Guard runs when content does. It does not operate on a fixed clock; it responds to the publish flow and to direct questions.
How It Gets Triggered
The most common trigger is automatic: when Marketing Content, Marketing Social, or Marketing Email completes a draft and the operator initiates publishing, the publish flow calls Brand Guard synchronously before anything goes out. Brand Guard scores the draft and returns a verdict. The calling agent waits for that verdict before proceeding.
The second trigger is conversational: when you mention Brand Guard in the brand-guard channel, it responds to your question or review request directly.
The third trigger is on demand from the app: in the in-app Brand Guard workspace inside The Marketing Workspace, you can start a new audit yourself. Paste a draft, pick the brand, and Brand Guard runs the same check it runs in the publish flow and records the result in the history feed.
Timing
Brand Guard runs within the publish flow, so the draft waits while the audit completes. Most audits finish in under two minutes. Longer or more complex drafts, or those that require a deeper review pass, may take a few minutes more.
If you ask for a conversational review in the brand-guard channel, you will typically see a response within two to three minutes.
What Runs Automatically vs. What You Request
| Situation | How it runs |
|---|---|
| Publish flow (via Marketing Content, Marketing Social, or Marketing Email) | Automatic; Brand Guard is called by the publish step |
| Conversational review (you paste a draft in the brand-guard channel) | On request; you initiate it |
| On-demand audit (you start a new audit in the in-app workspace) | On request; you initiate it |
| Audit history lookup ("why did you block X?") | On request, in Slack or in the in-app workspace |
| Re-audit after edits | On request |
Availability
Brand Guard is available continuously. It has no maintenance window and no separate service to start or stop. If it does not respond, see Troubleshooting.