What booking system does this website use?
Paste a URL and find out how a site takes bookings. Two very different answers are possible, and they lead to very different work: a third-party platform leaves the vendor's hostnames all over the page and can be named outright, while a custom-built booking flow leaves no vendor fingerprint at all and has to be inferred from structure. This hub explains both, lists every booking detector on this site, and is explicit about which answers are facts and which are inferences.
Third-party booking: named from a hostname
Most booking platforms are embedded rather than rebuilt: an iframe, a widget script, or a booking page hosted on the vendor's own domain. That means the vendor's hostname appears in the page you already downloaded — calendly.com, acuityscheduling.com, simplybook.me, setmore.com and so on. When that happens the answer is not a guess: it is a fact, and the detector names the platform and shows the matching URLs.
This is the common case, and it is also the case that matters commercially: the site owner is paying that vendor a monthly fee, and the booking flow inherits the vendor's load time, its cookie behaviour and its ceiling on customisation.
Custom-built booking: no fingerprint, only structure
A booking flow written directly into the site does not announce itself. There is no vendor hostname to match, which is exactly why a detector that only hunts brand names returns nothing useful here.
What remains are structural signals: a URL path such as /booking, /book-now, /appointment or /reserve; copy that says ``book an appointment'' or ``make a reservation''; a date or date-and-time input; a datepicker library (flatpickr, react-datepicker, Pikaday) instead of a plain text field; and a form whose action points back at the same site rather than out to a vendor. Together those make a custom build likely — not certain. Every such result on this site is labelled *likely custom-built* and lists the signals it used, so you can judge them yourself.
- Calendly— The default scheduling embed for sales calls and consultations.
- Cal.com— The open-source scheduling alternative, self-hostable.
- Acuity Scheduling— Appointment scheduling for service businesses, owned by Squarespace.
- SimplyBook.me— Booking platform common with salons, clinics and studios.
- Setmore— Free-tier appointment scheduling for small teams.
- Fresha— Salon and spa booking with its own marketplace.
- Booksy— Beauty and barber appointment marketplace.
- Mindbody— Fitness, wellness and studio scheduling.
- Square Appointments— Booking bundled with Square payments.
- Bookeo— Tours, classes and activity bookings.
- Appointy— Appointment software for services and education.
- Zoho Bookings— Scheduling inside the Zoho suite.
- HubSpot Meetings— Meeting links inside HubSpot's CRM.
- OpenTable— Restaurant reservations.
- ResDiary— Restaurant booking and table management.
- SevenRooms— Restaurant and hospitality reservations.
- Jinshuju 金数据— Chinese form and data collection tool, widely used for bookings and signups.
- MikeCRM 麦客— Chinese form and mini-CRM, common for enquiries and events.
- WJX 问卷星— Chinese survey and form platform.
- Tencent Survey 腾讯问卷— Tencent's survey and form tool.
- Youzan 有赞— Chinese commerce platform with built-in booking and appointments.
- Weimob 微盟— Chinese commerce and marketing platform with booking modules.
- Xiaoe 小鹅通— Chinese knowledge-commerce platform with course and session booking.
- Huodongxing 活动行— Chinese event registration and ticketing.
- Typeform— Conversational forms and enquiry flows.
- Jotform— Form builder often used for booking requests.
- Tally— Lightweight free form builder.
- Amelia— WordPress booking plugin — the site runs its own booking engine.
- Bookly— WordPress appointment plugin, often paired with WooCommerce.
- WooCommerce Bookings— Booking extension for WooCommerce stores.
- Easy!Appointments— Open-source self-hosted booking — custom-built but with a known engine.
Why the distinction changes the job
Third-party: the platform owns data, emails, calendar sync and often the payment flow. Performance work is limited to how and when the widget loads — you can defer it, lazy-load it, or replace an inline embed with a button, but you cannot make the vendor faster.
Custom: you own everything, so the fix can go all the way down to the API and the database. It also means the booking flow is part of the site's own performance and accessibility score, and nobody outside the project can fix it for you.
Estimating one as the other is a common and expensive mistake — which is why this is worth checking before quoting.
Forms and survey tools count too
Many businesses never buy a booking platform; they take enquiries through a form tool — Typeform, Jotform, Tally, Jinshuju, MikeCRM, WJX, Tencent Survey — and confirm by hand. Functionally that is the booking system, and the same hostname logic identifies it.
In these cases the page usually keeps the lead data in that tool, not in the website's own database. That is worth knowing before anyone promises CRM or reporting work.
If a booking detector hits, you have a named vendor and a fact. If none hits but the page has a booking path, a date picker or a local form, you have a likely custom build with listed signals — read them before quoting. If nothing at all appears, the site may take bookings somewhere the homepage does not link to; try the contact or services page.
Optimization help is available
Tell me your URL and what you want fixed — you get a clear scope, price and timeline.
To：[email protected] | Cc：[email protected]
