WReservation

How to set up online appointment scheduling

When booking depends on a phone line and one person, a business's opening hours shrink to its reception hours. This page covers where the booking flow breaks down and how to move to an arrangement where customers book themselves, in the WApps business management ecosystem.

Start your 30-day free trial

Web based·One WApps account·4 key outcomes·Page updated: 26 July 2026

Interface previewWReservation / WApps

Try it now:Pick a service, tap one of the open slots, and create the booking.

WApps / WReservation1 booking awaiting approval

New booking

Open slots are calculated from service duration, buffers and working hours.

Service

Consultation45 min · ₺750

Provider

EKTeam member 1

Open slots · 31 Jul3 open

Struck-through slots are taken — no double booking.

What is an online appointment system?

An online appointment system is web-based software where customers see open slots and book themselves without calling. Availability is calculated from service duration, staff working hours and existing bookings. The moment a booking is made it lands on the calendar and a confirmation or reminder goes out. Its purpose is not to digitise the appointment book but to take booking off one person's shoulders.

Problem and approach

The appointment book lives on a phone and in one head

Bookings arrive by phone, over WhatsApp and at the door, and they never reach the same book at the same time. Two records land on the same slot, and once staff change, who is free when survives only in one person's memory. Requests that come in after hours wait until morning, and some never come back. Because no-shows are not recorded as such, the real cost of empty slots stays invisible.

Target flow: customers book themselvesTarget flow: availability is calculated, not rememberedTarget flow: staff and resources tracked separately

Impact on the workflow

Target flow: customers book themselves

Open slots are visible on a shared page; bookings can be made outside working hours and phone traffic drops.

Target flow: availability is calculated, not remembered

Service duration, buffers and working hours are defined, so a conflicting slot is never offered in the first place.

Target flow: staff and resources tracked separately

Availability is set per person or per room, preventing two staff members from booking the same room.

Target flow: no-shows on the record

Implementation notes

WReservation is built for this flow

Service and duration definitions, staff/resource availability, a customer self-service booking page and booking states are built into WReservation.

What should you measure?

Four numbers are enough here: utilisation (booked hours / open hours), no-show rate, the share of bookings made through self-service, and average duration per service. All four fall out of the booking record itself and need no separate work.

Work it out with your own numbers

Try it with your figures: if you open S hours a day and B of them are booked, utilisation is B/S. With a no-show rate of N, the hours actually lost are B×N; multiplying that by the service price turns the value of a reminder message into a number. What matters is not the estimate but that no-shows are marked as their own state.

What setup this runs on

This flow is built with WReservation, and the order matters: define services with duration and price first, then staff or room availability and working hours, and share the booking page last. Decide up front whether bookings confirm instantly or wait for approval — approval cuts phone traffic but makes the flow depend on your response time.

Continue exploring

Next step