A visitor opens the chat on your website, says what they need, and books an actual slot in your calendar — length rules applied, details collected, invite sent, all in one conversation. The widget is a snippet on your site; the booking brain is the Aivell in your office, working against your live calendar.
starts when: A visitor types 'can I book an appointment?' in your site chat
A visitor lands on your site at lunchtime wanting an appointment, and the site answers with a phone number for a desk that is currently at lunch too. Some will call later. Many will book with whoever answers first — websites that can converse capture 20–35% more leads than those that just display a number.
Online booking platforms solve the availability half and create a new problem: your calendar, your patient names and your appointment reasons now live on the platform’s cloud, wrapped in a monthly per-calendar fee — and the tricky cases, like a first visit that needs double time, still get booked wrong.
The chat widget is one snippet on your site. The intelligence sits on the box in your office:
The guardrails are the quiet part that matters: this chore sees one calendar, writes to one calendar, and can only undo bookings it made itself. Your actual schedule can’t be wrecked by a chat window — and the whole thing is governed by a chore your receptionist could have dictated.
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:
greet the visitor and ask what the appointment is for
checkups get 30 minutes, first visits a full hour
offer only genuinely free slots from the calendar, next ten days
keep monday mornings clear — that's Nadia's admin time
collect name, phone and email before booking anything
book the slot, send the invite, confirm right in the chat
medical questions or anything unsure — give the front desk number, don't improvise
slot taken mid-chat? apologize and offer the next two
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:
They are live. The Aivell reads your real calendar at the moment of the conversation and writes the booking the moment the visitor confirms — no "pending request" limbo, no morning of manual confirmations. If a slot disappears mid-chat, it says so and offers the next ones.
One small snippet, pasted once — that is the entire installation. The widget carries the conversation to the box in your office and back; there is no booking platform account, no per-seat subscription, no third-party page your patients get redirected to.
No. Names, phone numbers and reasons for the visit are exactly the data you don't want on a booking platform's servers. Here the conversation is processed onboard and the booking lands in your own calendar — the visitor's details never leave your network.
Yes, because the rules are written as sentences. First visits take an hour, cleanings thirty minutes, monday mornings blocked for admin — the chore reads like your front desk's instructions, and edits take effect on the next conversation.
Customers email for an appointment; a private AI colleague checks the calendar, proposes slots, books and confirms — nothing leaves your office.
A chat widget on your site, an AI colleague in your office. Visitors qualified 24/7, leads saved, sales alerted — conversations never leave your network.
Reminder emails before every appointment, reschedules handled by reply — run by an AI colleague on a box in your office, not in someone's cloud.
An on-premise AI colleague for clinics and practices: books appointments, sends reminders, handles intake, cuts no-shows. Patient data never leaves the building.
Booking inquiries answered in the guest's language, reviews digested, arrivals prepped — an AI colleague that never sends guest data to the cloud.
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