home / use cases / scheduling and calendar / appointment-booking-by-email

Appointment booking by email, end to end

An Aivell watches your bookings mailbox, checks the calendar the moment a request arrives, proposes real free slots, and books the one the customer picks — invite, confirmation and all, in the customer's language. The whole exchange is handled onboard the box, behind your firewall, so patient and client details stay in the office.

Watch the demo

starts when: A customer emails asking for an appointment

The problem

“Do you have anything Tuesday afternoon?” is a one-line email that costs twenty minutes. Someone at the front desk opens the calendar, finds options, types them out, waits a day for the answer, discovers Tuesday is now gone, and starts over. Multiply by every new patient, client or customer, and 43% of professionals report spending three or more hours a week on exactly this.

The standard fix is a public booking link — which works until it doesn’t. Customers ignore it and email anyway, the link exposes your whole calendar to a cloud service, and edge cases (a first visit that needs an hour, a regular who always comes Thursdays) don’t fit the form.

How your Aivell does it

Requests keep arriving the way they always have — by email. What changes is who answers:

  1. The request lands, the trigger fires. No form, no link, no “please use our booking system” auto-reply. The customer writes in their own words, in their own language.
  2. The calendar is checked immediately. Real availability, including your written-down quirks — lunch stays free, fridays wind down at three, first visits need the long slot.
  3. Three options go back in minutes. While the competitor’s front desk is at lunch, your reply is already in the customer’s inbox.
  4. The customer picks, the Aivell books. Event created, invite sent, confirmation written in the customer’s language, the reason for the visit noted in the event for whoever runs the appointment.
  5. Exceptions wait for a human. An unusual request, a double-length booking, anything the chore flags — your Aivell pauses and asks Sofia from her phone before committing.

The guardrails make the boundaries physical: the bookings calendar is the only one it can write to, and the only person it can email is the customer who asked. Everything else about how your practice books — the rules, the tone, the exceptions — is a paragraph of plain language you can change over coffee.

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 · book appointments from email ● active

watch bookings@ for appointment requests, any language

check the calendar and pick free slots within the next two weeks

offer three options; first visits get morning slots when possible

keep lunch free, and never book fridays after 3pm

when the customer picks one, book it and send the invite

two people after the same slot? first email wins — offer the other fresh times

anything longer than an hour needs a yes from Sofia first

confirm in the sender's language and note the reason for the visit in the event

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 reads requests, proposes slots, confirms
Calendar checks availability, books, sends invites

Sensible guardrails.

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

Calendar Can create and move events only in the bookings calendar. Staff personal calendars are readable for availability, never writable.
Email May reply only within the requester's own thread. Mail to anyone else needs approval.

Questions, answered.

What happens when the customer says none of the slots work? +

The conversation just continues. Your Aivell reads the reply, checks the calendar again — "any time after Thursday" or "only mornings" — and offers new options. It is an email exchange with a colleague, not a booking form with fixed fields.

Can it follow our booking rules — buffers, lunch breaks, slot lengths? +

Yes, because the rules are the chore, written in plain language. Twenty minutes between visits, no fridays after three, first visits always an hour — you write the sentence, the Aivell obeys it, and changing a rule is editing a line.

Do appointment requests get processed by a cloud AI? +

No. The reading, the reasoning and the reply are all generated onboard the box in your office. For a clinic or a law firm, that matters — names, health details and case matters in booking emails never touch an outside server.

What if two customers ask for the same slot at the same time? +

The chore decides — typically first email wins. The calendar is the single source of truth, so the second requester simply gets a polite reply with the nearest alternatives instead of a double booking.

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