Approvals and the Inbox
Anything your AI team wants to do that reaches a customer, changes a record or moves money arrives as a proposal. The Inbox is where you say yes or no. It is designed so that saying no is always instant, and saying yes is as safe as the action deserves.
What a proposal contains#
- What the agent wants to do, in plain words: "Confirm Thursday 14:00 for Jonas Weber, Golf, brake pads".
- Why, with the evidence: the customer's message, the slot, the price list line.
- The draft, if a message is involved, in your business's voice and the customer's language. Edit it before approving.
- Risk level and, for money, the amount.
- Who proposed it and when it expires if nobody decides.
Risk levels#
| Level | Examples | How you decide |
|---|---|---|
| Low | A reply from the FAQ, a reminder, a note in the Brain | One tap, from the lock screen too |
| Medium | Confirming a booking, sending a quote | One tap |
| High | Anything with money: a refund, a budget, a cancellation with a charge; anything above the amount threshold | Face ID or passcode first, in the app |
| Critical | Irreversible changes to the business's data or settings | Face ID or passcode, in the app |
Risk is set by rules, not by the agent: a money action is never less than high. A phone left unlocked on a table cannot approve a payment.
Where you can decide#
| Surface | What you can do |
|---|---|
| Phone Inbox | Everything. Swipe right to approve, left to reject, tap to read and edit the draft |
| Lock screen | Approve or reject low and medium risk straight from the push, no app open. If the decision cannot be saved you get a tappable "Decision not saved" so nothing is silently lost |
| Web dashboard | Everything, with the full history next to it |
| Your assistant | Through MCP, list and decide approvals from ChatGPT or Claude |
Rejecting is always one tap with no biometric check. You should never be slowed down from saying no.
After you approve#
The action runs immediately in the app: the booking is confirmed, the email or WhatsApp message goes out, the invoice is created. If the agent attached a customer's phone number, the phone offers Send on WhatsApp with the approved text prefilled, so the message leaves from your own WhatsApp with your number. The result is recorded in the audit trail with the surface you decided on.
If the action fails (the provider was down, the record changed meanwhile) the proposal comes back to you with the reason instead of pretending it worked.
Incidents#
The Inbox also shows incidents: an app whose build broke, a payment provider rejecting every charge, a domain whose certificate did not issue. An incident has a severity dot and a Fix on web link that opens the exact workshop tab. New incidents of warning or critical severity send a push.
Making it quieter#
- Permissions. Let routine kinds run automatically; see AI team and permissions.
- Standing rules. From a proposal, choose Always do it this way to record a rule in the Brain, so the agent does not ask the same question again.
- Quiet hours. The morning briefing respects your quiet hours, and nothing arrives at night unless it is critical.
- Pause. The app card's Pause AI team switch stops proposals altogether while you are away.