How to Give an AI Assistant Your Calendar Preferences

Quick answer

Give an AI assistant calendar preferences as a short operating policy with clear priorities, named time zones, and examples of allowed and disallowed bookings. Separate firm constraints from flexible preferences so the assistant knows when to offer an option and when to ask.

“Schedule intelligently” is difficult to evaluate. “Client calls Tuesday through Thursday afternoons, with 15-minute buffers” is a rule you can inspect against actual events.

Separate facts, preferences, and authority

Facts describe availability: working hours, existing commitments, travel days, and calendars that should be checked. Preferences describe desirable placement: afternoon calls, meeting batching, or a quiet Friday.

Authority describes what the assistant may change. It can know that an internal review is flexible without having permission to move it. Put those categories in separate parts of the brief so flexibility does not become implied authorization.

Include the event destination. Many people use personal and work calendars together, but new customer meetings should usually belong to a specific account. Tell the assistant which calendar defines busy time and which owns the invitation.

Write the policy in five parts

1. Availability: Working hours, relevant calendars, holidays, and time zone.
2. Meeting types: Standard duration and participants for each common meeting.
3. Placement: Preferred days, focus blocks, and buffers.
4. Exceptions: What may move and what requires your choice.
5. Completion: The details you want reported after booking.

Keep explanations that change a decision and omit background that does not. An assistant does not need your entire productivity philosophy to know that Friday mornings are unavailable.

An illustrative consultant policy

A consultant meets clients Tuesday and Thursday, uses Wednesday for delivery, and has a personal school-pickup commitment that should affect availability without being disclosed.

The policy allows 30-minute status calls in afternoon windows and requires approval for meetings longer than an hour. It prohibits moving client calls automatically. A personal calendar contributes busy time, but external participants see only offered slots.

When a client requests Wednesday morning, the assistant should recognize a delivery-day exception. It can suggest Tuesday or Thursday and explain the exception to the owner. It should not assume that a blank calendar event grid overrides the written policy.

A preference template

Time zone: America/Los_Angeles. Check my work calendar and personal busy time. Create business events on the work calendar. Client status calls are 30 minutes, Tuesday or Thursday 1-4 PM, with 15-minute buffers. Keep Wednesday for delivery and Friday mornings unavailable. Do not disclose personal event details. Do not move existing client commitments. Ask before meetings longer than one hour or outside these windows. Return the event link, attendee list, and outstanding responses.

This is an illustrative example. Replace the details with your own rules and confirm that the assistant supports the required calendar operations and privacy behavior.

Add two boundary examples

Examples reduce ambiguity without needing a long policy. An allowed example could be a Thursday 2 PM client review with a 15-minute gap before the next call. A disallowed example could be a Wednesday 9 AM review that occupies delivery time.

Add an exception example: a customer escalation outside the window should be proposed to the owner with alternatives, not silently booked. The example tells the assistant how to handle the situation that is most likely to stress the policy.

Avoid contradictions such as “always protect afternoons” and “all client meetings should be afternoon.” If two preferences conflict, state which wins or route the choice to you.

Maintain the preferences over time

When your working pattern changes, replace the standing rule rather than layering a new instruction on top of an obsolete one. Ask the assistant to restate the current policy before a busy scheduling period.

One-off exceptions should expire with the named task. “This Wednesday is fine” should not become a general Wednesday preference. Include dates whenever a temporary change matters.

Review a few bookings after setup. Check not only whether the time was free, but also whether meeting type, buffer, calendar destination, and authority were correct. This catches interpretation problems before you delegate a larger volume.

FAQ

How long should my calendar policy be?

Short enough to inspect easily, but complete enough to settle common decisions. Supporting details can live in linked material if needed.

Can the assistant learn preferences from behavior?

Some products advertise preference learning. Explicit rules are still useful for constraints you do not want inferred or exceptions you do not want generalized.

Where should I begin with Righthand?

Explore smart scheduling, calendar sync, and meeting scheduling, then verify a small set of bookings against your written preferences.