Put booking and meeting links on your own domain

Booking pages normally live at https://app.freesbe.net/b/dana. With a custom domain, every booking page in the workspace moves to your company’s own address, such as https://meetme.acme.com/dana, and so do the links guests get to join your meetings and the invite links you send. The pages look the same, and visitors never see app.freesbe.net. An owner or admin sets it up once; everyone’s links switch over by themselves.

Before you start

• Custom domains come with the Corporate and Enterprise plans. On another plan, Workspace settings → General → Custom domain says it requires the Corporate plan.
• Pick a subdomain you control, like meetme.acme.com or book.acme.com. A bare domain such as acme.com can’t be used, because its root can’t point somewhere else with a CNAME record.
• You, or whoever runs your company’s DNS, need to add one DNS record.

1. Add the domain

1. Open the workspace menu (the workspace name at the top of the sidebar) and choose Workspace settings, then Custom domain.
2. Type the domain, for example meetme.acme.com. Freesbe shows what the links will look like.
3. Click Add domain.

2. Add the DNS record

Freesbe shows the record to add. At your DNS provider, create a CNAME record:

Type	Name	Target
CNAME	meetme (your subdomain)	domains.freesbe.net

Some providers want the full name (meetme.acme.com), others only the part before your domain (meetme). If your provider offers to proxy or speed up the record, turn that off: it must be DNS only.

Freesbe checks every few minutes and gets the HTTPS certificate as soon as the record shows up, usually in a few minutes, sometimes up to an hour while DNS catches up. Click Check now to look straight away. If Freesbe shows a second, TXT record under Ownership record (only if asked), add it too: that’s only when the domain is already in use somewhere else or sits behind a CDN or proxy.

3. Check that it’s working

The status changes to Working. From then on:

• Everyone’s booking pages use the new address. Copy, Copy for email signature and the link preview card all use it. Old app.freesbe.net/b/… links keep working, so signatures people already sent don’t break.
• Guests’ meeting links use it too: invite emails, calendar invites, reminders and Copy link on a meeting point to https://meetme.acme.com/m/…. Members still get their usual meet.freesbe.net/… links, which take them into Freesbe signed in.
• Invite links you create from then on use it, for workspace invites and guest invites.

Keep the DNS record in place. It’s how visitors reach Freesbe and how the certificate renews every few months.

Tell the team

Nothing changes for them except the address: their pages in Meetings → Bookings show the new links, and the old ones still work. Someone who opens just the domain, without a name after it, sees a short page that tells them to ask for the person’s link. Nobody can sign in to Freesbe on the domain, and nothing else answers there.

If it doesn’t work

• Waiting for DNS for more than an hour. Check the record is a CNAME (not an A record), its target is exactly domains.freesbe.net, and it’s DNS only, not proxied.
• “A CAA record on the domain blocks the HTTPS certificate.” Ask whoever runs your DNS to allow Let’s Encrypt and Google Trust Services, or remove the CAA record.
• “That domain is already connected to Freesbe.” Another workspace uses it. Pick another subdomain, or email support@freesbe.net.

To move to another subdomain, click Remove domain and add the new one. Links on the old domain stop working right away, including meeting invites and invite links already sent with it, so send those again. A workspace has one custom domain.

See Custom domains for everything the domain shows.