Mini lesson · English

How to let visitors book an appointment

Create a clear test appointment, connect its public booking link and verify booking, time zones and cancellation.

Start the interactive lessonRead the lesson below

Who is this for?

People offering a call or appointment from a website. Use the provider’s interface and an assistant for the link; calendar or website programming is not required.

Before you start

Your own Calendly account, controlled calendar and a second test inbox. The supplied fictional offer can be used privately; you do not need a real business. Available scheduling controls depend on your account.

Estimated time: 19–31 min

Estimates for the supplied starter files with prerequisite accounts and tools ready. Setup, deployment queues and delivery/DNS waits take additional time. Calendar/account permissions and available features depend on the provider and plan. Live booking tests are done in your own accounts.

What you will learn

  • Make the appointment offer and booking page agree.
  • Check a real test slot in both calendars.
  • Verify cancellation and relevant availability rules.

Workshop files

Step 1

Make one appointment promise

The visitor should know what they are booking.

Use the supplied fictional 15-minute website-review offer. Before the booking link, explain that the visitor will discuss one page, leave with one improvement to try and bring the page link plus one question. Choose and state where this practice meeting would take place.

Create the matching test event in your own scheduling account. Keep the fictional offer private and labeled as practice; you are testing a booking flow, not advertising a service you do not provide.

A concrete example

A complete example offer is: “Practice: a 15-minute website review by video call. Bring one page link and one question; leave with one concrete improvement to try.” The booking event should promise the same duration and location.

Use the supplied 15-minute practice website-review offer and my own booking account. Guide event duration, location, time zone, availability and calendar-conflict settings, then add its public link to the supplied page. Handle the page config for me. Help test a disposable booking and cancellation with only my controlled inboxes/calendars. Do not advertise the fictional offer as a real business service.

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

How it works (optional)

Let visitors book a specific appointment

Explain what the meeting is for before asking someone to choose a time.

A booking link reduces back-and-forth only when the visitor understands the offer. This example offers a 15-minute website review with one page and one question.

Calendly provides availability, calendar conflict checks and booking confirmation. Your website explains the promise and links to the public event. An embedded calendar is optional; a clear ordinary link is a useful first version.

Worked example

“Book a call” leaves the purpose open. “Book a 15-minute website review; bring one page and one question” sets a concrete expectation.

Extra implementation exercise

Which two pieces of information should the visitor know before opening the calendar?

Show a worked solution

They should know what the meeting is for, how long it lasts and what to bring or expect. That lets them decide whether booking is worthwhile.

  • Names purpose and duration.
  • Gives a preparation or outcome expectation.

Step 2

Configure the event and public route

Use your account’s actual scheduling controls.

In your own Calendly account, create the 15-minute practice event in your actual scheduling time zone. Use weekdays 10:00–12:00 for the exercise, connect a test conflict calendar and inspect any supported 10-minute buffer or one-day-notice setting. Record a missing plan feature instead of assuming it is on.

Copy the event’s public booking link and open it signed out. Check title, duration, location and displayed time zone before your assistant connects it to the supplied page. The account editor URL is not the attendee booking page.

A concrete example

Illustrative setup: the signed-out page offers the practice review for 15 minutes during the chosen weekday window. A one-day-notice option is unavailable on this account, so the test record lists that limitation rather than “passed”.

Calendly: scheduling overview · Calendly: availability overview

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

How it works (optional)

Configure availability and connect the public link

The website link and the provider's scheduling rules work together.

Follow START-HERE.txt in your own account. Set the event duration, actual time zone, available hours, calendar conflict checking and appropriate notice/buffers. Check which controls your plan supports.

Put the public event URL in config.js. The sample validates a Calendly HTTPS destination and keeps the link hidden until configured. It does not create appointments itself and must not link visitors into your admin editor.

Open the configured public event URL signed out before booking. Its title, duration, location and displayed time zone must match the website’s 15-minute review offer; a valid Calendly hostname alone does not prove the event exists or describes the right service.

Worked example

A page promising 15 minutes but linking to a 60-minute event is a product defect even if the URL opens successfully.

Calendly: scheduling overview · Calendly: availability overview

Extra implementation exercise

The booking page opens, but it offers times when your practice calendar is already busy. Is setup complete?

Show a worked solution

No. Verify which calendar is checked for conflicts and whether the busy event is visible to it. Test a known conflict before opening the event publicly.

  • Checks connected-calendar conflict settings.
  • Does not equate an opening link with correct scheduling.

Step 3

Book and cancel a disposable slot

Compare the same instant on both sides.

Use a second inbox you control to book one disposable slot. Compare its confirmation with the host’s calendar. Change only the attendee page’s displayed time zone to inspect the same appointment in another zone; do not change the host’s real availability to make this test.

Cancel the practice booking through its available cancellation path. Check the host calendar and the updated booking availability. Cancellation may free the slot, but other availability rules or a busy calendar can still keep it unavailable.

A concrete example

For illustration, 10:00 at UTC+3 and 07:00 at UTC describe the same instant. A 10:00 event in both zones would be different instants, so compare the time zones as well as the clock values.

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

How it works (optional)

Test a reservation, time zone and cancellation

A clickable link is the start of the workflow, not its completion.

Open the public event signed out and use your second inbox to book a disposable slot. Compare the selected time zone, attendee confirmation and host calendar event.

Test another displayed time zone and verify the converted instant, then cancel the test booking and inspect the resulting state. For in-person meetings, decide whether the event should be locked to the location's zone rather than assuming every visitor means your local clock time.

Use the time-zone selector on the public booking page to view a second zone without changing your account's scheduling zone. Compare the same chosen slot in both views and then in the calendar confirmation. If a buffer or notice control is unavailable on your plan, record that limitation before claiming the scheduling rule was tested.

Worked example

10:00 in one zone and 12:00 in another can be the same instant. The important check is the actual calendar time and zone, not matching the written hour everywhere.

Extra implementation exercise

The attendee sees a different clock hour than the host. Does that necessarily mean the appointment is wrong?

Show a worked solution

No. Different zones may display the same meeting at different local hours. Check the zone and converted instant in both calendars before diagnosing an error.

  • Compares time zones and actual instant.
  • Verifies both calendar confirmations.

Step 4

Finish a trustworthy appointment route

Retest the offer and the rules you can actually support.

Ask your assistant to connect the tested public event link to the supplied page. Use a known busy event in your controlled conflict calendar to test that its time is not offered, then remove temporary bookings and calendar fixtures afterward.

Complete booking-tests.csv with the offer, actual booking and cancellation results, time-zone comparison, busy-slot result and any unavailable plan controls. A working link is one result; conflict prevention is another.

A concrete example

A strong result can include one unresolved item: “The booking and cancellation matched both calendars, but I could not test conflict prevention because the test calendar was not connected.” That tells you what to fix next.

Files for this step

Start hereWorkshop files

Open or download the files below. When saving a project, keep the folder paths shown in the filenames.

How it works (optional)

Your assignment: make one appointment offer trustworthy

Use the same promise on the site, booking page and confirmation.

Replace the practice offer with a specific service you can actually provide. Keep its title, duration, preparation and location consistent across your website and provider.

Complete the booking test table using only your own test accounts. Remove the test booking afterward and keep any unsupported provider feature explicitly documented.

Worked example

A remote review should not unexpectedly ask someone to attend a physical office. Confirmation details are part of the experience, not just provider boilerplate.

The complete reference walkthrough is available in reference/assignment-walkthrough.txt. Compare its steps with your own result; fill the test record from observations in your own project.

Extra implementation exercise

Produce a consistent appointment page and a tested booking/cancellation record.

Show a worked solution

Keep the same 15-minute website-review promise on the website, public booking event and confirmation. In the public page use its time-zone selector to inspect a second zone; do not change the host's real availability merely to test the display.

Using two inboxes/calendars you control, book one disposable slot, verify its actual instant in host and attendee calendars, cancel it and inspect the updated availability. Place a known busy test event in the conflict calendar and ensure that time is not offered.

Record unsupported buffers/notice rules explicitly in booking-tests.csv. A working public link proves neither calendar conflict checking nor a successful reservation. Do not submit the test to someone else's real event.

  • Purpose, duration and location agree across the journey.
  • Conflict, time zone, booking and cancellation are checked in real test accounts.

Was this lesson useful?

Leave a like, or share it with someone who could use it.

Continue learning

Explore the other lessons