Calls

Booking

Booking pages PYLO hosts in place of Calendly and iClosed, with round robin, Google Calendar for each closer, invitee questions that can disqualify, and invites with reschedule and cancel links.

Read as Markdown

Booking runs the calendars your leads book calls on. You make an event type for each calendar you keep today (the funnel calendar after the application, the DM setting calendar and the dialling calendar), each closer sets their own hours and connects Google Calendar, and you share the link, embed it on your page or end a form with it. Every booking lands exactly where a Calendly booking does: a lead, a call on Post-Call, booking history, your flows, Slack and your booked call reminders.

Who can open it

Everyone. It sits in the Calls hub. A closer sees the calls booked with them and sets their own hours and calendar; a setter can open it to copy the live booking links for leads. Owners and admins see every booking, can move or cancel one, set anyone's hours, and make event types.

Event types

Under Event types, press New event type and pick a starter:

• Funnel call: 45 minutes with 15 minutes after, start times every 30 minutes, three days ahead with four hours' notice, round robin, and two questions: the capital they have set aside, and whether they will show up on time (answering no disqualifies).
• DM setting call: the same with one hour's notice.
• Dialling call: no limit on how far ahead, one hour's notice, and PYLO's own confirmation page.
• Blank: 45 minutes with 15 after, round robin, Google Meet.

A new event type is a draft with you as its first host. Open it to change:

• The call: its length, where it happens (Google Meet, a Zoom link, a phone call or anywhere else), the funnel a booking here lands on, and whether a booking here counts as qualified.
• When it can be booked: buffers before and after, how often start times are offered, minimum notice, how far ahead (a number of days with today counting as day one, weekdays only if you like; between two dates; or no limit), and the most calls one host takes in a day.
• Who takes it: round robin (a time shows when any host is free; the highest priority free host takes it, and equal priorities share calls by weight) or every host together. Keep the same host when an invitee reschedules on, as operators do in Calendly.
• What it asks: name and email always, the phone number (asked by default so reminders reach them), and your own questions. A choice can be marked Disqualifies: an invitee who picks it is not booked and goes to the page you set, or sees your message, and the attempt shows on Bookings so a setter can follow up.
• After booking: your confirmation (pre-call) page. Booking passes it the same details Calendly does (invitee_full_name, invitee_email, event_start_time, assigned_to, answer_1 and so on, plus the UTMs), so a page built for Calendly's redirect keeps working.

Times it offers this week checks the event type the way the booking page will, in your own time zone. Press Go live when it is ready; it needs at least one active host. Switch off stops new bookings and leaves booked calls alone.

Your agent can also plan an event type, and its changes, for you to approve.

Sharing it

Share on the event type gives you the link, a snippet that embeds the page on any website, a button that opens it in a popup, and a plain iframe. The page carries the UTMs on the link through to the lead.

To put the calendar at the end of your application, open the form under Forms, choose PYLO booking as the last step and paste the event type's link. A qualified applicant then sees the calendar with their name, email and phone already filled in, and the booking lands on the same lead.

Availability

Under Availability, each host sets the time zone they work in, their hours for each weekday (more than one block a day if they take a break), dates with different hours or none, and days off. Owners and admins can set anyone's hours, the workspace's holidays, the time zone booking windows are counted in, and the name invitees see.

Invitees always see times in their own time zone, and a host's 9:00 stays 9:00 on both sides of a daylight saving change.

Google Calendar

Each host connects the Google account they take calls on. Then:

• their own events on the calendars they choose block those times on the booking page;
• every booking is written to their calendar with its own Google Meet link;
• a call they move or delete in Google moves or cancels the booking, and the invitee is told.

What the invitee gets

A confirmation email with a calendar invite, and links to reschedule or cancel. A move sends an updated invite and a cancellation removes it from their calendar. Reminders are your messaging workflows: the Booked call reminders starter runs on every booking made here, as it does for Calendly bookings. See Workflows.

Two invitees can never take the same host's time: if one books it first, the other is told it has just gone and picks another.

Bookings

Every live event type's link sits at the top under Booking links, to copy and send to a lead. Bookings lists upcoming, past or all bookings with the invitee, the event type, the host and the status. Details shows their answers, source and meeting link, and lets owners and admins move or cancel the call. A booking that has not reached the lead or Google Calendar yet says so; PYLO tries again every five minutes.

Coming from Calendly or iClosed

Calendly and iClosed stay connectable, and nothing about them changes when you start using Booking. Import from Calendly brings your Calendly booking history in from a date you pick: check first (nothing is written), then import. Imported bookings become calls and leads with Calendly's own references, so a booking imported now and delivered later by Calendly is still one call, and old bookings start no reminders or alerts.