Let people book time

You set the rules once, and the page does the arithmetic

It's Wednesday, a prospect wants to talk, and nobody wants a six-email thread about Thursday. So you set an availability profile once: weekly hours in your own timezone, the notice you need, how far ahead people may book, how times are spaced, and a daily cap.

A booking page adds a name, one meeting length, the questions you want answered, and the purpose text every booker acknowledges. A page without that text isn't accepted, so nobody books without being told what the meeting is for.

The page offers times inside your hours that clear the notice period and the horizon, drops any time already held or booked, and stops at the day's cap. Draft pages, paused pages and addresses that never existed all get the same answer, so nobody can go looking for pages you're still preparing.

A visitor picks a time and it's theirs for ten minutes

Clicking a time places a hold before the form appears. Ten minutes is long enough to type a name and answer your questions, and short enough that an abandoned tab hands the time back.

Two people can still race for the same slot. The final write locks the page before it checks for overlaps, so exactly one booking lands, and the other visitor is told the time was just booked by someone else and asked to choose another. The daily cap is checked a second time inside that same write.

What's kept: the booker's name, email and timezone, the moment they acknowledged your purpose text, and a copy of that text read from the page at booking time — never taken from whatever the browser sent. A rota booking also records which rota and which rule assigned it.

A team rota shares out the bookings by two rules you can explain

Point a page at a rota and it offers every time at least one member has open, each member worked out from their own hours, holds and bookings. When a visitor picks a time, the rule runs again against the members who still have it.

There are two rules. In turn: the next member after whoever was booked last. Longest wait: the member whose last confirmed booking is oldest, with anyone never booked going first and ties settled by rota order. A hold that expires never moves the pointer, so a visitor who wanders off doesn't cost a colleague their turn.

If nobody on the team still has the time, the visitor is told so — a booking never falls through to someone who didn't have it open. The list of times never reveals who's on the rota, and a booking that names a host outside it is refused.

One script tag puts the booking inside your own page

The install is two pieces you paste: a plain link to the hosted page, then a script served from Runner's own origin with the major version in its address. The script renders the booking inline where the link was, in your brand and accent colours.

If the page is paused or the address is wrong, the script quietly does nothing and the link stays on screen, so a visitor still reaches the hosted page. The embedded booking runs through the same code as the hosted page, so a rule added to one is a rule on both.

Questions buyers ask