This is the limit the product is built around. The system reads data, works things out and proposes changes, but it does not apply them itself. Anything that moves money waits in the approval queue with its reason and its expected effect. Confirm it and it is applied, read back from the account, and written to the log with your name.
14 days on any plan, no card needed to start. After the click: a three-field form and the workspace.
The same count of waiting actions used to appear in two places and disagree with itself. Now the queue has one counter, and it is where you expect it.
Screen recording: an action in the queue with its reason and expected effect, a person confirming it, the change applied through the API, and the result read back from the account.
An action in the queue is not "raise the budget". It is "raise the budget on this campaign, on this platform, because over this period and on this much data the cost per lead is under target". Without a reason and an amount of data, an action does not reach the queue at all.
You can confirm or reject from the section, from the summary or from Telegram. A rejection is recorded too: the system remembers which proposals a person turns down and does not bring the same one back twice.
After confirmation the system applies the action through the platform API and re-reads the object from the account. If the platform refused, the refusal text is shown inside the action. Here "applied" means "read back", not "sent".
The Autopilot section shows how far the system is allowed to act on its own: what it may only propose, and what it may apply after confirmation. The assistant in Telegram follows the same rules: any tool that moves money leads to the queue.
From recommendation to log entry there are four steps, and a person takes only one of them.
A module, a recommendation or the assistant forms an action with its reason, effect and amount of data.
The action sits in the queue; the counter shows in the summary and a notification goes out on the chosen channels.
A person confirms or rejects it, from the section, the summary or Telegram.
Through the platform API, then read back from the account and written to the log.
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.
No. It will propose that as an action with its reason and expected effect. It raises the budget only after a person confirms, and then re-reads the campaign from the account to be sure the change stuck.
Users whose role in the organisation allows it. Actions the client signs off, a launch against a proposal for instance, are moved into the client portal.
The action gets the status failed, with the platform response text. That tells a platform limit apart from a fault in the system and points at what to change.
Yes. The assistant in Telegram shows waiting actions and takes a confirmation or a rejection. It does not run money-moving tools directly - only through the queue.
The first 14 days are free on any plan and you do not need a card to start. The approval queue is always on and cannot be switched off.
14 days on any plan, no card needed to start. After the click: a three-field form and the workspace.
