Customers
Booking links
A public page people pick a time on — which skips the days the host is on leave, because that is recorded here.
A booking link is a page somebody outside your organisation can open, see when a colleague is free, and take a slot. No account, no back and forth.
It knows when the host is away
Availability windows say when somebody is normally free. Approved leave and public holidays say when they are actually not — and both are already in this database, because leave lives here. A scheduling tool bolted onto a CRM cannot know, so it offers the slot, the client takes it, and somebody cancels by hand from their holiday.
Nothing has to be kept in step. Leave is approved, and the days stop being offered on the next visit to the page.
What blocks a slot
| Reason | Effect |
|---|---|
| Outside the availability windows | Never offered |
| Approved leave | The whole day is blocked |
| A public holiday they observe | The whole day is blocked |
| Another booking on any of their links | That time and its buffer |
| Inside the minimum notice | Not offered until it is far enough away |
Half a day off blocks the whole day
Leave records how many minutes somebody took, not which hours. Offering slots across an unknown half means a client eventually arrives to nobody, which costs more than the bookable time it saves. You can switch the whole behaviour off per link.
Where the meeting happens
- A video call
- Either your own standing room link, typed once and sent with every booking — which needs no setup at all — or a fresh meeting created per booking in Microsoft Teams, Google Meet or Zoom.
- A phone call
- The invitee gives a number when they book. Where you have connected telephony you can ring them from the booking itself: it calls your phone first and bridges when you answer, so there is nothing to install.
- In person
- An address, and it is required — a booking that says only “in person” is one the invitee cannot turn up to, and the product refuses to save one.
Teams, Meet and Zoom
| Provider | Whose account the meeting lives in | What it needs |
|---|---|---|
| Microsoft Teams | The host's own | Their Microsoft mailbox, plus one extra permission granted on their own settings page |
| Google Meet | The host's own | Their Google mailbox with calendar access — a Workspace admin can authorise it once for the domain |
| Zoom | Your organisation's | A Server-to-Server app you create inside your own Zoom account |
A meeting that could not be created never loses you the booking
Everywhere else in this product an integration that cannot do its job refuses outright — sending a contract for signature does, because one silently not sent is a contract somebody thinks is with the signatory. A booking is the opposite case. It is a commitment two people have just made, and refusing it because Zoom was unreachable leaves the client with no meeting at all; they do not try again. So the booking stands, the reason is shown to you on your own register, and the invitee is told the joining link will follow rather than being handed a button to nowhere.
Asking for the permission is its own step
Connecting a mailbox does not grant the right to create meetings in your name. That is asked for separately, by you, from your own settings page — bundling it would mean everybody who ever connected a mailbox had handed it over without being asked.
Time zones
Your availability is expressed in the host's own zone, so *Tuesdays nine to five* keeps meaning nine in the morning where they are when the clocks change. Everybody booking sees times in their zone, with the host's shown beside them.
Bookings are stored as real moments rather than as a clock reading, which is what stops a meeting drifting by an hour when either side's clocks change between the booking and the day.
Two people, one slot
If two people take the last slot at the same moment, one of them is refused and told to pick another. The database enforces it rather than a check that reads the diary and then writes to it, because between those two steps is exactly where the double booking happens.
A cancelled booking frees its slot and stays on the record. That somebody booked and called off is a fact about the relationship, and it is the answer to why an hour was held.
Cancelling
Whoever booked gets a private link that lets them cancel without an account. It is the only thing that authorises the cancellation, so it goes to the address they booked with and appears nowhere else.
What it does not do
- It does not read the host's calendar. A meeting accepted in Outlook does not block a slot here — only leave, holidays and bookings made through this product are known. Creating a meeting and reading a diary are different permissions, and only the first is asked for.
- It does not put the meeting in anybody's calendar either. It creates the conference; your own calendar entry is not written for you.
- There is no round-robin across a team, and no link that books more than one person at once.
- Rescheduling is a cancellation and a new booking.
A link publishes when somebody is free
Creating one takes the same permission as editing customer records, because a booking page tells the open internet the shape of a colleague's working week.