What Calendly gives you
Calendly is the tool most practices reach for first, and for consultation booking it is a reasonable choice. You define event types, each with its own duration, availability, description and questions. It reads your Google, Outlook or Microsoft 365 calendar so it only offers slots you actually have. It can create the video link automatically through Zoom, Teams or Google Meet. It sends confirmations and reminders. Depending on your plan it can take payment through a connected provider, route visitors to different event types from a form, and apply workflow reminders. Check the specifics of your plan with Calendly before you build a flow that depends on one.
It offers three ways onto a website: an inline embed, a popup widget that floats on the page, and a popup triggered by a link or a button. Which one you pick, and where, is the whole performance question.
The rule
Nothing from Calendly loads until the visitor has decided to book. Service pages, team profiles and the home page are for reading, deciding and ranking. They link to booking. One page carries the embed.
The floating popup widget breaks this rule by design, because it loads Calendly's script on every page it is placed on, and on most practice sites it is placed on all of them. It also covers content on small screens. We do not use it.
The setup that works
One booking page. /book, carrying the inline embed, a one line reassurance, the phone number, and nothing else. No reviews widget, no gallery, no chat bubble. The embed is the only heavy thing on the page, which is fine, because everybody who reaches it wants it.
Reserve the height. Give the embed container a fixed height in CSS at each breakpoint so the page does not jump when the widget arrives. Layout shift on a booking page costs bookings.
Preconnect. A preconnect hint for Calendly's domain in the head of the booking page only, so the connection is warm by the time the script asks for it.
Load the script on that page only. Not in a global template. If your site loads it site wide, that is a fix worth making this week.
Everything else links. Every Book button elsewhere is a link to /book with parameters, not an embed.
Deep links from every page
This is where a practice site earns its keep. The visitor should never have to choose in the widget what the page already knows.
- A service page links to the event type that fits it, so the person reading about wills books the wills consultation.
- A team profile links to that person's own event type or scheduling link.
- The header and footer link to the general introductory call.
- An email signature or a newsletter links with campaign parameters so you can see which produced meetings.
Calendly supports URL parameters for prefilling the invitee name, email address and answers to your custom questions, and it passes UTM parameters through to the booking record. Use them. A client arriving from a service page should see their matter type already selected and only need to pick a time.
Configure Calendly before you wire it
- Two or three event types, not nine. An introductory call, a paid consultation, and one profession specific type if you need it.
- Availability windows that are deliberate. Two or three consultation blocks a week, not your whole diary.
- Minimum notice and buffers, so nobody books you in twenty minutes or back to back for three hours.
- Questions kept to five or six, including what it concerns, a sentence in their words, any deadline, and the other parties for a conflict check.
- A privacy link in the event description, since you are collecting personal information at this point.
- Payment connected where the consultation is chargeable. It ends no shows.
- Confirmation and reminder wording in your voice, saying what to have ready.
- Where the answers land. Into the inbox somebody watches, and into your practice system if it connects.
Keep sensitive material out of Calendly's question fields. Identity documents, financial statements and case papers go through a secure portal or your practice system, not a scheduling form.
When Calendly is the wrong tool
If you already run Clio Grow, Karbon, Intelliflo or a similar practice system, its own booking and intake will usually serve you better, because the booking becomes a record in the system rather than a calendar entry somebody retypes. If your firm lives in Microsoft 365, Microsoft Bookings may already be paid for and already on the right calendars. Calendly is the right answer when you want scheduling and nothing else, and it is a very good answer to that question.
Testing on phones
Safari and Chrome on iOS and Android, and inside the in app browsers of LinkedIn and Facebook, since a share of professional traffic arrives that way. Complete a real booking from a service page, from a team profile and from the header. Confirm the prefilled answers arrive, the reminder sends, the video link works and the entry lands in the right calendar. Then cancel it.
Tracking
Track a booking_click on every Book link with the page and event type as parameters, and count completed bookings on the confirmation redirect. Read it monthly against enquiries and calls, so you know which service pages are producing meetings rather than only visits.
Common mistakes
- The floating widget on every page.
- The embed dropped onto the home page, so the heaviest thing on the site loads for everybody.
- Nine event types, so the client has to choose your taxonomy.
- No height reserved, so the page jumps.
- No phone number beside the widget.
- Nobody testing after Calendly updates its embed code.
Where this sits
Calendly is one of the tools we wire into a professional services website most often, and this setup, one booking page, deep links from every service and profile, the phone alongside, and a monthly test, is the version that keeps the site fast and the diary filling.