--- title: "Alerts: with context, on the right channel, and without noise" description: "Alerts name the platform, account, period and amount: delivered every 5 minutes, escalated after 2 hours, 4 channels, quiet hours." canonical: https://adsbeast.pro/features/en/alerts language: en section: features product_route: https://adsbeast.pro/inbox translations: - ru: https://adsbeast.pro/features/ru/alerts - uk: https://adsbeast.pro/features/uk/alerts - sk: https://adsbeast.pro/features/sk/alerts - es: https://adsbeast.pro/features/es/alerts - he: https://adsbeast.pro/features/he/alerts - ar: https://adsbeast.pro/features/ar/alerts --- # Alerts: with context, on the right channel, and without noise A notification without context is useless, and a stream of notifications is harmful: people stop reading them. Every alert names the platform, the account, the period and the amount in dollars, passes a relevance check, and goes out on the channel its recipient chose. Anything nobody handles is raised after 2 hours. ## How notifications work - **Channels**: Email, Slack, Telegram, a browser notification - 4 to choose from - **Delivery**: The queue is checked every 5 minutes - **Escalation**: An unhandled alert is raised after 2 hours - **Context**: Platform, account, client, period, amount in dollars - in every message - **Relevance**: A gate cuts out repeats and events you cannot answer with an action - **Quiet hours**: Personal settings by category and by time of day An alert you cannot answer with an action is noise. So every one carries a button or a jump into the section where the problem gets solved. ## What the event feed does ### The context lives in the message itself A notification used to be able to say "budget exceeded". Now it names the client, the platform, the account, the period and the amount in dollars. An operator knows what it is about without opening the system, and decides whether it needs opening now. - The client, platform and account in every message - The period and the amount in dollars - A link into the section where the problem gets solved ### A relevance gate against the flood Once the bell shows thousands unread, people stop opening it. Events go through a check: repeats collapse into one, the insignificant is not delivered, and anything you cannot answer with an action never becomes an alert at all. - Repeating events collapsed into one - Events with no possible action filtered out - Personal category and channel settings ### Escalating what nobody picked up An alert nobody has handled in 2 hours is raised up the team. This covers the events where delay costs money: a delivery stall, no leads, a cap exceeded. - The importance of an unhandled alert raised - A notification to whoever owns that client - A history: when it arrived, who handled it, what they did ### Rules: on what condition to call a person Beyond the built-in alerts, an operator writes their own: on what condition, for which client, on which channel. A rule can be run against a past period before you switch it on. - Your own alert rules by client and platform - A rule tested against historical data - Separate channel settings for each rule ## The path of a single event From a change in the ad account to a handled alert there are four steps, and three of them happen without a person. 1. **The event** - A module notices a delivery stall, no leads, a cap exceeded or a review rejection. 2. **The relevance check** - Repeats collapse, the insignificant is not delivered, and the rest gets its context attached. 3. **Delivery** - Every 5 minutes on the chosen channels, respecting quiet hours. 4. **Handling** - An operator answers with an action; anything unhandled is raised after 2 hours. ## Figures from the code - 5 min - between notification deliveries - 2 h - before an unhandled alert is raised - 4 - delivery channels - 2 h - between campaign delivery checks ## What the event feed does not do - It does not send notifications you cannot answer with an action. - It does not wake you at night for categories the recipient put inside quiet hours. - It does not replace approvals: an alert tells you, and the action is confirmed separately. - It does not repeat the same event over and over - repeats collapse into one. ## Questions and answers ### Can I get alerts in Telegram? Yes, it is one of the 4 channels alongside email, Slack and a browser notification. Telegram is also where you can confirm or reject a waiting action. ### What do I do when there are too many notifications? Set the categories and channels to suit you and switch on quiet hours. On top of that, the relevance gate collapses repeats and does not deliver events you cannot answer with an action. ### What happens to an alert nobody handled? After 2 hours its importance is raised and it goes to whoever owns that client. The history shows when it arrived, who handled it and what they did. ### Can I write my own alert conditions? Yes, in the rules section: condition, client, platform, delivery channel. You can run a rule against a past period and see how many times it would have fired before switching it on. ## Connect an account and get a first alert with the platform, period and amount in it The first 14 days are free on any plan and you do not need a card to start. Channels and quiet hours are set by each person on the team. - Start free: https://adsbeast.pro/signup?lang=en - Pricing: https://adsbeast.pro/pricing?lang=en ## See also - [Today: what is happening right now and what needs a decision](https://adsbeast.pro/features/en/dashboard): One screen for every agency account: spend by platform in one currency, refreshed every 15 minutes, what is on fire and what needs a decision. - [Budget guard: it will not let you blow the cap or buy junk traffic](https://adsbeast.pro/features/en/budget-guard): Monthly caps and pacing across every platform: checked every 2 hours, a placement guard every hour, overspend stopped through an approval. - [Assistant: a chat about your ad accounts, not generic advice from the internet](https://adsbeast.pro/features/en/assistant): The assistant answers from your ad account data, works in app and in Telegram, understands voice, and sends money-moving actions to the approval queue. - [Agents and automation: the system works while you sleep, and it does not spend](https://adsbeast.pro/features/en/automation-agents): Background modules watch campaigns on a schedule, rules say "if this happens, do that", and flows reach outside systems. Money still goes through an approval.