Skip to content
Neos Meet is in public beta.3 months of any paid plan free for every beta user — and permanent perks for the first 100.See the beta terms

Blog

Scheduling, explained honestly.

Working explanations of the parts of scheduling that quietly go wrong — host assignment, timezones, per-seat pricing, migrations. Written from the engine, not from a keyword list. Every price on this blog renders from the same file our pricing page uses, and every competitor figure carries the date it was verified.

Scheduling, explained

Round-robin meeting links: how host assignment works, and where it breaks

How round-robin booking links assign a host, the three competing definitions of “fair”, and the six failure modes that quietly ruin them.

· 10 min read

Pricing, honestly

How scheduling tools actually price — and where per-seat costs start to bite

The four pricing models scheduling tools use, the arithmetic of per-seat pricing as a team grows, and the contract terms that cost more than the sticker price.

· 7 min read

Migration guide

How to switch scheduling tools without breaking your existing links

Your booking link is in email signatures, bios, docs, and other people's CRMs. How to move to a new scheduler without a broken link or an orphaned meeting.

· 7 min read

How it works

Timezone handling in scheduling: why cross-timezone bookings go wrong

Wall clock vs instant, DST transitions that delete and duplicate an hour, midnight rollover, and half-hour offsets. The five places a booking's time goes wrong.

· 8 min read

Buyer's guide

What to actually evaluate when choosing a scheduling tool for a team

A framework for picking a scheduler: the eight dimensions that matter, a trial protocol that surfaces real problems in a week, and the contract questions first.

· 8 min read

Contracts, honestly

How Calendly's renewal and cancellation terms actually work

Auto-renewal, a CPI+3% default escalator, non-cancellable fees, and downgrades that wait for term end. What Calendly's own customer terms say, quoted.

· 6 min read

Architecture

Why some booking tools create a mailbox for every page

Microsoft Bookings provisions a real mailbox per booking page. That buys real things — and it also puts objects in your GAL and your attack surface.

· 5 min read

Etiquette

When not to send a booking link

A booking link is a gift to someone who already wants to meet you, and an imposition on someone who does not. How to tell which one you are sending.

· 5 min read

Lock-in

What happens to your booking links if we shut down

Scheduling tools die and take your links with them. What our sunset clause commits to, what export gives you, and the failure it does not cover.

· 6 min read

Explainers

Longer reference pages that are not posts. These carry no date on purpose: each one is generated from the part of the product it describes, so it changes when the product does rather than when we get round to editing it.

Calendar access

Scheduling that can't read your calendar

Every calendar permission we request, printed in full and tagged by whether the provider's API enforces the limit or only our own code does. Google's free/busy scope cannot return event titles; Microsoft has no equivalent, and the page says so.

For agents

Book me without a browser

The machine-readable half of a booking link: a JSON descriptor at a stable URL, the two public endpoints it points at, and the two things it will never tell a caller — the host's address, or a meeting length the booking path would refuse.

Competitor figures quoted across these posts were verified on July 21, 2026. Prices drift — check the vendor before you commit. See our pricing for ours.

A booking page you can have working in a minute.

Sign in with Google and your link is live before you configure anything. No card, no sales call.

Get started free