Online booking systems for small business

A booking system built around your diary.

Customers choose a service and time without calling. You keep one dependable diary, receive the useful details and automate the routine messages. A focused appointment system is usually £700 - £1,200 and can be added to an existing or new website.

Try the booking demoChoose the right setup

No platform commission. Deposits, reminders and connections are scoped around the actual workflow.

One dependable diaryconnected route
TodayTuesday
09:30Cut and finish
11:00Consultation
13:30Booked online
BookingDiaryReminder

One record moves through the whole journey.

24/7customers can request or book
0%commission charged by Ernest
Onesource of availability
Yourscustomer and booking records

Try it without signing up

Customer on the left. Your useful record on the right.

Choose a business and a time, then confirm the pretend booking. Nothing is sent or stored. The owner panel shows what the system would prepare behind the scenes.

Interactive example
01
Customer viewNorth Street Studio
Service

Cut and finish

45 minutes·£38

Maya

Choose a day

Choose a time

£10 depositReady to confirm
02
Owner viewWhat arrives
waiting

Complete the customer side.

The booking record, payment state and automated actions will appear here.

What the system removes

The booking is simple. The loose ends are expensive.

While you are working

Missed calls

A customer can choose the next action instead of trying another business.

Before the appointment

No-shows

Deposits and well-timed reminders make the commitment visible.

Across the team

Diary clashes

Availability comes from one agreed source, with buffers and blocked time tested.

After every booking

Repeated admin

Confirmations, calendar details and routine follow-up stop being copied by hand.

One record, start to finish

The customer sees choice. You see control.

The exact steps change with the business. The dependable pattern does not.

Availability must come from one source. If an existing calendar or practice system cannot connect safely, that limit is identified before it is promised.

  1. 01
    Choose

    Service, person and time

    Durations, buffers, locations, capacity and blocked time shape what can be selected.

  2. 02
    Commit

    Details and optional payment

    Collect only what is useful. Add a deposit, full payment or card hold when the agreed provider supports it.

  3. 03
    Confirm

    Both sides know what happens

    The customer receives a clear confirmation and your diary or working record updates.

  4. 04
    Follow through

    Reminder, move and cancel

    Routine messages and secure self-service links reduce calls without losing control.

Choose the smallest dependable setup

Keep, connect or build.

The right answer depends on where availability and customer records already live. A new system should remove work, not create a second diary for staff to remember.

01You already have a provider that works

Connect it cleanly

Keep the dependable diary and improve the website route into it through a supported link, embed or API.

Best when staff already trust the current system.
02The need is focused and the website is sound

Build it into the website

Own the booking route, fields and records without renting a large platform for a small job.

Best for one clear booking workflow.
03The team needs private workflows

Build a custom app

Add staff logins, permissions, internal notes, multiple locations, reporting or bespoke allocation rules.

Best when the diary is only one part of the process.

Different businesses, different rules

Same booking principle. A workflow that fits.

Salon appointment booking system

Services, durations, staff choice, deposits, blocked time and reminders, with the client list under your control.

See salon website work

Clinic appointment booking system

Treatment types, practitioners, reminders and agreed pre-visit forms, with a clear boundary before the clinical record.

See clinic website work

Service visits and consultations

Postcode rules, arrival windows, travel buffers, useful enquiry details and assignment to the right person.

See websites for trades

Connections without guesswork

The connection is checked before it is sold.

An integration is only dependable when the provider exposes the right data and actions. Ernest checks documentation, account access, limits and failure behaviour before confirming the route.

Google or Outlook calendarStripe, PayPal or another payment providerBooking systemCRM or customer recordEmail, SMS or WhatsApp route

API, embed, authorised export or direct link chosen deliberately

Double-booking and simultaneous requests tested where live availability is promised

A manual fallback defined for provider failure

A working system on this website

Not a mock-up. A real booking route.

The call request on the Contact page is built in-house. It stores a private booking record before sending mail, prevents accidental duplicate requests, provides calendar files and supports secure rescheduling or cancellation.

It deliberately asks for a preferred day and time band rather than pretending to show live availability. That is the correct workflow for this business. A client system can use true slot inventory where the agreed diary supports it.

See the working call booking
  1. 01
    FirstPrivate record stored

    A mail failure cannot silently lose the request.

  2. 02
    ThenConfirmation and calendar

    Both sides receive a clear summary and usable event details.

  3. 03
    AfterwardsMove or cancel securely

    The same record updates rather than creating a duplicate.

Booking system price

A range with visible reasons.

The range covers a focused appointment route. The written proposal confirms the exact diary, messages, payment behaviour and connections before the build starts.

See all website and system prices
Typical one-off build£700 - £1,200usually 1 to 3 weeks
  • Service, staff, location and duration rules
  • Customer booking and confirmation route
  • Owner record and tested daily workflow
  • Launch, training and practical handover

Price rises with multiple locations, complex availability, staff permissions, migration, payment rules, SMS volume or closed third-party systems.

Standalone support£25 - £45/moorRun Growthincluded in £199/mo

Support is optional. External calendar, payment, SMS or messaging providers may charge their own fees directly.

Before the booking build

Booking system questions.

Does the booking system sync with Google Calendar or Outlook?

It can when the chosen calendar and account provide a dependable connection. I check whether the link is one-way or two-way, how blocked time is represented and what happens if the provider is unavailable before promising live synchronisation.

What stops two people booking the same time?

A true slot system checks one authoritative availability source when the customer confirms. I test simultaneous requests, service duration, buffers, staff calendars and blocked time. If the current provider cannot expose availability safely, I will not create a second diary and call it synchronised.

Can it send automatic reminders?

Yes. Email reminders can be built into the route, and SMS or messaging can be added through a suitable provider. The timing, wording, consent and failed-delivery behaviour are agreed rather than left as a generic default.

Will I need to replace the booking provider I already use?

Not if it works and exposes a reliable route. I can keep it and improve the website connection through an authorised link, embed or API. Replacement makes sense only when the current tool causes the problem or cannot support the required workflow.

Can customers move or cancel their own appointments?

Yes, when self-service is part of the agreed build. Secure links can update the same booking record, apply notice rules and release availability without asking staff to copy the change into another system.

Can existing customers and future appointments be migrated?

Sometimes. It depends on the export, API access, field quality and permission to use the records. I inspect the source and map a test import before including migration in the proposal. A closed provider may limit what can be moved.

Bring the diary, not a feature list

Show Ernest how a booking works today.

The first conversation maps the real services, people, availability and follow-up. You will know whether to keep, connect or replace the current setup before a build is proposed.

Discuss your booking workflowExplore every system and add-on Email or telephone only. No obligation and no platform sales pitch.
Book a free call WhatsApp