Nothing happens without your OK
A team that works for you has to earn trust, and trust comes from control. Aneflo is built so that your team does the legwork, and you keep the final say on anything that matters.
Approvals
When your team reaches a step that is important, it stops and asks. An approval shows you what is about to happen in plain language: who a message goes to, what it says, which event changes, or what will be spent. You can approve it, change it, or decline.
What counts as important is things that touch other people or are hard to undo. Sending an email in your name, replying in a conversation, changing a meeting other people are invited to, or spending money all belong here. Looking things up, organizing information for you, and preparing a draft do not need a question, because nothing leaves your side until you decide.
You can see pending approvals in one place, so a request is never lost in a long conversation. If you do not answer, the action simply waits.
When a draft changed
Drafts are where approvals matter most. Your team writes a reply, you glance at it, and later a teammate refines it with new information. You should never approve one version and have another go out.
Aneflo handles this by tying approval to what you actually saw. If a draft changed after you looked at it, the approval shows that it changed and what is different, and it asks again. Approving an old version does not carry over to a new one.
That small rule removes a whole category of surprise. What is sent is what you approved.
Spending room
Some work costs money to do. On every plan, your team can use paid data services to get information it could not otherwise reach. These calls have a spending ceiling, so a task cannot run up a bill on its own.
Small calls within that ceiling can run without an approval card, because stopping you for a few cents would make the team slower than doing it yourself. Anything beyond the small range, or anything the ceiling would not cover, asks first. It is spending room: enough freedom to keep work moving, with a hard edge around it.
Your rules come first
Defaults are a starting point. If you tell your team that every outgoing message needs your OK, or that it should never touch a particular calendar, those rules apply every time, including to small things that would otherwise run on their own. Explicit rules always win over defaults.
You can add rules in conversation. Say what you want, and your team confirms what it understood before it relies on it.
Seeing what happened
Approvals are only half of control. The other half is knowing afterwards. Activity records what your team did, what it handed off, and what it is waiting on. If something looks off, you can see where it came from and correct it. Memory works the same way: it is visible and editable, so anything your team has learned about you can be changed or removed.
Why we built it this way
An assistant that asks about everything is exhausting, and one that asks about nothing is a risk. The goal is to ask rarely, ask at the right moment, and make each question easy to answer in a few seconds, with enough information to say yes or no without opening anything else.
If you want to see it in action, the five-minute guide gets you to your first approval quickly.
FAQ
What counts as important?
Things that affect other people or are hard to undo, such as sending a message on your behalf, changing a calendar event others are invited to, or spending money.
Can I make Aneflo ask about more things?
Yes. Explicit rules you set always apply, so you can require approval for anything you want to see first.
What if I do not respond to an approval?
The action waits. Nothing important happens until you say yes.
