Your own booking domain

Serve your booking pages on a hostname you own, such as book.yourdomain.com, instead of your Calemander address.

By default your booking pages live at yourworkspace.calemander.com. A booking domain puts the same pages on a subdomain of your own website. The page, the prices, the theme and the booking itself are unchanged — the address in the browser bar is yours, and so is the address in the confirmation email, the reminder, the calendar invite and the receipt. You do not rewrite any of those: once the domain is live, every new link we send carries it, including the single-use links you create for one person.

What you need

A Pro or Studio workspace. Pro includes one booking domain and Studio includes three. Free includes none.
A domain you already own, and access to wherever its DNS records are edited.
A subdomain to give it, such as book, schedule or appointments. A root domain like yourdomain.com cannot be used yet; that is usually where your own website lives.

Adding your domain

Open Dashboard → Settings → Booking domain and type the hostname you want, for example book.yourdomain.com.
The page then shows one DNS record to add at your domain registrar or DNS host:

CNAME book → customers.calemander.com

The page shows the same four fields your DNS host asks for — type CNAME, the name (book), the value (customers.calemander.com) and DNS only for the proxy setting — with a button that copies the record.
If your DNS is at Cloudflare, leave the record unproxied. The cloud icon next to it must be grey, not orange. A proxied record puts your own Cloudflare account in front of ours and the certificate cannot be issued. Every other DNS host adds a plain CNAME with no such setting, and nothing extra is needed there.
Once that record resolves, the certificate for your hostname is issued at the edge, and the status moves from Waiting for DNS to Issuing certificate to Live. The page shows the current status and the time it was last checked, and you can re-check it yourself with Check now.

No certificate is installed anywhere, and there is nothing to renew. On the first domain we set up this way, the certificate was issued a few minutes after the CNAME record started resolving. How long that takes for you depends on how quickly your DNS host publishes the record, which is outside what we can see.

Occasionally the certificate cannot be validated from the DNS record alone, and the page then shows a second record — a TXT record with a long name and value — to add alongside the CNAME. If it is not shown, it is not needed.

Checks keep running for seven days. If the DNS record has not appeared by then, the domain is marked Not set up and the remedy is to remove it and add it again.

What stays on your Calemander address

Only the pages your clients see move. These stay on yourworkspace.calemander.com, and opening one on your booking domain sends you back there:

Your dashboard, sign-in and sign-up.
The API and anything a webhook or integration calls.
Door screens. A paired tablet stores its pairing against the address it was paired on, so the pairing instructions keep naming your Calemander address on purpose.
The “connect your calendar” option on the booking page, which needs a sign-in that can only happen on a Calemander address. It is hidden on a booking domain rather than shown and then failing.

Links you have already sent

Your yourworkspace.calemander.com address keeps working. Every cancel, reschedule and manage link is tied to your workspace rather than to a hostname, so links in emails you sent before adding the domain still open the right booking. New links use the booking domain.

Search engines are told that the booking domain is the address to list, so the same page on two addresses is treated as one page.

Embedding on your own site

Booking pages refuse to be framed by another site, so you cannot put book.yourdomain.com in an <iframe> on your homepage. Use the embed snippet from Dashboard → Embed, which is built for that. Embedding your booking page covers it.

Two things to know about the hostname

HTTPS is enforced on it. Pages served on your booking domain carry a Strict-Transport-Security header with a one-year lifetime. It applies to that hostname alone and does not include subdomains, so it cannot affect www.yourdomain.com or anything else you run.
Analytics see one site, not two. Your Google Analytics property, if you have set one, records the booking domain as its own hostname. If your website and your booking domain should count as one journey, add the booking domain to that property's referral exclusion list in Google Analytics.

Removing it

Dashboard → Settings → Booking domain → Remove stops serving your pages on that hostname. Links already sent keep working, because they resolve through your Calemander address. You can then delete the CNAME record at your DNS host.

Embedding your booking page — putting it inside your own site.
Billing and plans — what each plan includes.

Last checked 2026-09-11.