Does it talk to the person asking for the meeting?

It drafts the reply and you send it. Every confirmation with an outside party is yours, through the channels you already authorize, and the audit is where fit gets established.

What happens when the rules cannot place a request?

The conflict is named along with the rules it broke, and the request is held rather than forced into a slot. Who gets the time is a decision you make.

Booking one meeting takes longer than the meeting

Today

The rules about your time are written down nowhere

Booking one meeting takes longer than the meeting.
The rules about your time are real and written down nowhere: which mornings stay clear, how much notice a first conversation needs, who is allowed to interrupt the block you keep for the work itself.
Whoever asks first wins, so the protected block survives right up until somebody needs it.
Then one person moves, and the whole thread starts again from nothing.

With agents

The rules held in one place, and the calendar itself left alone

The rules about your time apply the same way every time.
You approve a time instead of negotiating one.
Your calendar stays yours.

How an agent runs it

Every scheduling thread re-derives the same rules about your time by hand. This workflow holds those rules in one place and leaves the calendar itself alone.

Reads

Takes the meeting requests and the availability you authorize it to see, and nothing else.

Applies

Works to the rules you wrote down for your time, including the blocks that stay protected and the notice each kind of meeting needs.

Prepares

Puts up a proposal that shows the conflict it worked around and the rule that shaped it, so you are checking a decision rather than rebuilding one.

Names

Says which requests your rules cannot place, and which conflicts only you can settle.

Drafts

Writes the reply and the hold in your words, for you to send or place.

Human gate

It writes to no calendar. Nothing is placed, moved, cancelled or declined by it, nothing goes to an outside party, nothing is sent in your name, and the coordination can be run by hand at any point without the agent because the rules and the calendar are yours.

Records

Keeps what was proposed and what you decided, so the next proposal starts from the record rather than from the thread.

Results

What changes when the rules are written down

The same rules every time

They are written down once, and every proposal names the rule it applied.

Approve a time, don't negotiate one

The proposal arrives with the conflict it worked around already shown.

Your calendar stays yours

The workflow writes to no calendar, so every placement remains a person's action.

Where this fits

Workflow / Automate a Workflow

Tier 1 through the Automate a Workflow door: one process end to end, from a request arriving to a proposal a person places. The calendar, the invitation and the conversation with the other party stay yours. If the same rules later sit alongside inbound requests and follow-through for one seat, the executive assistant layer is where that goes next, as a possible step rather than a promised state; How It Works shows how the gates and the authorizations are built.

Tier 1 / Prove

How It Works

Questions, answered

No. It writes to no calendar at all: it proposes times and drafts replies, and a person places, sends and confirms. The gate is closed by default, and the rules and the calendar live in your systems, so the coordination can be run by hand at any point without the agent.

AI Opportunity Audit

See how many threads your rules could have proposed without you

Bring last month's scheduling threads and see how many of them your own written rules could have proposed without you in the loop.

Book an audit