Using AI in Setting up Notification Rules

Instead of building a notification rule step by step, you can describe what you want in plain language and let AI generate the rule configuration for you. This is the fastest way to set up alerts for publishing events, conversation activity, and channel changes in Statusbrew.

The AI rule builder is in Beta. It's a great starting point, but it can make mistakes. Always review the trigger type, data sources, and actions it is configured with before saving. Every field is editable after generation.

Who Can Do This?

The AI rule builder is available on Premium and above plans. Primary Owners, Owners, and Admins can create and manage Notification Rules.

How Does It Work?

When you open the Notification Rule builder, you'll see a Describe what you want to see field at the top of the form. Type a plain-language description of the rule you want and click Generate.

The AI reads your description and automatically configures:

• Rule name

• Trigger type

• Data sources (when you mention a specific network name)

• Action type (Slack Alerts, Microsoft Teams Alerts, Send notification, Send email, or Send email to external users)

Once generated, a confirmation banner appears: "We've configured this rule based on your request." All fields remain fully editable. Review everything before clicking Submit.

Available Trigger Types

Notification Rules support the following trigger types:

Engage

• Message replied

• Conversation snoozed

• Conversation closed

• Conversation re-opened

• Conversation assigned

• Conversation Added to Inbox

Publish

• Post created

• Post updated

• Post deleted

• Post approved

• Post step approved

• Post rejected

• Post recalled

• Post published

• Post failed

• Post Note

• Conversation Note

Channel

• Channel added

• Channel removed

• Channel re-authenticated

• Channel disconnected

• Channel disconnect warning

How To Write A Good Description?

You do not need to use technical terms or exact field names. Write the way you would explain it to a teammate.

Three things that make a description work well:

• The trigger: What event should fire the notification, a conversation being closed, a post failing, a channel disconnecting, etc.

• The profile or network: Mention the exact profile name as it appears in Statusbrew, or the network followed by "accounts" (for example, "Facebook accounts" or "Instagram accounts"), so AI can fill in data sources automatically

• The notification channel: Where you want to be notified, Slack, Microsoft Teams, or email to an internal or external user

The more specific you are, the better the result. A vague description like "notify me when something happens" will still produce a rule, but a specific one like "send a Slack alert when a post fails on my Facebook accounts" will produce exactly what you need.

Examples

Engage Triggers

• When a conversation is closed on my Instagram accounts, send a Slack alert to <slack channel> in <slack team name>

• When a conversation is re-opened on my Twitter accounts, send a Microsoft Teams alert to <microsoft team name>

• When a conversation is assigned on my Facebook accounts, send a notification to <user name>

• When a conversation is snoozed on my LinkedIn accounts, send an email to <user name>

Publish Triggers

• When a post is published on my Facebook accounts, send a Slack alert to <slack channel> in <slack team name>

• When a post fails on my Twitter accounts, send a Microsoft Teams alert to <microsoft team name>

• When a post is rejected on my LinkedIn accounts, send an email to <user name>

• When a post is created on my Instagram accounts, send an email to <email address>

Channel Triggers

• When a channel gets disconnected on my Instagram accounts, send a Microsoft Teams alert to <microsoft team name>

• When a channel is re-authenticated on my Facebook accounts, send a Slack alert to <slack channel> in <slack team name>

Before You Save

Once the AI generates your rule, we recommend reviewing and completing all fields before clicking Submit. In particular, cross-check the following:

• Data sources: Verify the correct profiles are selected. If you did not mention a specific network in your description, select the profiles manually.

• Trigger type: Confirm the trigger matches what you intended.

• Slack Alerts: Click the action to select the Slack team and channel.

• Microsoft Teams Alerts: Click the action to select the connector.

• Send notification: Select the recipient user or user group.

• Send email: Select the recipient user or user group.

• Send email to external users: Add the external email address.

• Additional options: If you want to receive notifications only during specific hours or days, configure this manually under Additional options after generating.

Data sources are always required before saving. If you don't mention a specific network or profile name in your description, data sources will be left blank. You must select them manually before clicking Submit.

FAQs

Can I regenerate a rule with a different description?

Yes. Clear the description field, type a new prompt, and click Generate again. The form will be updated with the new configuration.

Why is my data source blank after generating?

The AI only selects data sources when you explicitly mention a network name in your description. If you wrote "notify me when a post fails" without specifying a network, data sources will be left blank. Add the network name to your prompt (e.g., "on my Facebook accounts") and regenerate.

Can I edit the rule after the AI generates it?

Yes. Every field, like name, trigger type, data sources, actions, etc., is fully editable after generation. The AI output is a starting point, not a final configuration.

Is the AI rule builder available on all plans?

The AI rule builder for Notification Rules is available on Premium and above plans.