A meeting type is one bookable thing. A discovery call, a demo, a support session. Everything a visitor sees follows from how you set it up.
The basics
Title. What it is called on the booking page. Write it from the visitor's side: "Intro call" beats "Discovery (outbound)".
Slug. The last part of the booking link. Short, readable, permanent. Changing it later breaks every link you have already shared.
Description. A sentence about what the meeting is for. Worth writing. It is the only thing telling somebody whether they picked the right option.
Duration. How long the meeting runs.
Thirty minutes is the default most people should use. Sixty is a commitment that visibly reduces bookings, and fifteen is right for a triage call and too short for a first conversation.
Duration, honestly
The length you choose is the length the visitor commits to, and it is also a signal about what the meeting is.
Fifteen minutes reads as a triage or a quick answer. Too short for anything exploratory.
Thirty is the default and the right answer for most first conversations.
Sixty reads as a workshop. Measurably fewer people book one, and the ones who do arrive more committed.
Pick for the meeting you actually want rather than the one you can imagine. A thirty-minute call that regularly overruns is better handled by adding a buffer than by making the slot an hour.
Protecting your day
Three settings decide how much of your time this can consume.
Buffer after adds a gap following each booking, so you are not walking out of one call into another. Ten or fifteen minutes is usually right, and it is the single most valuable setting here.
Maximum bookings per day caps how many can be taken. Without it, one busy day can consume everything.
Availability, which is set separately and covered in its own piece.
The combination is what stops a public booking link becoming a way for strangers to fill your week.
Description, briefly
One or two sentences, from the visitor's side, saying what the meeting is for and what they will leave with.
It is the only text distinguishing two options on a page, and it is the thing a hesitant visitor reads before committing thirty minutes. Leaving it blank is the most common configuration mistake here and the easiest to fix.
Where the meeting happens
Four choices.
An address, for meeting in person.
A Zoom link you provide.
Microsoft Teams, generated automatically for the booking.
A calendar entry without a location, when the arrangement is understood.
The automatically generated option is the one to prefer where it applies, because a link created per booking cannot be the wrong link, which a pasted one occasionally is.
Who it is with
A meeting type belongs to a staff member, and availability follows that person.
Distribution across several people is not built yet. Pooled team booking is one of the sections showing a "coming next" panel. Until it lands, several people each need their own meeting type, and the practical arrangement is one link each rather than one shared link.
What to ask before the meeting
Guest emails lets the booker add colleagues, who are invited too. Worth enabling for anything where more than one person on their side will attend, since it saves a round of forwarding.
Require a phone number adds a mandatory field. Enable it where you genuinely need one, and not otherwise: every required field costs some proportion of bookings, and a phone number you never call is a pure cost.
The context step is the substantial one, and it has its own piece.
Confirming
Auto-confirm books the slot immediately.
Manual holds it until you accept.
Auto-confirm is right for most things. A visitor who books and then waits to hear whether it counted has been given something to worry about, and a proportion of them will book elsewhere.
Manual is right when you genuinely need to vet, and when you will actually respond within the hour. Manual confirmation with a slow response is worse than no booking page.
Internal meeting types
A meeting type can be marked internal, which keeps it off the public listing while its link still works.
Useful for a meeting you only ever share deliberately: an escalation call for existing customers, or an interview slot. It is a soft privacy measure, not a security control, since anybody with the link can still book.
Campaign attribution
A meeting type can be attributed to a marketing campaign, so bookings through it count toward that campaign's results.
Worth setting whenever a booking link exists because of a specific campaign. It is the difference between knowing that a campaign generated traffic and knowing it generated meetings.
Guest emails
Letting the booker add colleagues is off by default and worth switching on for anything where more than one person will attend from their side.
The alternative is what happens without it: they book, then forward the invitation, and the people who join are invisible to you until they appear on the call. With it, you know who is coming and can prepare accordingly.
It costs one optional field and it is the kind of small thing that separates a considered booking page from a generic one.
Editing one later
Changes take effect immediately for anybody who has not yet booked. Bookings already taken keep the terms they were made under, including the duration.
The exception is the slug. Changing it breaks every link already shared, and there is no redirect from the old address. Rename the title freely; leave the slug alone.
If you genuinely need a different slug, the safer route is a new meeting type, with the old one retired once its links have stopped being used.
A sensible first set
One. The meeting you have most.
Resist building five. Every additional option on a booking page is a decision imposed on a visitor, and a page with one clear choice converts better than a menu.
Add a second when you can name a meeting that genuinely differs in length, audience or purpose, rather than one that differs only in who it is with.
Did this answer your question?
No, ask a person