Dozens of background modules check campaigns on a schedule: delivery every 2 hours, placements every hour, creative fatigue every 12 hours, bids and structure every few hours. Each of them can propose an action. Not one of them can spend money without a person confirming.
14 days on any plan, no card needed to start. After the click: a three-field form and the workspace.
How much a module may do alone is set out loud in the Autopilot section: what it may only propose, and what it may apply after confirmation. Nothing may apply without confirmation.
Screen recording: the list of background modules with their schedules and last run times, a rule of your own tested against a past period, and a flow into the CRM.
Walking through twenty ad accounts by hand every morning is impossible, and a problem spotted on the third day costs three days of budget. The modules run on a schedule and bring only what changed: stalled campaigns, placements switched back on, burnt-out creatives.
A rule is written in words: on what condition, for which client and platform, what to do. The action can be a notification, a task for a person, or a change that goes into the approval queue. A rule can be tested against a past period before you switch it on.
The flow builder ties system events to outside services: a lead goes to the CRM, a deal goes to a platform as a server event, an alert goes to the team chat. The scheduler checks the queue every 60 seconds.
The Autopilot section shows how far the system may act on its own for each type of action. The same rules cover the background modules, the chat and the assistant in Telegram: any tool that moves money leads to the queue.
The background modules work as soon as an account is connected. Rules and flows are added as you need them.
The modules start checking them on their own schedules.
What may be proposed, and what may be applied after confirmation.
Condition, client, platform, action; tested against a past period.
Flows into the CRM, server conversions, webhooks and team chats.
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 form an action with the reason, the arithmetic and the expected effect, and send a notification. It is applied only after a person confirms, and then read back from the account.
Run it against a past period: the system shows how many times it would have fired and on which campaigns. That tells a useful rule apart from one that would flood the feed with notifications.
They tie system events to outside services: a lead into the CRM, a deal as a server event to a platform, an alert into the team chat, a webhook into your own system. Every step is logged, and a failed one is retried.
Each one shows its schedule and its last run time. A missing pulse is an alert, not silence: a module that has gone quiet looks exactly like a module with nothing to say.
The first 14 days are free on any plan and you do not need a card to start. The trust level is yours to set and yours to change at any moment.
14 days on any plan, no card needed to start. After the click: a three-field form and the workspace.
