Send BrandJet mention alerts to Slack: step-by-step screenshots
Follow the current BrandJet interface below. Each screenshot matches the numbered action directly beneath it.
Step 1: Open Settings and select Integrations.
Step 2: Locate Slack and switch it on to start workspace authorization.
Step 3: After Slack is connected, open Notifications.
Step 4: Enable only the alert types that have a clear Slack owner.
Step 5: Choose Every Hour, Once Daily, or Weekly Summary.
Step 6: Choose the sentiment threshold that should trigger review.
Send BrandJet mention alerts to the right Slack channel
Outcome: Connect BrandJet to Slack, choose which mention-related signals should trigger notifications, set their frequency and thresholds, route them to the right channels, and confirm delivery with a test notification.
Prerequisites: Access to the BrandJet workspace where notifications are configured, permission to connect the intended Slack workspace, and access to the Slack channels you plan to use.
The best setup is not the one that sends the most alerts. It is the one where every important alert reaches a person who knows what to do next.
1. Open the Slack integration in BrandJet
In BrandJet:
- Open Settings.
- Go to Integrations.
- Select Slack.
- Start the Slack connection flow.
This is the verified BrandJet route for connecting Slack. BrandJet's public integration documentation also describes the connection from Settings > Integrations > Slack. See BrandJet's Slack connection guide.
Do not configure alert logic before the Slack connection is working. Connection and notification policy are separate steps.
2. Authorize the correct Slack workspace
Continue into the Slack authorization flow and select the workspace that should receive BrandJet notifications.
Review the workspace carefully before approving the connection, especially if your organization uses separate Slack workspaces for internal teams, customers, or regional operations.
BrandJet's public documentation says the Slack integration can post to authorized channels and use the public channel list for channel selection. It also notes that private channels require the BrandJet bot to be explicitly added. Review the documented Slack behavior.
After authorization, return to BrandJet and confirm the integration is connected using the state shown in your workspace.
Authorize the workspace that owns the response workflow
Connect BrandJet to the workspace where the people responsible for the alerts already work. Do not choose a workspace merely because it has the broadest membership.
3. Choose the default Slack channel
Select the default Slack channel available in the verified BrandJet connection workflow and save the connection.
Treat this as a fallback destination, not necessarily the final destination for every alert.
For example, a general monitoring channel might be suitable as the default, while interested replies and crisis signals are routed separately later.
A simple channel structure could look like this:
| Signal | Example destination |
|---|---|
| General mention monitoring | #brand-monitoring |
| Interested replies | #sales-replies |
| Sentiment issues | #customer-signals |
| Crisis alerts | #crisis-alerts |
These channel names are examples. Use the channel structure that matches your team's actual ownership.
4. Decide which BrandJet alerts should reach Slack
The authenticated BrandJet notification workflow includes controls for:
- mention alerts
- interested-reply alerts
- sentiment alerts
- crisis alerts
Do not configure them as one undifferentiated feed.
Mention alerts
Use mention alerts when the team needs awareness of new monitored mentions.
If mention volume is high and most mentions do not require immediate action, Once Daily or Weekly Summary is usually more useful than an Every Hour interruption.
Use the cadence shown in the live BrandJet workspace and review it whenever mention volume changes.
Interested-reply alerts
Route interested replies to the team that can follow up.
For a lean B2B team, that will often be sales, growth, or another revenue owner.
Decision rule: If an interested-reply alert is enabled, a named person or team should be expected to act on it.
Sentiment alerts
Use sentiment alerts as a review signal.
A sentiment alert should prompt someone to inspect the underlying context before deciding whether a response or escalation is required. Do not treat a single sentiment signal as automatic proof of a customer issue or reputation incident.
Crisis alerts
Reserve crisis alerts for a route with a defined escalation owner.
Before enabling an urgent Slack path, decide:
- who receives the alert
- who validates the situation
- what the first action should be
- who takes over if the primary owner is unavailable
A crisis alert without an escalation process simply creates a louder notification.
5. Set the notification frequency
The live BrandJet notification menu provides:
- Every Hour
- Once Daily (Default)
- Weekly Summary
Alert-type toggles control whether New Mention, Interested Reply, Sentiment, and Crisis alerts are enabled.
Choose frequency based on urgency and actionability.
Use Every Hour for active monitoring
Every Hour fits enabled signals that need frequent review, such as interested replies or a crisis queue with a clear owner.
Use Once Daily for routine review
Once Daily is the default and suits a managed daily review of routine brand monitoring activity.
Use Weekly Summary for low-urgency awareness
Weekly Summary suits trend review when individual events do not require a same-day response.
If an alert type adds no value, turn off its individual toggle instead of looking for an Off option in the frequency menu.
Every Hour is for active review. Daily and weekly summaries are for lower-urgency awareness.
6. Tune alert thresholds
The authenticated workflow includes threshold controls. Use the exact threshold labels and available values shown in your BrandJet workspace.
Do not assume that maximum sensitivity is automatically safer. A threshold that generates too many irrelevant alerts can make the team stop paying attention.
Think about two risks:
| Setting problem | Operational effect |
|---|---|
| Too sensitive | Too many low-value alerts |
| Too restrictive | Important events may not surface |
| Balanced | Alerts are usually worth reviewing |
Start with the consequence of missing the signal.
If missing an event would have little impact, use a more selective threshold or a digest.
If missing the event could affect a qualified opportunity or an urgent reputation response, a more sensitive configuration may be justified.
Tune thresholds without hiding important mentions
Thresholds should help prioritize human review. They should not replace it.
For sentiment or crisis-related alerts, review the underlying mention or conversation before making a public response, customer decision, or escalation based solely on the alert.
7. Route each alert type to the right Slack channel
After deciding what should trigger, map alerts to the channels where the appropriate owners already work.
BrandJet's Slack documentation confirms that different notification events can be mapped to specific channels. See BrandJet's routing guidance.
A practical routing model is:
| BrandJet alert | Typical owner | Example channel | Expected action |
|---|---|---|---|
| Interested reply | Sales or revenue | #sales-replies |
Review and follow up |
| Mention | Marketing | #brand-monitoring |
Review or include in monitoring |
| Sentiment | Support or communications | #customer-signals |
Check context |
| Crisis | Escalation owner | #crisis-alerts |
Validate and escalate |
These are workflow examples, not BrandJet defaults.
Route by alert owner and urgency
Every high-attention channel should answer one question clearly:
Who owns the next action?
If the answer is unclear, either change the route or move the alert to Once Daily or Weekly Summary until ownership is defined.
8. Send a test notification
Use the verified test notification control in BrandJet after the connection, frequency, threshold, and routing settings are configured.
Then open Slack and confirm that the test message appears in the intended channel.
Check:
- the correct channel received it
- the BrandJet message is recognizable
- the information shown in the test is readable
- any available BrandJet link goes to the expected destination
BrandJet's public Slack documentation says notifications can include a link back to BrandJet for action. Review the integration documentation.
Do not assume that every live alert will contain exactly the same fields as the test notification. Document live message content only after verifying it in the real workflow.
9. Confirm the right person can actually see the alert
A message being delivered to Slack and an individual receiving a desktop or mobile notification are two different things.
First, confirm that the BrandJet message exists in the channel.
If it does, BrandJet successfully reached that destination. If a teammate still receives no Slack notification, review their Slack notification configuration.
Slack supports channel-specific notification preferences, mute states, and broader notification schedules. See Slack's channel notification settings and general notification settings.
This distinction prevents unnecessary reconnection attempts when the BrandJet message is already present.
FAQ
The test message does not appear in Slack
Check the setup in this order:
- confirm the Slack integration is connected
- confirm the intended channel is selected
- confirm the relevant alert-type toggle is enabled
- review its threshold
- check whether the frequency is Once Daily or Weekly Summary rather than Every Hour
- send the test notification again
If the destination is a private Slack channel, confirm that the BrandJet bot has been added as required by BrandJet's documented private-channel behavior.
The message is in Slack, but nobody gets a notification
This usually points to Slack notification behavior rather than failed BrandJet delivery.
Check:
- channel-specific notification preferences
- whether the channel is muted
- workspace notification settings
- device notification settings
- notification schedules
The team receives too many alerts
Reduce interruption before abandoning the monitoring workflow.
Try:
- moving routine mentions from Every Hour to Once Daily or Weekly Summary
- tightening the relevant threshold
- separating urgent and informational alert types
- routing only actionable signals to high-attention channels
Important alerts are being missed
Review the opposite side of the configuration:
- check whether the threshold is too restrictive
- confirm the correct alert type is enabled
- verify the destination channel
- check whether Once Daily or Weekly Summary delays visibility
- repeat the test after routing changes
Keep the Slack workflow useful after launch
Review the setup whenever alert volume or team ownership changes.
A compact recurring review is enough:
- Were any urgent signals missed?
- Which alerts repeatedly produced no useful action?
- Did anything go to the wrong channel?
- Does every alert reviewed Every Hour still have an owner?
- Does the test notification still reach the intended Slack destination?
The goal is not to move every BrandJet event into Slack. It is to shorten the path between an important signal and the person who can act on it.
Once the Slack route is working, you can connect it to the wider monitoring workflow through BrandJet integrations and BrandJet social listening. For the initial setup, start with one high-value alert, route it to one clearly owned channel, test it, and expand only after that first route is dependable.