Notify me

project overview

Fixing and improving a broken Notify Me flow across all Docplanner markets - spotted the opportunity while working on the core booking flow, escalated cross-team, drove the fix end-to-end.

project type

Product design

year

2026

my role

Senior Product Designer

client

Docplanner

Early results (Poland): 200 → 1,500 bookings/week from notifications · 1K → 10K sessions/week · 3× backend requests

What Notify Me is When a doctor's calendar is fully booked, patients can leave their email or phone number and get notified the moment a slot opens. It's the marketplace equivalent of a smart waitlist - a low-friction way to convert strong booking intent into a future booking when there's nothing to book right now.

The problem 89,000 patients clicked Notify Me in Poland in three months, a clear signal the demand is there. But the feature was quietly broken. In six markets, patients subscribed and received nothing. In Poland, notifications took up to an hour, so slots were often gone by the time patients clicked through. And the click-through landed on a single-slot flow or a dead end.

The problem 89,000 patients clicked Notify Me in Poland in three months, a clear signal the demand is there. But the feature was quietly broken. In six markets, patients subscribed and received nothing. In Poland, notifications took up to an hour, so slots were often gone by the time patients clicked through. And the click-through landed on a single-slot flow or a dead end.

How I approached it I noticed the broken exit path while auditing the booking flow, patients clicking through the notification email were hitting a dead-end config step. Rather than log a bug, I ran the diagnostic: what percentage of signups were converting, where in the chain were they dropping off, and which markets were functioning at all. The answer surfaced 89K signals leaking through a chain of small failures, silent notification jobs in six markets, hour-long delays where jobs did run, and a click-through that landed on a service config step instead of a bookable calendar. I built the business case around that leakage and got engineering, ops, and my manager to prioritize the initiative within 2 weeks.

How I approached it I noticed the broken exit path while auditing the booking flow, patients clicking through the notification email were hitting a dead-end config step. Rather than log a bug, I ran the diagnostic: what percentage of signups were converting, where in the chain were they dropping off, and which markets were functioning at all. The answer surfaced 89K signals leaking through a chain of small failures, silent notification jobs in six markets, hour-long delays where jobs did run, and a click-through that landed on a service config step instead of a bookable calendar. I built the business case around that leakage and got engineering, ops, and my manager to prioritize the initiative within 2 weeks.

Early results (Poland) · Backend requests: 8k → 24k/week · Sessions from notifications: 1k → 10k/week · Bookings from notifications: 200 → 1,500/week

other projects

other projects

other projects

Insurance configuration modal on laptop screen

Insurance System

UX/UI

Booking flow in mobile app

Booking flow

UX/UI

Patient app landing page on mobile screen

Cardo Health app

UX/UI & Design system