Tone alerts
Set up Tone alerts so staff are told when a member sounds angry or frustrated, and understand Mood history on Enterprise
Tone alerts read the emotional tone of a member's messages in a ticket and, when the member sounds angry or frustrated, post a 🎭 Tone Alert card in your alerts channel, pinging a role if you pick one. Checking runs until a staff member replies, then stops. This page is for the admin who wants the team warned before a conversation goes wrong. The related Mood history feature, which records how a member's mood changed over a whole ticket, is covered at the end.
Tone alerts are available on Pro and Enterprise and need the Atlas switch at the top of AI assistant → Atlas plus an alerts or logs channel. Mood history (the Mood tab on the ticket page) is a separate Enterprise feature. Upgrade your plan
Setup
Open the card
Go to AI assistant → Atlas → Alert staff to upset members. It is in the Sort and flag new tickets section of the What Atlas does tab.
Switch it on
Turn on the switch on the Alert staff to upset members card.
Pick a role to ping
Choose the Role to ping, or leave it on No ping to post alerts without mentioning anyone.
Save
Click Save changes in the bar at the bottom of the page. Make sure an AI alerts channel or a logs channel is chosen under General → Where the bot posts.
Settings
| Setting | Values | Default | What it does |
|---|---|---|---|
| Alert staff to upset members (the card's switch) | On, Off | Off | Master switch for this feature |
| Role to ping | A role, or No ping | No ping | Mentioned on every alert. Without a role, the alert is posted without a ping |
Alerts post in the AI alerts channel under General → Where the bot posts; when it is not set, they go to your logs channel.
Servers that set up alerts per tone earlier keep them, and the picker shows Custom alerts (N). They keep working as they were until you pick a role, which replaces them with one ping for angry and frustrated members.
Tones
Atlas classifies each check into one of six tones. Angry and Frustrated raise an alert; the others are recorded only.
| Tone | Typical signs | Alert |
|---|---|---|
| Angry | Capital letters, profanity, threats | Yes |
| Frustrated | Repeated complaints, impatience | Yes |
| Upset | Disappointment, sadness | No |
| Confused | Uncertainty, repeated questions | No |
| Happy | Thanks, positive words | No |
| Neutral | Plain factual messages | No |
What happens
- A member sends a message in a ticket.
- Atlas reads the messages together: it checks after the member's third message, or about 30 seconds after the first, so a burst of messages is judged as one.
- The AI classifies the tone.
- If the member sounds angry or frustrated and Atlas is confident, a 🎭 Tone Alert card is posted in your alerts channel. It mentions the Role to ping when one is set and shows
AI detected Frustrated tone in ticket #ticket-0412, then Detected Tone, Confidence, User, and AI Analysis with the reasoning. Change its wording on the Messages page (Tone alert). - Once a staff member replies in the ticket, the member's later messages are no longer checked.
The member sees nothing. The card goes to the alerts channel only.
Worked example
A moderation team wants to know about angry and frustrated members right away. They pick @Senior Support as the Role to ping.
A member writes this is the THIRD time I've asked, then nobody answers here, then hello??. After the third message Atlas reads all three together, and @Senior Support is pinged with a Frustrated alert in the alerts channel.
Mood history (Enterprise)
On Enterprise, the AI assistant → Atlas → Mood history card, in the Help your staff section, records how the member's mood changed across the ticket. It is on by default. On Pro the card is shown locked with an Enterprise badge.
- The analysis runs automatically when a ticket is closed and needs at least 3 member messages.
- While AI usage on the Atlas page is set to Essentials only, mood history is paused: tickets that close are not read for mood. Tone alerts keep working.
- Open the ticket in the dashboard and choose the Mood tab to see how the member's mood changed from start to finish. A ticket that is still open shows
Mood shows up when the ticket closes; a ticket with too few member messages showsNot enough messages to read the mood. - Across all tickets, the Stats page sums this up under More stats → Customer mood.
- The history is stored on the ticket and follows your ticket retention policy.
Limits and gotchas
Alerts need an alerts or logs channel. Without one the analysis still runs but no alert is posted; choose one under General → Where the bot posts.
- Tone alerts only post a card; they do not change priority or escalate the ticket. Use Automatic priority for priority.
- Atlas does not check tickets from members on AI assistant → Atlas → Keep Atlas away from, or tickets opened from a panel button that turns Atlas off. No mood history is recorded for them either.
- Tone checks count toward the ticket member's AI assistant → Atlas → Limit per member when it is on.
Privacy
Message content is analysed only to classify tone and, on Enterprise, to build the mood history. Analysis of new member messages stops once staff reply. Data is not shared with third parties or used for anything else.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| No alerts at all | The card or the Atlas switch is off, or neither an AI alerts channel nor a logs channel is set | Check both switches, and choose a channel under General → Where the bot posts |
| Alerts post but nobody is pinged | Role to ping is No ping | Pick a role |
| A member seems upset but no alert came | Only angry and frustrated tones alert, Atlas was not confident, or staff had already replied | Nothing to fix; alerts are for clear cases before staff step in |
| No mood history on a ticket | The ticket is still open, has fewer than 3 member messages, or the owner's plan is not Enterprise | Wait for the close, or check the plan |
Common questions
Which plan do I need? Pro or Enterprise for Tone alerts. Mood history on the ticket page needs Enterprise.
Does the member see the alert? No. Alerts go to the alerts channel, which members should not be able to see.
Can I alert different roles for different tones? No. Pick one Role to ping for every alert. Servers that set up per-tone alerts earlier keep them until they pick a role.
Do I need a role? No. Without a role the alert is still posted in the alerts channel, just without a ping.
Why did the alerts stop mid-ticket? Checking stops once a staff member replies in the ticket. That is by design.
Can it escalate or change priority? No. It only posts an alert. Pair it with Automatic priority or Sorting for those actions.
Where is the mood history? Open the ticket in the dashboard and choose the Mood tab. It fills in after the ticket closes.
Join our Discord server for support
Was this page helpful?
Last updated on