Scheduling

A booking page on your calendar: people outside Peractor pick a free time, and it lands on your calendar with its call.

Your booking page is a public link where anyone — a customer, a candidate, someone with no Peractor account — picks a time you're free for a kind of meeting you offer. The meeting lands on your calendar, with a video call when you want one, and they get a confirmation with an invitation for their own calendar and a link to move or cancel it.

Your page

Open Settings ▸ Scheduling. Each organization you're in gives you a page of your own, at /book/<organization>/<you>: switch it on, set its address and a line about you, and your working hours — a time zone, the hours of each weekday (more than one stretch a day, for a lunch break), and dates off. Copy link hands it out.

Free time is your working hours minus what is already on your Peractor calendar, in every organization you're in: events and work blocks you own or are invited to. An all-day event doesn't make you busy. Times from Google or Outlook calendars aren't read yet.

Kinds of meeting

A page offers one or more kinds of meeting, each with its own link: a title, a length (15 minutes to 12 hours), and where it happens — a video call, a place, a phone call to a number the visitor gives, a link, or nowhere in particular. Each kind also says:

  • Which calendar it books into: your own, the organization's, or a project's — any you may put events on. A video call needs the organization's or a project's calendar, because a personal event has no call; the call is made in the organization's installed Zoom, Meet or Teams, hosted by you.
  • Questions the visitor answers — a line, a paragraph, a choice or a phone number, each required or not.
  • Buffers kept free before and after, the minimum notice (four hours unless you change it), how far ahead (sixty days), the step between offered times (15, 30 or 60 minutes) and an optional daily limit.
  • Reminders: the visitor's by mail, with their link to move or cancel (a day before unless you change it), and yours on the event.

Team pages

Whoever holds Manage planning can make a team page from a role, at its own address. Round robin gives each booking to one free member — whoever has had fewest in the last thirty days; collective offers only times when every member is free and books them all, so its kinds book into the organization's or a project's calendar, where everyone sees them.

When someone books

The visitor sees the days with free times in their own time zone, picks one, gives their name and email and answers your questions. Then the meeting is on your calendar — titled "Intro call with Sam Lee", with their answers in its description and them listed as invited by mail — and:

  • they get a confirmation with an invitation file their calendar keeps, and a link of their own to Reschedule or Cancel;
  • you hear it in your inbox and by mail (switch the mail off on the page);
  • a move sends them an updated invitation, and a cancellation one that takes it off their calendar.

Moving the event in your calendar moves the booking and tells them; deleting it cancels the booking. Upcoming on the Scheduling page lists your bookings, and Cancel there takes a reason they read.

Limits

The pages aren't listed by search engines. One address can hold three upcoming bookings on a page, a page takes fifty bookings a day, and one connection makes at most ten bookings, moves or cancellations an hour. A time is given to one visitor only: whoever asks second is told it was just taken.

Workflows, the assistant and MCP

An on: booking trigger starts a run when a time is booked, moved or cancelled — "when someone books a demo, draft a brief from their answers". The assistant reads your pages and bookings and stages changes for you to approve; cancelling a booking always waits for you, because it writes to the visitor. MCP's read_scheduling and scheduling_write do the same under your permissions.