home / use cases / email and inbox / daily-inbox-digest

Your inbox, summarized before your coffee

Every morning at the time you pick, an Aivell reads what landed in your mailboxes overnight and sends one email — what needs a decision today, what merely needs a reply, what other chores already handled. Ten lines instead of a hundred messages, prepared entirely behind your firewall.

Watch the demo

starts when: Every morning at 7:30, on a schedule

The problem

The first hour of the day belongs to the backlog. You open the laptop and scroll: overnight orders, a supplier’s price change, three newsletters, a bank notice, something from the accountant that may or may not be urgent. With office workers receiving around 121 emails a day, the morning pile alone is a reading assignment — and the one message that actually needed you by 10:00 is somewhere in the middle of it.

Skimming is the standard coping strategy, and skimming is how deadlines get missed. The subject line said “quick question”; the body contained a payment date. Prioritizing mail properly means reading all of it — which is precisely the hour you don’t have.

How your Aivell does it

At 7:30, everything since yesterday gets read. Properly read — bodies, attachments’ cover notes, buried dates — across the mailboxes you named, before you’re out of the shower.
Three lists, ranked your way. Needs a decision, needs a reply, noise. Deadlines and amounts are pulled out and put on top; the senders you flagged as always-important can never sink to the noise list, whatever their subject line says.
The night shift reports in. If other chores answered questions or filed orders overnight, the digest says so in one line each — you learn what was handled without opening a single thread.
The digest respects your attention. Twenty lines, hard limit, noise cut first. An empty night produces one honest sentence, not a padded report.
Each colleague gets their own. Same run, different mailboxes: the projects inbox briefed to its owner, yours to you. Guardrails keep each digest reading only its own mailboxes and sending only to its own recipients.

It’s the briefing a very good assistant would leave on your desk — except the assistant read your private mail, so it had better live in your office. This one does: the reading and the writing both happen on the box, and the only thing that leaves it is the summary to you.

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 · morning inbox digest ● active

at 7:30 every weekday, read what arrived in my inbox and info@ since yesterday's digest

sort it into three lists — needs a decision, needs a reply, just noise

anything with a deadline or an amount goes on top, date and figure pulled out

mail from the bank, the notary or the accountant is never noise, whatever it says

note what the other chores already handled overnight, one line each

keep the digest under twenty lines; if it runs long, cut the noise section first

Chiara gets her own digest for the projects mailbox, same shape

nothing worth reporting? say exactly that, in one line

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.

Schedule fires the digest run each morning

Email reads the mailboxes, sends the one summary

Sensible guardrails.

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

Email Read access covers the named mailboxes only; every other folder and account is off-limits.

Email Outbound is the digest itself, to its named recipients — no replies, no forwards, nothing else.

Questions, answered.

Does it answer or move any of my email? +

No — this chore only reads and reports. A guardrail limits outbound mail to the digest itself, so your inbox is observed, never touched. If you want messages answered or routed too, that's a separate chore with its own rules, running alongside.

How does it decide what "needs a decision"? +

By the rules you wrote. Deadlines and amounts float to the top, certain senders are never noise, the rest is judgment briefed in plain language. When it files something wrong, you correct the chore in a sentence — like telling a new assistant once.

My inbox is the most confidential thing I own. Where is it read? +

On the box, in your office. The overnight mail is read behind your firewall, the summary is composed there, and the one email it produces goes to you. No message body ever transits an AI provider's servers.

Can others on the team get their own digest? +

Yes — one chore can brief several people, each on their own mailbox, each in their own shape. The colleague running projects gets project mail; you get yours; nobody gets each other's.

Related.

Shared inbox triage that never sleeps

Your info@ mailbox, triaged by a private AI colleague — classified, routed, and the routine ones answered. Behind your firewall, around the clock.

email and inbox read →

A morning briefing with the context attached

One email at 7:30 with today's meetings — and for each one, the latest thread, open items and client notes. Compiled onboard, inside your network.

scheduling and calendar read →

Weekly reports that write themselves

Your Aivell queries the database, builds the weekly report and mails it out on schedule — computed onboard, so your numbers stay behind your firewall.

data, spreadsheets and reporting read →

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.