The AI Booking Page: A Scheduling Link That Doesn't Cost You the Hour
A normal booking link books your time. This one books the meeting — an AI persona takes the call, and you get the transcript, the scores, and the recording. Here's how to set one up in about five minutes.
Every scheduling link ever built solves the same problem: stop emailing about when. They're good at it, and they all share an assumption — the slot that gets booked is an hour of your life.
An AI booking page breaks that assumption. Someone picks a time, gets a calendar invite, joins the call, has a real conversation — and you're not in it. What arrives afterwards is a transcript, a scored analysis, and a recording.
Same familiar flow for the person booking. Completely different economics for you.
The three ways to get someone into a session
Most of the confusion here is people picking the wrong one, so start with this. There are three surfaces, and they're for different situations.
| URL shape | Who can use it | Use when | |
|---|---|---|---|
| Share link | waterr.ai/{username}/{scenario-slug} | Anyone with the link, if you allow it | Open-ended. Post it, embed it, send it to a list |
| Scheduled invite | waterr.ai/{username}/{scenario-name}/{invite-code} | One named participant, in one window | Fairness matters — interviews, assessments |
| Booking page | waterr.ai/{username}/b/{scenario-slug} | Anyone, at a time they choose | You want them to self-schedule |
The share link is the simplest: one URL per scenario, and a toggle. Turn "Allow anyone with link" on and anyone with the URL can start a session; leave it off and only participants you invite through Scheduling can use it. If the copy button is greyed out, that toggle is the reason.
Scheduled invites are the controlled version. You set a date and a 30-minute slot, optionally an expiry — 24 hours, 7 days — and optionally a maximum number of uses, which you'd set to 1 for a single attempt. Each participant gets an email with their own unique link, and every invite carries a status: Active, Scheduled, Expired, or Revoked. That's the shape you want for an assessment, because everyone gets the same window and one attempt.
The booking page is the one people ask for by name, because it's the shape they already know from every scheduling tool they've used.
How the booking page works
It runs on Cal.com. You connect your Cal.com account and the page uses your existing event types, which means the availability rules you've already set up carry over rather than needing to be rebuilt.
Setup, in order:
- Open the scenario's Settings tab.
- Enter your Cal.com API key to connect the account.
- Toggle Enable Booking Page on.
- Choose which Cal.com event type this scenario uses. Your available event types are pulled from your Cal.com account.
- Share the URL:
https://waterr.ai/{username}/b/{scenario-slug}— for example,https://waterr.ai/harshit/b/sales-discovery-call.
That's the whole thing. Five minutes if your Cal.com account already exists.
What the person booking sees
Worth walking through, because this is where trust is won or lost.
They land on the booking URL and see the scenario details and information about the AI persona they'll be speaking with — before they commit to a time, not after. They pick a slot from the embedded Cal.com calendar. They get a calendar invite containing the session link.
At the appointed time they open the link, see the welcome page with the persona's name and avatar, grant microphone access and optionally camera, and the conversation starts.
The disclosure sits in front of that: a consent modal before the device check, carrying a message you write in plain text or markdown, with "I understand" to proceed or "Cancel" to leave. Most people use it to state that the session is recorded, transcribed, and reviewed — which is a legal requirement in two-party-consent jurisdictions, not just good manners.
One honest caveat if you're in a regulated context: the consent click is enforced, but it isn't written to an auditable consent table. If you need formal records of who agreed to which version and when, plan to keep your own.
What you get back
The call ends and the pipeline runs. You get the transcript, the recording, and an analysis scoring the participant against the goals you set on the scenario — each goal scored on a scale, typically 1 to 10, with written feedback, an overall average, and transcript highlights tied to the goal each one supports.
If you're wiring this into something else, don't poll for it. Register a webhook endpoint and session.analysis_complete arrives with the analysis in the payload — goal_results, strengths, growth_areas, highlights — so your ATS or CRM gets a scorecard rather than a transcript to parse.
Three setups that work
Inbound discovery that qualifies itself. Put the booking page where "book a demo" goes today. The persona runs your discovery scenario — budget, timeline, current stack, what broke — and you show up to the second conversation already knowing. The prospect gets time immediately instead of waiting three days for a slot in your calendar.
First-round screening candidates self-schedule. The booking page goes in the job posting. Candidates pick a time that suits them, including outside your working hours, which is a real advantage across time zones. You review scorecards instead of running twenty half-hour calls. For a formal process where every candidate should get the same window and one attempt, use a scheduled invite instead — that's what it's for.
Customer feedback at the moment it's worth giving. Booking page linked from a milestone email or in-product moment. People are roughly ten times more expressive answering an AI than recording themselves cold into a webcam, because the friction of self-recording eats most of what they'd have said.
Frequently asked questions
Can people book a meeting with my AI instead of me? That's exactly what this is. They pick a slot, get a calendar invite, and join a session with your persona. Your calendar stays empty; the transcript, scores, and recording arrive when it's done.
Do I need a Cal.com account? Yes. The booking page is Cal.com-backed — you connect with an API key and select from your existing event types. If you'd rather not add Cal.com, use a share link for open access or scheduled invites for controlled ones. Both work without it.
What's the difference between the booking page and a scheduled invite? Who picks the time. On the booking page the participant self-schedules from your Cal.com availability. With a scheduled invite you set the slot, email a unique link, and control expiry and maximum uses. Self-serve versus assigned.
Can I use my own domain?
Yes, under white label. You pick a subdomain, add a CNAME pointing at custom.waterr.ai, and we configure SSL and routing — after which session links use yourdomain.com/... instead of waterr.ai/.... White label also covers the session interface, participant emails, embed widgets, and the end-of-session page.
What if the participant doesn't show up? No session runs and nothing is generated. Cal.com's own reminder and no-show settings apply, since it's handling the scheduling layer.
Can I run more than one booking page? Yes — the page is per scenario, with its own slug and its own Cal.com event type. A screening scenario and a discovery scenario are two pages with different personas, goals, and availability.
More on the delegation mechanic in send an agent, and the full setup in the booking page docs.