Skip to main content
Ares runs on a simple contract: routine work runs on its own, and anything customer-visible or money-related waits for you. The approval queue is where that contract is enforced, and it is designed to cost you seconds per day, not add a second job.

What requires approval

CategoryExamples
New spendCampaign launches, budget increases, scaling a winner
CreativeNew ad copy or imagery, changes to a running ad
Out-of-pattern messagingA blast to a list, re-engaging old leads, anything beyond standing follow-up
Judgment callsAnything Ares itself flags as unusual or risky for your account

What runs without approval

  • Reading and organizing CRM data
  • Standing lead follow-up you have already authorized
  • Monitoring, reporting, and analysis
  • Pausing something that is clearly wasting money
The asymmetry is intentional: actions that stop problems run free, actions that create exposure wait for you.

Working the queue

Pending approvals live on the dashboard. Each one shows:
  • What Ares wants to do, in full: the exact message, the exact ad, the exact budget
  • Why, in a sentence: the reasoning, not just the request
  • The blast radius: who it reaches or what it spends
You have three moves:
  1. Approve. One tap. The action executes and shows in activity.
  2. Decline with a note. “Too pushy, soften it” or “wrong photo” sends it back for revision. The revised version returns to the queue.
  3. Ask questions first. Jump to chat and interrogate: “what happens if we do not do this?” The approval waits while you decide.
Approvals do not expire silently. If something sits unanswered, Ares reminds you rather than acting anyway or quietly dropping it.

Widening standing authorization

Approving the same kind of action repeatedly is a signal. You can convert a pattern into standing authorization in chat:
“You do not need to ask before pausing underperforming ads.” “Re-engagement messages to leads under 90 days old are pre-approved if they follow the usual templates.”
Standing authorizations are visible, revocable, and narrow by default. “Never ask me about anything again” is not an available setting, by design: spend and new creative always come to you.

Narrowing it

The other direction always works too, and instantly:
“Ask me before sending anything to commercial leads.” “All messaging goes through approval this week, we have a sensitive job in progress.”

The point

The queue exists so you can delegate execution without delegating judgment. You stay the owner: every dollar and every customer-facing word is either something you approved directly or something you explicitly pre-authorized in a scope you can revoke.