home / use cases / scheduling and calendar / meeting-coordination

Meeting coordination without the ping-pong

Cc your Aivell on any scheduling thread and it takes over the ping-pong — reading internal calendars directly, asking external attendees by email, proposing times that work for everyone, booking the room and sending invites. When someone drops out, it restarts the search itself. All of it runs onboard, behind your firewall.

Watch the demo

starts when: You cc your Aivell on a 'when suits everyone?' thread

The problem

Four attendees, two firms, one meeting — and eleven emails to schedule it. Everyone proposes, someone’s Tuesday collapses, the room is free but the client isn’t, and by the time a slot clears, the first proposal has expired. It is universally hated and universally tolerated: 43% of professionals spend over three hours a week doing scheduling arithmetic by email.

Scheduling links were supposed to end this, and for one-on-ones they mostly did. But multi-party meetings across organizations still come down to a human reading a thread, holding five constraints in their head, and typing out options — usually a partner’s assistant, usually several times per meeting.

How your Aivell does it

You change exactly one habit: cc your Aivell when the ping-pong starts.

  1. It announces itself and takes the thread. Attendees see a short note that scheduling is being handled; from then on, proposals and replies flow through it.
  2. Internal availability is read, not asked. Colleagues’ calendars are checked directly — including the standing rules the chore knows, like court mornings that never move.
  3. External attendees get asked like humans. A polite email with three concrete options. Their replies — “Thursday works, Friday only after two” — are parsed and reconciled without anyone filling in a poll.
  4. The slot clears, everything is booked at once. Room reserved, invites out, agenda attached, and one confirmation cc’d to you — the eleven-email thread compressed to the two that mattered.
  5. Reschedules restart the machine. A late decline triggers the search again automatically, with everyone kept informed instead of discovering an empty room.

Guardrails keep it inside its lane: colleagues’ calendars stay read-only, invites can only land in the meetings calendar, and it can never email anyone who wasn’t already on the thread. The judgment calls — oversized meetings, evening slots — pause and wait for Giulia, exactly as the chore says.

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 · coordinate the partner meetings ● active

when I cc you on a scheduling thread, take it over and say so

read our calendars for availability; external people get asked by email

propose three slots inside office hours that clear for everyone

Davide's tuesday and thursday mornings are court time — untouchable

once all confirm, book the meeting room and send invites with the agenda

someone cancels late? restart the search and keep the others informed

more than six attendees, or anything after 6pm — check with Giulia first

cc me on the final confirmation only, not the noise in between

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 runs the thread with all attendees
Calendar reads availability, books room and invites

Sensible guardrails.

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

Calendar Colleague calendars are read-only for availability. Events can be created only in the meetings and room calendars.
Email May write only to people already on the thread it was cc'd into. Adding new recipients requires approval.

Questions, answered.

How does it schedule with people outside the firm, whose calendars it can't see? +

The way a good assistant does — by asking. External attendees get a short email with proposed times; their answers are read and reconciled with the internal calendars. Nobody outside is asked to click a scheduling link or make an account anywhere.

What happens when a partner cancels an hour before the meeting? +

The chore covers it. Your Aivell notices the decline, tells the other attendees the meeting is moving, and starts the availability round again — using what it already knows about everyone's calendars, so round two is usually one email long.

Are our calendars and threads shared with a scheduling service? +

No. Scheduling tools in the cloud see your whole calendar and everyone you meet. Here the calendars stay on your systems and every message is read and written by the box in your office — who your firm meets, and when, is nobody's data but yours.

Can it respect rules that never appear in the calendar? +

Yes — that is what the chore is for. Court mornings are sacred, no client meetings before ten, the senior partner never does video on fridays. If you can say it to an assistant, you can write it in the chore.

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