An Aivell reads each incoming email and writes a ready-to-send draft reply in your tone, pulling facts from your own knowledge base. Nothing goes out on its own — drafts wait in the thread for a human to approve, edit or discard. All the reading and writing happens onboard, behind your firewall.
starts when: An email arrives in your mailbox
Answering email is a writing job nobody was hired for. Each message asks the same small labor: recall the context, dig up the fact, pick the words, get the tone right. Multiply that by the day’s stack and you arrive at 28% of the workweek spent inside the inbox — most of it composing slight variations of replies you have written a hundred times.
The usual fixes fail in opposite directions. Canned templates read like canned templates, and the sender notices. Full auto-responders go further and send things you would never say, to people who matter. What you actually want sits in between: a colleague who writes the first draft of everything — and always gives you the last word.
The chore is eight lines of plain language, and every one of them is yours to change. Tighten the tone, add an exception, promote a correspondent to “always ask first” — it’s editing a briefing, not configuring software.
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:
read each new email in my inbox; skip newsletters, receipts and automated mail
write a draft reply in my tone — short, direct, no corporate filler
pull facts from the knowledge base; if a fact isn't there, leave a [gap] marker instead of guessing
reply in the sender's language; German drafts go past Giulia before me
asking for a price or a commitment? draft it, but flag it "needs your numbers"
angry or legal-sounding mail — draft a short acknowledgment only, nothing more
save every draft inside its thread; never send anything yourself
at 17:30 list the drafts still waiting, so nothing sleeps in the outbox
Connected with single-click passkeys — no copied tokens, no OAuth hell.
Every tool can be limited to exactly what this chore needs. For this one, you might set:
It can't. Sending is disabled by a guardrail at the tool level — not a polite instruction, a limit the box enforces. Your Aivell writes drafts; the send button stays human.
You brief it, in the chore, the way you'd brief an assistant — "short, direct, sign with first name only". It also sees the earlier messages in each thread, so it picks up how you already talk to that person. When a draft sounds off, correct the chore in one sentence.
No. The model runs onboard the box in your office and learns nothing from your mail. Messages stay on your mail server; the drafting happens behind your firewall and is never shared with an AI provider.
The chore says don't guess. The draft arrives with a visible gap marker where the missing fact goes — a price, a date, a yes or no — so you fill in one blank instead of writing the whole reply.
Your info@ mailbox, triaged by a private AI colleague — classified, routed, and the routine ones answered. Behind your firewall, around the clock.
Customers write in any language; your Aivell replies in theirs and briefs the team in yours. Translation runs onboard, so mail never leaves the office.
An on-premise AI colleague chases unanswered emails and missing client documents — politely, on a schedule, stopping the moment the reply arrives.
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.
onboard inference · air-gapped · fixed monthly fee