What Calendly is for here
Calendly gives you event types with their own durations, locations and questions, a scheduling page on Calendly's domain, embeddable versions of that page, direct links to a single event type, confirmations and reminders, and connections to Google, Outlook and Microsoft 365 calendars. Paid plans add payment collection and workflow messages. Acuity does a similar job with a little more of the intake and package handling built in.
On a life events site it serves exactly one visitor: the person planning ahead. Pre-need enquiries, will and power of attorney appointments, memorial consultations, celebrant meetings with a family who has already chosen. It is not for the bereaved family in the first hours, and it should never appear beside the urgent number.
The performance question is where the embed goes. The answer: on one page, and never on every page.
The rule
Nothing from Calendly loads until the visitor is on the booking page. The planning ahead page, the wills page, the memorials page and the price list are for reading; they carry a button that opens the booking page with the right appointment already selected.
The booking page
A plain URL such as /book-a-consultation, with three things: one line saying what the appointment is and that there is no obligation, the embed, and the phone number for anyone who would rather speak first.
Reserve the height so the page does not jump when Calendly loads, and tell the browser about the domain early:
<link rel="preconnect" href="https://assets.calendly.com">
<div class="booking" style="min-height: 720px">
<div
class="calendly-inline-widget"
data-url="https://calendly.com/your-practice/consultation"
style="min-width:320px;height:760px"></div>
<script
src="https://assets.calendly.com/assets/external/widget.js"
async></script>
</div>Load the widget script only on this page. Calendly also offers popup buttons and popup text triggers; avoid both on this kind of site, because a booking window that opens over the page is the sort of interruption a bereaved visitor should never meet. If you use the popup anywhere, use it on the planning ahead page only, triggered by a deliberate tap.
Deep links from the pages that matter
Each event type has its own URL, so the button on each page opens the right one:
- Planning ahead and pre-paid plans, to the pre-need consultation.
- The wills page, the power of attorney page and the trusts page, each to the matching appointment on a will writing practice site, with the fixed fee stated beside the button.
- Memorials and inscriptions, to the showroom or home visit consultation on a memorial mason site.
- The family enquiry route on a celebrant site, once the family has decided.
The visitor who has read about lasting powers of attorney should see that appointment, not a menu of eight.
Configure Calendly first
- Event types with honest durations, and separate types for a home visit, an office appointment and an online meeting. Home visits matter here more than in most sectors, because many clients are older or unwell.
- Location details spelled out, including what happens if it is at their home.
- Two or three questions at booking, no more. Do not ask a bereaved or elderly person for a history in a form.
- Buffers and minimum notice, so nobody books an appointment for an hour's time.
- Confirmation and reminder messages rewritten in your voice, with the address, what to bring, and how to change the appointment.
- Calendar connected, so double bookings cannot happen.
- A redirect after booking to a thank-you page on your own domain.
Book every event type yourself from a phone before wiring the site.
The thank-you page
Point Calendly's redirect at /book-a-consultation/thanks, where the visitor reads what happens next, what to bring, and the number for anything before then. Without the redirect the booking finishes on Calendly's domain and your site never knows it happened.
Privacy
Booking data about wills, funerals and pre-need arrangements is sensitive. Keep the questions minimal, check where the tool stores data and whether that matters where you work, name the tool in your privacy notice, and make sure the confirmation email does not put anything into an inbox the client might share. Confirm the current position on data handling with the vendor rather than assuming.
Tracking
A booking_click event on every button with the page and event type, a booking_complete event on the thank-you page, and Calendly's own reporting for bookings by type. Monthly, read which page produced each booking. It usually tells you which service page to expand.
Monthly check
From a phone, on the home page and one service page: tap the button, complete a booking for each event type, confirm the confirmation and reminder arrive, the calendar blocks the slot and the thank-you page loads. Booking tools change their embed code; find out before a client does.
Common mistakes
- The widget script on every page, slowing the site for the many who are only reading.
- A booking button beside the twenty-four hour number, offering an appointment to someone whose relative died an hour ago.
- One generic event type with no pre-selection.
- Intake questions that read like a form at a bank.
- No redirect, so nothing is counted.
Where this sits
Calendly and Acuity are the tools we wire into funeral and life events websites most often, on one booking page with deep links from the planning ahead and document pages, kept well away from the urgent contact route. The booking tool runs the diary; the site gets the right person to it in one tap.