This is a structural placeholder for a real case study. Every number and detail below is illustrative only and must be replaced with the client’s actual figures, with their written approval, before this goes live.
The situation
A general practice clinic in Dhaka was taking every booking by phone. Two receptionists spent most of a shift on calls that were, in effect, the same conversation repeated: is there a slot today, what does it cost, do you take this insurance. Patients who called outside opening hours got no answer at all, and some simply booked with a different clinic instead.
What we built
- A WordPress site with a real online booking flow, so a patient can see available slots and confirm a visit without calling.
- WhatsApp as the confirmation and reminder channel, since that is where the clinic’s patients already were.
- A simple internal dashboard the front desk could actually use, instead of a generic booking plugin’s default admin screen.
What changed
[Placeholder — replace with real, client-approved figures] Online bookings accounted for a meaningful share of new appointments within the first month. Call volume at the front desk dropped enough that reception time could shift toward patients who were already in the building, rather than the phone.
Why this is the shape of the story we tell
“Bookings up, phone lines quieter” is the outcome. “We built a booking system” is just the deliverable. The design system this site follows is explicit on this point: case studies lead with the outcome, never the feature list — and no number appears here that has not been confirmed by the client in writing.