An assistant that talks to attendees and changes the calendar when it has to.
The assistant takes over communication before and after the meeting: answers questions, reschedules, cancels, and leaves anything out of scope to you. It does not join meetings or take notes — that is on the roadmap.
Three channels, independent of each other
Every booking has its own reply address; when the attendee answers, the assistant replies in the same thread.
No extra setup needed.
The attendee writes on WhatsApp, the assistant answers on the same channel and sends reminders there.
Requires a Meta Cloud API account and an approved number.
Booking-page chat
Questions asked while booking are answered in the chat widget on the page.
Enabled from the booking page.
If one is not configured, the others keep working.
Four things it does
Answers
Reads the booking record to answer questions about time, duration, attendees and the link.
Reschedules
Proposes the organiser’s open slots, takes the choice, and moves the meeting after explicit confirmation.
Cancels
Applies cancellation requests with two-step confirmation; auto-cancel can be switched off.
Escalates
Hands over to the organiser on out-of-scope requests such as pricing, contracts or someone else’s calendar.
Guardrails
Rule, value and reason. All of it shipped behaviour.
| Rule | Value | Why |
|---|---|---|
| Action cutoff | 60 minutes | Close to the meeting no reschedule or cancellation happens; it escalates to the organiser. |
| Confirmation lifetime | 30 minutes | An old “yes” does not count towards a new action. |
| Message rate | 20 / hour | A per-conversation limit that blocks loops and abuse. |
| Confirmation steps | 2 steps | Every reschedule and cancellation asks for explicit confirmation first. |
| Source of truth | tool call | Availability and meeting details are read from the system, never invented. |
| Input handling | data | Attendee messages are not read as instructions; no out-of-scope data is exposed. |
The organiser’s side
Reminders. Email and/or WhatsApp 1 day and 30 minutes before the meeting, plus its own reminders written onto the calendar event.
Daily brief. One paragraph every morning — 08:00 by default, in your timezone — summarising the shape of the day and the one or two things worth preparing.
Control. Auto-reply, auto-reschedule, auto-cancel, channels, reminder offsets, brief time, reply language and a free-text “tone” instruction.
Model. The assistant runs on Claude.
Sample daily brief · 08:00
You have four meetings today; three of them run back to back between 11:00 and 13:00 with no gap. The 14:30 call has no agenda — you may want to write one first. You are meeting the 16:00 attendee for the first time. A reschedule requested yesterday is waiting for your approval.
Transcripts, recording summaries and action-item extraction are not implemented yet. Team and organisation screens are also on the roadmap — the data model exists, the UI does not.
Hand your calendar traffic to the assistant.
Ten-minute setup: connect the calendar, add an event type, pick the assistant’s channel.