Conversa Labs Help Center
en
Language
pt_BR Portuguese (Brazil) en English es Spanish

Public booking page

Open in
View as Markdown Open in ChatGPT Open in Claude
Conversa Labs

Conversa Labs

Last updated on Jul 28, 2026

Overview

The public booking page is the link you send so customers can book time themselves, with no back-and-forth. It shows only the free slots of the chosen event type — computed from your availability, your busy times (native and Google), and the buffers. The customer picks a slot, answers the intake questions, and confirms.

On confirmation, Conversa Labs can automatically open a conversation, create a task with a reminder, link to a CRM deal, and send a confirmation email with a Google Meet link and an .ics file — each side-effect can be turned on or off per event type.

Prerequisites

  • The Calendar module enabled, with at least one event type and availability configured.
  • For the automatic Meet link, an active Google connection.
  • For paid bookings (optional), the Payments module enabled — in that case the slot is held and is only confirmed after payment.

Step by step

  1. In the Calendar, open the event type you want to publish and copy the public link.
  2. Share the link with the customer (message, email, website, social bio, etc.).
  3. The customer opens the page and picks a date and time from the free options.
  4. If the event type offers more than one option, they choose the location of the meeting — for example Google Meet, phone, in person, or a custom location.
  5. They fill in their contact details — including the phone number (optional) — and answer the intake questions, if any.
  6. (If the event type requires payment) the customer completes the payment to confirm.
  7. The customer confirms and receives the email confirmation with the details and the invite.
  8. You see the new booking in the Calendar and inside the contact's conversation.

Settings & options

  • Link per event type: each event type has its own link, with its own rules.
  • Intake questions: custom fields the customer answers when booking. Each question has a type — short text, long text, dropdown, multiple choice, checkboxes, number, email, phone or date — and the public form renders exactly that control (lists and choices use the options you configure). In the editor you can rename, change the type, reorder and delete any question.
  • Location / Google Meet: in person, a manual link, or an automatically generated Meet link.
  • Address / location instructions: for in-person, phone or custom locations, fill in the address (or the link/instructions). It goes into the invite, the confirmation message, the .ics file and the Google event. Meet needs none — the link is generated on its own.
  • Customer picks the location: when the event type offers two or more location options, the page shows a picker to whoever is booking. If the customer picks Google Meet, the video-call link is generated automatically. With a single option, the event type's fixed location applies.
  • Phone / WhatsApp: a field on the public form. When filled in, the customer also gets the confirmation and reminders over WhatsApp; left blank, everything still arrives by email. You can tick "require phone" on the event type — the booking is then only accepted with a valid number, including for callers hitting the API directly.
  • The number is always kept: the WhatsApp number typed in is written to the contact even when that contact already exists. If the contact already has a different number, the old one stays as the identity and the new one is recorded on the profile — nothing the customer types is discarded.
  • Extra guests: enable it to let the customer add other people to the appointment. You set the guest limit; each guest becomes an attendee and receives the Google invite.
  • Booking side-effects: conversation, task, CRM deal and confirmation email — per event type.
  • Distribution across agents: round-robin or collective when there's more than one host.
  • Payment (optional): require payment to confirm, or just hold the slot until payment (depends on the Payments module).

Use cases

  • Put the booking link in your Instagram bio or email signature.
  • Drop the link mid-conversation on WhatsApp so the customer can book a demo.
  • Take paid bookings (consultations, mentoring) confirmed only after payment.
  • Automatically distribute bookings across the agents of a team.

Tips, limits & best practices

  • The page is unauthenticated and safe: it shows only free slots, never the details of other bookings.
  • Keep intake questions short to reduce drop-off.
  • The phone number is optional, but worth it: with it the customer gets the confirmation and reminders over WhatsApp, which cuts no-shows. Without it nothing is lost — the email is still sent.
  • Only offer a location choice with options you can genuinely honour: everything ticked on the event type shows up for the customer.
  • Check the time zone — the page shows times in the correct zone for the customer.
  • Every confirmed booking becomes a complete record: use the side-effects (conversation, task, deal) so you don't lose the follow-up.

Troubleshooting

  • The page shows no slots: confirm availability, notice rules and buffers on the event type — there may be no free windows in the period.
  • The customer didn't get the confirmation: check the email entered and whether the confirmation email is on for that event type.
  • The booking didn't create a conversation/task/deal: check that those side-effects are enabled on the event type.
  • Payment didn't confirm the slot: confirm the Payments module is active and the payment was completed — the slot is held until confirmation.

See also