Context Theory Get your growth audit

Answer

How do you give an AI agent access to a shared calendar?

Read broadly, write narrowly, and route every write through something that owns the rules. A calendar write reaches a person.

Split it. Reading is a confidentiality decision about what the entries reveal; writing sends invitations to real people and is close to irreversible. Give read access broadly and route writes through a booking rule.

Reading and writing are different problems that happen to share an interface. Reading a calendar exposes who the business meets, when, and often why — entries carry client names, candidate interviews, medical appointments, board matters and negotiations in their titles. That is a confidentiality decision about content, and it is answered by scoping which calendars are visible rather than by trusting the agent's discretion.

Writing is the harder half because it has external effects that arrive immediately. Creating an event invites people, moving one notifies them, cancelling one tells them it is off. There is no version of undo that unsends those. An agent that creates a meeting with the wrong customer, at the wrong time, or with a title that reveals something to an unintended attendee has already communicated before anybody reviews it, which puts calendar writes closer to sending email than to editing a record.

The construction that works is a booking rule rather than a permission. Rather than granting write access to a calendar and instructing the agent to be careful, give it one narrow operation — book within these hours, of these durations, in these categories, with these attendees, on this calendar — implemented so that anything outside the rule is impossible rather than discouraged. The agent chooses among permitted slots; it does not choose what is permitted.

Buffers and travel are where automated booking creates a supervision job that did not exist before. A person scheduling knows the site visit before it needs an hour on either side, that two client calls back to back are a bad idea, and that Friday afternoon is when the invoicing gets done. Encoding those as rules is straightforward; discovering them after the agent has booked over them is a week of apologies. Write the rules down before switching it on, from whoever currently protects the diary.

Cancellation and rescheduling deserve their own decision and usually a different answer. Booking into free time is additive and its worst case is a wasted slot. Moving or cancelling an existing commitment takes something away from somebody who planned around it, and the cost is borne by a person who was not consulted. Most businesses should let an agent propose a reschedule and let a person send it, at least until the log shows how often the proposal was right.

Finally, the log is the control that makes the rest reviewable. Every event created, moved or cancelled, with the request that caused it, in a place somebody looks at weekly. Calendars are unusual in that errors are self-reporting — people complain — but the complaints arrive individually and look like isolated mistakes. Seeing them in one list is what turns five awkward conversations into one rule that needed changing.

A calendar write is not a database write. It arrives in somebody's inbox, and the undo does too.

Siddharth Sharma, Context Theory

Related questions

Should the agent have its own account?

Yes, and it is the single highest-value structural decision here. A distinct identity means the permission grant is visible, the audit trail attributes actions correctly, revocation is one action, and invitations arrive from something recognisable rather than appearing to come from a person who did not send them. Running an agent under a staff member's credentials makes every one of those impossible and is difficult to unwind later.

What about reading calendars to answer questions rather than to book?

That is the easier case and often the more valuable one — availability, workload, how much of the week is committed, whether a customer has been visited recently. It needs read scope only, has no external effects, and is a reasonable place to run for a few weeks before granting anything that writes. It also produces the evidence for whether booking is worth automating at all.

METHOD

Every figure below carries its source and the date it was verified. Nothing on this page is asserted.

The numbers on this page.

Datapoints
What Value Specific to
Sub-15-minute compliance — automated routing vs manual only62.5% vs 39.1%Category-wide
Average agent inbound response time15+ hoursCategory-wide

2026 speed-to-lead benchmark · verified

2026 real estate lead-response benchmark · hours · verified

What is specific to this page.

Evidence
Kind Claim Check it against
WorkflowCalendar reads and writes are different risks sharing one interface: a read exposes entry content including client names and appointment subjects, while a write sends an immediate notification to other people that no undo retracts.Reading a month of calendar entry titles and listing which would be a disclosure if seen by an unintended party.
SoftwareA booking rule implemented so that out-of-bounds bookings are impossible constrains the agent to choosing among permitted slots, which is a structurally different control from granting write access and instructing the agent about limits.Attempting, through the agent, to book outside the stated hours, durations or categories and observing whether it is refused or merely discouraged.
ResponseBooking into free time is additive and its worst case is a wasted slot, whereas moving or cancelling an existing commitment removes something from a person who planned around it and was not consulted, which makes rescheduling a separate permission decision.Separating the create, update and delete permissions in the calendar grant and checking which the agent actually holds.
ProcurementUnwritten scheduling constraints — travel buffers, spacing between client calls, protected administrative blocks — exist in the head of whoever currently protects the diary and produce a supervision job when discovered after automated booking rather than before.Interviewing the person who currently manages the diary and writing down every rule they apply without being asked.

Each row would be wrong on another industry's page. Where a sourced figure exists it is in the table above instead; these are the constraints that shape the work and do not happen to be numbers.

Start with the measurement.

Reading about a benchmark is not the same as knowing your own number. The audit produces yours, measured rather than estimated.

Get your growth audit

$497 · delivered in 5 business days · credited against month one