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.
14 days on any plan, no card needed to start. After the click: a three-field form and the workspace.
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.
Screen recording: the event feed with context attached, personal channel and quiet hour settings, an alert rule, and an unhandled event being escalated.
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.
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.
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.
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.
From a change in the ad account to a handled alert there are four steps, and three of them happen without a person.
A module notices a delivery stall, no leads, a cap exceeded or a review rejection.
Repeats collapse, the insignificant is not delivered, and the rest gets its context attached.
Every 5 minutes on the chosen channels, respecting quiet hours.
An operator answers with an action; anything unhandled is raised after 2 hours.
Ad accounts hand over their statistics through your own OAuth apps. The system puts them into one picture, agents look for what to change, and only what you approve gets changed.
Early access
We are opening access to agencies in turn. Leave a work email and we will write when your turn comes, then help you connect the first account.
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.
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.
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.
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.
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.
14 days on any plan, no card needed to start. After the click: a three-field form and the workspace.
