First: should customers book themselves?
Self-booking works well when appointments are predictable — fixed length, fixed location, no assessment needed. It works badly when:
- Job length depends on what the customer describes.
- Travel between jobs matters.
- Some requests need triage first (urgent versus routine).
- Specific skills or parts are needed.
In those cases, a booking request — customer suggests times, your team confirms — is often better. Say clearly on the page that it's a request.
Option 1: link to a booking page
A button on your site links to your booking tool's hosted page.
- Pros: simplest, no impact on your site's speed, the booking tool handles everything.
- Cons: customers leave your site; branding may differ.
- Good for: consultations, simple appointments, getting started.
Option 2: embed the scheduler
The booking tool's widget appears on a page of your site. Tools like Cal.com and Calendly document embedding options in their help pages (Cal.com docs, Calendly help centre).
- Pros: customers stay on your site; consistent experience.
- Cons: third-party scripts affect page speed and privacy; layout issues on small screens.
- Good for: businesses booking appointments frequently through the site.
- Check: mobile layout, page speed (see Core Web Vitals), and that your privacy notice mentions the tool.
Option 3: integrate with your systems
Bookings flow into your CRM, job management or calendar, with confirmations, reminders and internal tasks.
- Pros: no retyping; reminders and handoffs automated.
- Cons: more setup, more to test and maintain.
- Good for: businesses with steady booking volume and established processes.
- Check: reschedule and cancellation handling — see reschedules and timezones.
Decision table
| If… | Consider |
|---|---|
| Jobs need assessment first | A request form, not self-booking |
| You're testing whether customers will book online | A link |
| Booking is a main action on your site | An embed |
| You re-enter bookings into another system | Integration |
Settings that prevent problems
- Buffer time between appointments.
- A minimum notice period so nobody books an hour from now.
- Limits on how far ahead people can book.
- Clear timezone handling.
- Confirmation messages that say exactly what's been booked — see booking confirmations and reminders.
- An easy way to reschedule or cancel.
MendRev's approach
MendRev's own site uses a hosted booking link for consultations. On client sites, we can link or embed a booking tool you use; deeper integration with your other systems is scoped as a Business Automations project.
Questions
Is a booking request form different from online booking?
Yes. A request form collects a preferred time for your team to confirm; true online booking lets the customer pick a slot that's confirmed immediately. Be clear on your site which one you offer.
Will a booking embed slow my site?
It can, because it loads third-party scripts. Load it only on the page where it's needed, and test page speed on a phone.
Sources and further reading
- Cal.com docs cal.com
- Calendly help centre help.calendly.com
Official documentation changes. Check the current version before you rely on a rule, limit or setting.
Next step
See a site built around your real details.
Look at sample layouts (fictional previews, not client work), read published website pricing, or ask for a free concept preview.
Already happy with your site? Website Maintenance covers monitoring, a monthly form test, backups and edits.