ScenarioCustom web app Medical practice

A front desk that no longer lives on the phone.

Several specialists' schedules managed by hand and mornings on the phone: online booking that is simple for patients and safe for health data.

This week’s scheduleCardiology Mon09:0009:3010:3011:0012:00Tue09:0009:3010:3011:0012:00Wed09:0009:3010:3011:0012:00Thu09:0009:3010:3011:0012:00Fri09:0009:3010:3011:0012:00 ReminderTomorrow at 10:30
Web appBookingsHealth data privacy
Typical profile
Multi-specialty practice with several specialists
Typical duration
10–12 weeks
Investment
from €3,500 + VAT
Services
Web app

What a scenario isScenarios are realistic examples based on the projects we handle most often: they show how we work, they don't name clients and they don't report results. We're happy to talk through real case studies on a call, respecting our clients' confidentiality.

The point of departure.

The scenario: a multi-specialty practice with several specialists, each with different hours, visit lengths and habits. Almost all bookings go through the phone, the front desk spends most of the morning setting and moving appointments, and many visits are missed because patients forget.

Off-the-shelf solutions don't fit the way the practice really works, and in healthcare it isn't enough for it just to work: patient data requires precise rules on access, consent and retention.

Sound familiar?
  • The front desk spends most of the morning on the phone.
  • The various specialists' schedules are managed by hand or in different tools.
  • Many visits are missed because patients forget.
  • Off-the-shelf solutions don't fit the way you work.

How we approached it.

  1. Observe before designing

    A few hours at the front desk are worth more than any requirements document: that's where the exceptions emerge, like follow-up visits with different lengths or slots the doctor moves at the last minute.

  2. Book in a minute

    Patients choose the specialist, visit type and a free slot, and log in with an email link, with no password to remember. Designed for people who aren't comfortable with digital tools too.

  3. Reminders and waiting lists

    Automatic reminders before the visit, one-click cancellation and freed slots offered right away to people waiting.

  4. Privacy designed in from the start

    Explicit consent, an access log, retention periods and the right to erasure built into the data structure, not added at the end. A gradual rollout, one specialist at a time.

  5. Front-desk panel

    A single view of every schedule, with reschedules, urgent cases and phone bookings on the same calendar patients use online.

  6. Testing with real cases

    Before launch we test dozens of real situations: long visits, last-minute cancellations, patients without email, changes to the doctor's schedule.

How the work is spread outTypical timeline in weeks · 10–12 weeks
Observation and requirementsWk 1–2
Design and prototypeWk 3–4
DevelopmentWk 5–10
Gradual rolloutWk 11–12

Everything we deliver.

  • Booking web app for patients, on phone and computer
  • Per-specialist schedules with different durations and rules
  • Passwordless login via email link
  • Automatic reminders and waiting list
  • Front-desk panel to handle reschedules and urgent cases
  • Health data privacy built into the data structure

The tools and why we choose them

Custom web app
It adapts to the practice's real rules instead of forcing the practice to adapt.
Magic link login
No password to remember: simpler for less tech-savvy patients too.
Scheduled notifications
Reliable reminders and slot release, verified with automated tests.
Access log
Who saw what and when: a requirement for health data.

How we know if it works.

Before we start, we set the indicators and the starting point together, so results are read from data and not impressions.

  • Online bookings

    Share of appointments booked through the site versus by phone.

  • Missed visits

    The effect of reminders on no-shows.

  • Calls to the front desk

    How much time is freed up for the work that really needs a person.

  • Patient satisfaction

    A short questionnaire after the visit.

Three lessons from projects like this.

  1. Observe before designing

    The most important exceptions emerge from watching the front desk at work, not from reading requirements.

  2. Lowering the barrier to entry

    Removing the password matters more than any advanced feature for people who rarely use digital tools.

  3. Start one department at a time

    A gradual rollout brings out special cases before they affect the whole practice.

The questions about projects like this.

If yours is not here, write to us: we will reply as soon as possible.

Is patient data safe?

The platform is built with explicit consent, an access log, encryption and defined retention periods, in line with GDPR rules for health data.

Does it integrate with the management software we use?

Often yes, if the management software offers a way to connect. We check it during the analysis.

And people who prefer to call?

They can keep doing so: the front desk uses the same schedule, so online and phone bookings never overlap.

How much does a web app like this cost?

A custom web app starts at €3,500 + VAT; the quote depends on specialists, rules and integrations.

If you feel
the time is right,
it probably is.

Tell us about your project: the assistant prepares the brief in two minutes, then a person from the team replies. No automatic quotes.

MBCBMCThe Nalu team, here for you