Notifications#
One single mechanism tells you about everything that needs your attention: a mention, an urgent lead, a post that did not go out, an engine that stopped. Every notification leaves a trace in the app, with a button that takes you where the action is.
You were mentioned
Someone @-mentions you in a comment on a visual, replies to a thread you take part in, or comments on content you authored. You are notified ONCE per comment, with the strongest reason.
An urgent lead arrives
An inbound message asks for a fast reply — “call me back quickly”, “it's for today”. The alert only fires when the lead BECOMES urgent: one already flagged that insists does not ring again.
A post did not go out
The network refused it. This is the most important alert of the four: a scheduled post goes out precisely when you are away from the screen, and content that never appears does not recover on its own.
An engine stopped
An automation or a sequence falls over for want of credits, after too many failures, or on a configuration that is no longer valid. Nothing visibly breaks: the screen still says “active”, and simply nothing happens any more.
The in-app trace ALWAYS goes first: it is the only channel that cannot be lost. It survives a full mailbox, a disconnected Telegram, an email filed as spam. Turbo then reaches you where you already are. Email only goes out where it adds something.
An urgent lead emails the project owner, and only them: writing to the whole team for every event would turn each inbox into a log, and that is how product messages end up filtered out. Other members get the trace and Turbo. A failed post sends no email at all: an expired token produces one per pending publication, and a burst would get notifications muted.
The right-hand panel lists what is waiting for you, newest first, with a dot on what you have not read yet. Every line carries a “View” button that takes you exactly where the action is: the mention on its visual, the prospect's conversation, the posts page, the stopped sequence's screen.
The section disappears entirely when there is nothing: a permanently empty area teaches you to stop looking there. New ones arrive live, without reloading the page.
A SUCCESSFUL post does not notify you. It is the most frequent event in the product, it is expected, and there is nothing for you to do about it: notifying it would drown out the other four. Same reasoning for “credits received” and “creation ready”, which flash by without leaving a line to deal with — the balance is visible, the creation is in the library.
The rule fits in one sentence: a notification earns its place when it calls for a decision and missing it costs something. Everything else teaches you to stop reading — and you unlearn reading what mattered at the same time.
Was this documentation helpful?