YOWO7 Booking pages

Appointments that are already in the calendar

You share one link. The guest only sees times that are really free and books with name and email. The event lands in the target calendar, the confirmation carries the calendar file — and the guest sits in your CRM as a contact.

What YOWO7 booking pages do

Four building blocks from the public link to the CRM contact — without scheduling by email.

One link instead of email threads

Create a booking page, publish it, share the link. The guest needs no account and no invitation.

Only real free times

Free times come from your windows and your calendar. Busy times, buffers and notice period drop out.

Event in the target calendar

A booking becomes an event in the calendar you picked — with the guest as attendee and a confirmation by email.

The guest is a contact

YOWO7 looks up the CRM contact by email address or creates it. The booking sits on that contact.

The page your guest sees

booking.yowo7.com/b/your-slug holds the public page: title, duration and the free times. The guest picks a slot, fills in name and email — phone is optional — and is done.

  • Public link, no account and no login for the guest
  • Free times in the time zone of the booking page
  • Name and email are required, phone is optional
  • Confirmation on the page and by email
  • Only published pages are reachable

No login, but not unprotected

The public page limits requests per minute and filters out automated submissions.

Create booking pages in the workspace

In the app you create pages: title, duration, time zone and the calendar the events land in. Publishing makes the link reachable, unpublishing takes it offline again.

  • Title, duration in minutes, time zone and target calendar
  • Slug and public link come from the title
  • Publish, unpublish and delete
  • Pick any writable calendar source as the target
  • Create and edit from the member role, read for viewers

Where the free times come from

Every page has availability windows — Monday to Friday, 9 to 17 by default. Slots are built from them in the length of your duration. Busy times, buffers, minimum notice and the booking horizon cut away what does not fit.

  • Windows per weekday, plus exceptions for single days
  • Defaults: Mon–Fri 9–17, 30 minutes duration, 60 minutes notice, 28 days horizon
  • Buffer before and after the appointment
  • Collision check against calendar events and existing bookings
  • Windows, buffers and notice are set via Public API or MCP — from the Business plan

The slot is held briefly

Picking a time holds it for two minutes. Only a time from the current list can be booked.

A booking becomes an event

Booking creates the event in the page's target calendar, with the guest as attendee and the form details in the description. The guest receives a confirmation with a calendar file.

  • Event in the target calendar, with the guest as attendee
  • Form details sit in the event description
  • Confirmation to the guest, with an .ics file attached
  • Sent through a sender identity from your workspace
  • Connected Google and Outlook calendars refresh before the slot list

Whoever booked is in the CRM

YOWO7 looks up the guest by email address and creates the contact if it does not exist yet. The booking sits on that contact — no second list just for appointments.

  • Contact found by email address or created
  • Booking on the contact instead of a separate appointment list
  • Keep working in the CRM: notes, tasks, deals
  • The event stands even when no contact can be matched

One customer record, not another tool

The guest sits next to your other contacts — with company, email and everything else on the record.

Bookings at a glance

For each page you see the bookings: guest, email, time and status. You know what is coming up without searching the calendar.

  • Bookings per page, with guest, email, time and status
  • Status confirmed or cancelled
  • A cancellation deletes the event and frees the time
  • Unpublish the page when nothing should be booked

Booking pages via API and MCP

Private apps manage booking pages with the same actions you use: eight tools for creating, changing, publishing and reading. Booking itself happens on the public page.

  • Scopes booking:read and booking:write
  • booking_list_pages, booking_create_page, booking_update_page
  • booking_publish_page, booking_unpublish_page, booking_delete_page
  • booking_list_slots and booking_list_bookings for reading
  • Public API and MCP belong to the Business plan and above

Every detail

The scope of YOWO7 booking pages to scan through — so you can see whether your workflow fits.

Booking pages

  • Title and duration in minutes
  • Time zone per page
  • Target calendar from your writable sources
  • Slug and public link from the title
  • Publish, unpublish, delete

Free times

  • Availability windows per weekday
  • Exceptions for single days
  • Buffer before and after the appointment
  • Minimum notice and booking horizon
  • Slots in the length of the configured duration

No double booking

  • Check against existing calendar events
  • Check against times already booked
  • Recurring events are counted
  • Short hold while picking a time
  • Only times from the current list are bookable

Public page

  • Address booking.yowo7.com/b/{slug}
  • No account and no login for the guest
  • Name and email required, phone optional
  • Only published pages are reachable
  • Rate limits per minute and filters against bots

Calendar

  • Event in the page's target calendar
  • Guest as attendee on the event
  • Form details in the event description
  • YOWO7 calendar, Google and Outlook
  • Connected calendars sync before the slot list

Confirmation

  • Email to the guest right after booking
  • Calendar file (.ics) attached
  • Sent through your sender identity
  • No reminder emails
  • No rescheduling or cancelling by the guest

CRM and hosts

  • Contact found by email or created
  • Booking on the CRM contact
  • Several hosts per page possible
  • The first host who is free gets the booking
  • No rotation between hosts

Roles, API and limits

  • Read for viewers, create and edit from member
  • Public API and MCP with the scopes booking:read and booking:write, from the Business plan
  • Booking runs through the public page, not the API
  • No payments and no group appointments
  • Managed in the web app, not in the mobile app

Missing something for your workflow? Ask us — we will tell you straight whether and how it works.

And this is one module

Booking pages are part of YOWO7

The same workspace holds Calendar, CRM, Inbox, Projects and more. One login, one data set, no handover between tools.

Core apps

More apps

See what else belongs to it — or create your first booking page.

FAQs about booking pages

You publish the booking page and share the link, for example booking.yowo7.com/b/intro-call. The guest picks a free time, fills in name and email and books. No account needed.

Name and email are required, the phone number is optional. The public page asks for nothing else.

No. Before showing free times, YOWO7 checks the host's calendar events and existing bookings including buffers. Picking a time holds it briefly, and only a time from the current list can be booked.

The ones inside the page's availability windows. By default that is Monday to Friday, 9 to 17, with 30 minutes duration, 60 minutes minimum notice and a 28-day horizon. Duration, time zone and target calendar are set in the app. Windows, buffers and notice go through Public API or MCP, which are included from the Business plan.

The target calendar of the booking page. That can be the YOWO7 calendar or a connected Google or Outlook calendar, as long as it is writable. Events from connected calendars also count in the collision check.

Yes, an email with a calendar file to save. It is sent through a sender identity from your workspace. There are no reminder emails.

No, the public page has no interface for that. When a booking is cancelled, the event disappears from the calendar and the time is free again.

Yes. YOWO7 looks up the contact by email address and creates it if it does not exist yet. The booking sits on that contact. If matching fails, the event still stands.

Yes. The first person who is free at the chosen time gets the booking. There is no rotation or even distribution. You maintain the host list via Public API or MCP, so from the Business plan.

Yes. With the scopes booking:read and booking:write private apps manage pages and read free times and bookings: booking_list_pages, booking_create_page, booking_update_page, booking_publish_page, booking_unpublish_page, booking_delete_page, booking_list_slots and booking_list_bookings. Booking happens on the public page.

No. Booking pages do not take payments. Quotes and invoices live in Sales.

Team and up. They are managed in the web app — Calendar and booking pages are not part of the mobile app. The public booking page itself is a web page and needs no app.

One link. The appointment stands.

Create a booking page, pick the target calendar, share the link — with your real appointments instead of sample data.

Get started

Booking pages belong to the workspace — from the Team plan.