Availability Block Sync

Availability Block Sync is a routine your Townie AI assistant runs on every calendar change: it recomputes the real open gaps inside business hours — weekdays only, holidays skipped, declined events and holds excluded, busy intervals merged — and reconciles the placeholder availability blocks to match exactly. The blocks are a derived view of open time, so what looks free truly is bookable, and real meetings are never touched.

To: your Townie

Subject: Create me an Availability Block Sync routine

Build me a routine that keeps my principal's bookable time always accurate, so the placeholder "open" blocks on the calendar actually match their real free time.

Run it on every calendar change.

When the calendar changes:
- Recompute the real open gaps within business hours: confirm it's a weekday and inside the active window, skip holidays, exclude declined events and holds, merge busy intervals, and find the gaps of at least 30 minutes.
- Reconcile the placeholder availability blocks to match those gaps exactly - add, trim, or remove them as needed.

Industry specifics that matter:
- Treat the placeholder blocks as a derived view of open time, so what looks free truly is bookable.
- Respect hold/intent semantics: office holds should stay visible but bookable, not counted as busy.
- Only ever write to the placeholder blocks - never touch real meetings.

This only edits its own placeholder blocks off real calendar data, so it's safe to keep them in sync on its own.

Before you build this, tailor it to the integrations I actually use and what you already know about me. Don't take the above at face value - ask me the critical questions that make it stronger: which tools and integrations to use, what the output should look like, and how much autonomy you should have (what to do on your own vs. check with me first).

Sent when you sign up — works as-is, or edit anything.

Get started with this routine

See it work: open time that's never a lie

Keep bookable time accurate without hand-editing the calendar

How this routine works

Works with

It reacts to every calendar change
A booking, a decline, a moved meeting — each change makes your Townie recompute what's actually open, so the blocks never drift out of date.
It computes the real open gaps
Weekdays inside the active window, holidays skipped, declined events and holds excluded, busy intervals merged — leaving only true gaps of at least 30 minutes.
The blocks reconcile themselves
Placeholder availability blocks get added, trimmed, or removed to match the gaps exactly. It only ever writes to its own placeholders — real meetings are untouchable.

Availability Block Sync FAQ

It's a routine your Townie AI assistant runs on every calendar change: it recomputes the real open gaps within business hours — excluding declined events and holds, skipping holidays, merging busy intervals — and reconciles the placeholder availability blocks to match those gaps exactly. The result is a calendar where what looks free truly is bookable.

Yes, by design: it only ever writes to the placeholder availability blocks it manages, derived from real calendar data — it never creates, moves, or deletes actual meetings. Read more in our security overview.

Holds keep their meaning: an office hold stays visible on the calendar but still counts as bookable, while declined events don't block time at all. You define which event types count as busy, and it applies that consistently.

Yes. Business hours, the minimum gap (30 minutes by default), which days are active, and how holidays are handled are all yours to set — tell your assistant once and every recompute uses the new rules.