Priorities and Preferences

Priority without rule-writing#

Most scheduling tools require you to encode your preferences up front — meeting types, buffer rules, priority tiers, blackout windows. That configuration is work, it goes stale, and it never covers the case actually in front of you.

Vela reads priority from context instead. A client meeting outranks an internal sync. A final-round panel outranks a coffee chat. An investor call gets the protected slot. You can override any of it by saying so in plain language on the thread.

Preferences stated plainly#

Availability windows

"Friday evenings are free" or "no calls before 10am" are understood as stated. You do not have to translate them into recurring calendar blocks.

Meeting-type defaults

Screens run 30 minutes, hiring-manager calls 45, panels an hour. Tell Vela once and it applies the default while still accepting exceptions on the thread.

Buffers and back-to-back limits

If you do not want four interviews stacked without a break, say so. Vela spaces them when it negotiates rather than filling every open slot.

VIP handling

Some counterparties get the good slot regardless of what else is competing for it. Vela applies that ranking when proposing times.

Why this matters for external coordination#

Priority is the difference between an assistant and a booking link. A link treats every request as equal and first-come-first-served, which is exactly the wrong behavior when one of those requests is your most important client.