Andy drafts. A human approves. Nothing slips out.
Every Andy-proposed write — an outbound email, a calendar invite, a new invoice, a contact update — passes through an approval card. You review, edit, approve, dismiss. The audit log records the decision.
What the approvals queue looks like
A single feed of everything Andy wants to do on your behalf. You can clear it in five minutes a morning, or work it as it comes in.
- Email sends, calendar writes, accounting writes, task creates — all queued.
- Approve, edit, or dismiss each card with one click or keystroke.
- Approved actions execute against the provider; the audit log records who, what, when.
- Operator-controlled thresholds: routine actions can auto-approve, significant ones cannot.
How Andy presents its work for approval
Andy never acts invisibly. Every proposed write shows up as a card with the exact change, the context that produced it, and a one-tap approve.
- Diffs for edits to existing records — see what changes before you say yes.
- Plain-English summary of what will happen on which provider.
- A “why” line: which thread, workflow, or rule produced this draft.
How the company brain feeds it
The brain remembers which kinds of decisions your team waves through and which it always wants to read carefully. Approval friction goes down on the routine stuff, stays high on the important stuff.
- Routine approval patterns can be turned into auto-approve rules.
- Anomalies (unusual recipients, unusual amounts) stay manual.
- A full audit trail is always there if you need to revisit a decision.
For technical readers
The approvals module exposes the same operational record to every other module — so a change here ripples into the relevant workflow, contact, and Andy context automatically. All writes back to providers (where applicable) go through the Approvals queue unless an operator-defined auto-approve rule applies.
Want to see this running on the apps you already use? Apply for the beta, or tell us what your team is trying to run from one place.