Booking enquiries or a live booking system: which do you need?
Choose an appointment enquiry when you need to review a request before confirming it. Use a live booking system when availability, staff and services can be reliably checked before a slot is reserved. An existing booking provider may already do that work for you.

An enquiry starts a conversation
A visitor chooses a service, provides a preferred date and shares their contact details. Your team reviews the request and confirms what is available. The website must make clear that the request is not yet a confirmed appointment; otherwise two people may believe they have booked the same slot.
This can suit a landscaping site visit, a bridal appointment with specific requirements, or an initial consultation where someone needs to review the details. Keep the first enquiry focused on what you actually need to reply. A general website enquiry should not ask visitors to send a full medical history.
An existing platform may be the simplest connection
If your business already manages services and staff in a booking platform, connecting the website to that system may preserve the diary you rely on. A clear booking link takes the customer to the provider. An embedded widget can keep part of the journey within your page, where the provider supports it.
Check the whole mobile experience, including the point where a visitor moves to the provider. Confirm whose branding they see, whether a login is needed, who sends the confirmation, and where a cancellation is managed. Provider subscriptions and fees remain separate from the cost of displaying a booking link.
Live availability needs rules and a source of truth
A confirmed booking system needs to know when the business is open, how long a service takes, which person or resource is available and whether another booking has taken the slot. It must handle changes and simultaneous requests consistently. These are backend requirements, not just calendar styling.
Deposits add payment and refund states. Reminders add delivery rules and customer communication choices. Staff calendars, recurring visits and rescheduling introduce more decisions. Write down the rules and agree the integration before treating these as standard website features.
- Where are available slots stored and updated?
- Who confirms, cancels and reschedules appointments?
- What happens when a payment fails or a slot is taken?
- Which system sends the customer confirmation?
- How does a staff member correct a booking or close a day?
Choose the smallest journey that does the job
Start with the process your team can support. If every appointment needs a conversation, an honest enquiry journey can be more useful than a calendar that implies instant confirmation. If you already operate a live diary, duplicating it in a second system can create unnecessary work.
Webora's £400 business website package includes an agreed booking or enquiry journey. Live calendar integrations, payment processing, reminders and custom administrative systems require scope confirmation. Our interactive booking example demonstrates service selection, preferred timing, contact details and review; it does not reserve a real appointment.
Tell us what you use now, what a customer needs to do and what your team should receive. We can then agree whether an enquiry, a booking link or an additional integration is appropriate.
Keep this comparison handy
| Journey | Customer outcome | Business responsibility |
|---|---|---|
| Appointment enquiry | A request awaiting confirmation | Review the request and contact the customer |
| Existing booking platform | Whatever the provider's booking rules support | Maintain the provider's diary, services and subscription |
| Custom live booking system | A reservation following the agreed availability rules | Maintain the scheduling rules, administration and integrations |