home / use cases / back-office operations / approval-workflows

Approvals prepared for you — you just say yes

Requests for expenses, discounts and purchases land by email or webhook. Your Aivell assembles the case — who asks, how much, what the policy says — clears the trivial ones under your thresholds, and sends the rest to the right approver as one tidy summary with a yes or no to tap. Every decision lands on the audit trail.

Watch the demo

starts when: An expense, discount or purchase request arrives by email or webhook

The problem

Approvals are the traffic lights of the back office: everything stops at them. A €40 expense claim and a €40,000 purchase wait in the same inbox, behind the same overloaded manager. The requester writes a paragraph, the approver asks for the missing receipt, the thread grows, a week passes — for a decision that took eleven seconds once the facts were in one place.

Getting the facts into one place is the real work: who is asking, how much, against which budget, what the policy allows. That assembly is repetitive judgment, done dozens of times a week by people paid to do something else — and it is precisely the kind of preparation work that never should have been a human’s job in the first place.

How your Aivell does it

  1. The request arrives however it arrives. An email to approvals@, or a webhook straight from your expense tool or shop system — the trigger fires either way.
  2. The case gets built. Requester, amount, reason, history, and the relevant line of your policy, condensed into a summary an approver can read in ten seconds.
  3. The trivial clears itself. Under the thresholds you wrote — say, expenses below €100 with a receipt — the request is approved, recorded and confirmed without bothering anyone.
  4. The rest goes to the right person. Discounts above 15% to Paolo, purchases above €1,000 to Giulia. Each gets one message: the case, and a yes or no to tap wherever they happen to be standing.
  5. Silence has a plan. Twenty-four hours without an answer earns one reminder; after that, the deputy gets the case. The requester is kept informed at every step.
  6. Everything is on the record. Who approved what, when, and against which rule — written to the audit trail automatically, ready for the auditor’s least favorite question.

The thresholds, the approvers, the deputies — all of it lives in a chore written like you would brief an assistant. Move a threshold, rename an approver, tighten a rule: edit the sentence, and the next request follows the new policy.

The chore, as you'd write it.

No flowcharts, no code — a chore is just a message to your Aivell, in your own words. It shapes it into a solid, guarded procedure and follows it to the letter. This one:

Giulia Aivell · route approval requests ● active

when a request lands, work out what it is — expense, discount, or purchase

assemble the case — requester, amount, reason, and what the policy says

expenses under €100 with a receipt attached — clear them, tell the requester

discounts above 15% go to Paolo; purchases above €1,000 go to Giulia

send the approver one short summary with a plain yes or no

no answer within 24 hours — remind once, then route to the deputy

record every decision and its reasoning on the audit trail

You
Got it — I'll start right away, and check with you whenever something needs a human.
Giulia Aivell

The tools it uses.

Connected with single-click passkeys — no copied tokens, no OAuth hell.

Email receives requests, notifies approvers and requesters
Webhooks takes requests straight from your systems

Sensible guardrails.

Every tool can be limited to exactly what this chore needs. For this one, you might set:

Email May write only to the named approvers, their deputies and the requester. It cannot broaden the circle on its own.
Webhooks Accepts requests only from the systems you registered. Calls from anywhere else are dropped unanswered.

Questions, answered.

How does approving from my phone actually work? +

The chore pauses mid-run and sends you the case — amount, requester, policy check — as a message you can answer with a tap. The Aivell holds its breath until you decide, then finishes the job. Pausing for a human is built into the product, not bolted on.

Can the AI approve things by itself? +

Only inside the lines you drew. If you wrote "expenses under €100 with a receipt clear automatically", it clears those and nothing else. Raise the bar to zero and every single request waits for a human.

Requests contain salaries, margins and supplier prices. Who sees them? +

Nobody outside your walls. The request is read, summarized and routed on the box itself — no cloud AI, no third-party workflow service. The most sensitive numbers in your company stay in your office.

What happens when the approver is on holiday? +

The chore already knows the fallback — remind once, then hand the case to the deputy you named. No request quietly rots in an absent manager's inbox for two weeks.

Related.

What is an Aivell?

An Aivell is an on-premise AI colleague: a small box that plugs into your network, runs its own AI onboard and takes the repetitive work off your desk. Prompts, documents, data — nothing ever leaves your office. Unplug the internet: it keeps working.

You describe each task as a chore, in plain language. Your Aivell turns it into a solid, guarded procedure and runs it in the background — with guardrails on every tool, a complete audit trail, and approvals in your hand when you want them. One-time setup, fixed monthly fee. No tokens, no overages.

Watch the demo

onboard inference · air-gapped · fixed monthly fee