Skip to content
All work
WebBots2023 · ~1 min read

Appointment booking for a children's clinic

Walk-in queueing replaced by time-slot booking: parents pick a free slot in Telegram, and a cancelled booking goes straight back into circulation.

# The problem

The clinic ran on a walk-in queue. Parents with small children waited an hour or more, arguments over who was next broke out at reception regularly, and there was no way to predict when you would be seen. Cancelling a visit was no better — the freed place simply went to waste.

# The solution

I built a booking system. A parent picks a free slot in the Telegram bot and comes at that time; cancelling returns the slot to the pool immediately, so the next person takes it instead of leaving a hole in the schedule. Doctors get a web panel with the schedule for the day, appointment statuses and report exports. The least trivial part turned out to be computing the available windows. A 25-minute slot has to be checked against existing bookings, overlaps with neighbouring appointments, doctor breaks and working hours — and give the same answer in the bot and in the panel. All availability logic lives on the backend: both clients ask for the same list of free windows, so booking two children into one slot is impossible even on simultaneous requests.

# The outcome

The system has been in production since 2023. Over the first half of 2025 it handled 2,396 bookings — around 15 a working day — with more than 1,300 patients on file. The walk-in queue and the arguments at reception are gone: parents know their exact time and come to it. In the same period 415 cancelled bookings went back into circulation instead of sitting as empty gaps in the schedule.

# How it works

  1. ParentPicks a free time in the bot instead of queueing on the day.
  2. Telegram botShows the open slots and takes the booking. Built together with an intern from the mockup the client supplied.
  3. DoctorRuns their own day and closes off time when there will be no appointments.
  4. Doctor panelA Vue 3 interface: schedule, working-day templates, breaks.
  5. API · GraphQLOne place for every booking rule: slot length, overlaps, cancellation.
  6. PostgreSQLBookings, schedules and history. A cancelled booking frees its slot rather than vanishing.
  7. RedisCache and supporting storage alongside the main database.

Dashed: not my work — platforms and the client’s own systems

Next project

AI answers during a live call

Need something similar?

Discuss the task