Alerts
Alerts gathers in one list the notices sent by your monitoring tools, your backups and your organization's own systems. Your team reviews them by severity, opens the details of each one and turns the ones that need work into tickets.
- A channel with its own address for each system
- Critical, warning or info severity
- Turn an alert into a ticket for your client
The AgentticCRM Alerts screen, with fictitious data: the counters for unread, critical, warning, read and converted alerts; the list of the three unread alerts, one critical, one informational and one warning, each with its message, the channel it came in by, the time and the buttons to open it in the source system, create a ticket, mark it read or delete it; and the five channels, each with its default severity, the alerts it has received and the time of the last one, one of them paused.
Which systems can send you alerts
Any tool that can send a notice to a web address can connect. These are the most common cases.
-
Monitoring tools
Dashboards such as Grafana, which send a notice when a metric crosses a threshold or a rule fires.
-
Uptime checkers
Services that check your website or online store and send a notice when it stops responding or comes back.
-
Servers and containers
Tools such as Beszel or Watchtower, which report on your servers and on updates to your containers.
-
Backups and scheduled jobs
Jobs that run on their own, like a nightly backup, and report whether they finished or failed.
-
Deployments
Your release process reports when a new version goes out cleanly or stops halfway.
-
Your own systems
Any program your organization runs can send a notice, with named fields or as plain text.
How to connect a tool to Alerts
-
Create a channel
In Alerts, click New channel, name it after the system that will send the notices and pick its default severity.
-
Copy the channel address
AgentticCRM shows you a private address only once. Copy it: for security, it cannot be shown again.
-
Paste it into your tool
Add it to your tool's notification settings. The Alerts screen lists the fields it accepts and gives an example.
-
Check that they arrive
Each channel shows how many alerts it has received and when the last one arrived, so you know the system is still sending.
How each notice is read
Every tool names its data its own way. Alerts recognizes the most common names for the title, the message, the severity, the incident identifier and the link. If the notice arrives as plain text, its first line becomes the title.
Nothing is thrown away: the original notice is kept exactly as it arrived, and when you open an alert you see which field each detail came from. If the same incident arrives twice through the same channel with the same identifier, only one alert is kept.
Turn an alert into a ticket and tasks
When an alert needs work, click Create ticket and choose the affected client. The alert is marked as read, shows Has a ticket and takes you to it in one click.
From the ticket, your team talks with the client and turns the follow-up into tasks with an owner, a priority and a date. The alert keeps the original technical notice; the ticket and its tasks organize the response.
- 3severity levels: critical, warning and info
- 5details read from every notice: title, message, severity, identifier and link
- 120notices per minute at most on each channel, so a system failing in a loop cannot flood the list
- 30seconds between automatic refreshes of the list
A system that reports every minute does not flood your team with notifications: alerts are reviewed in their own list, with a count of the ones still unread.
Frequently asked questions
Does Alerts monitor my systems on its own?
No. Your monitoring tools detect the problem and send the notice; Alerts receives it, organizes it and puts it in front of your team.
What if a channel address leaks?
Replace the channel's key from Edit channel. The old address stops working immediately and you get a new one to paste into your tool.
Can I pause a channel?
Yes. A paused channel stops accepting notices until you resume it, and the alerts it already received stay in the list.
Who can create or change channels?
People with the permission to manage channels, which is separate from the permission to review alerts. That way, the people handling support work the list without changing where notices come in.
Can I delete alerts that are not useful?
Yes, one at a time or several at once. They leave the list, but the original notice is kept for audit and recovery.
Can the Assistant work with alerts?
Yes. Ask it to show you the alerts, mark one as read or turn one into a ticket. Before saving the change, it shows it to you for approval.
Alerts alongside other features
- Support ticketsEvery alert that needs work becomes a ticket for the affected client.
- Tasks and timeFrom that ticket, the follow-up is split into tasks with an owner and a date.
- Main dashboardUnread critical and warning alerts appear in your daily summary.
- AssistantAsk the Assistant, or your connected ChatGPT or Claude, to go through pending alerts or turn one into a ticket.
- Activity and auditCreating a channel, replacing its key, deleting alerts or turning them into tickets is all recorded.
See AgentticCRM working with your team's day-to-day
Ask for a demonstration and we will show you how these features fit the way you already work: your clients, your projects and the way you get paid.