I designed a new slot booking system where parents could choose their class time themselves, instead of getting a call from the ops team. My role included understanding the old flow, creating the new design, and making it easy to use.
TEAM
Product Designer with 1 Developer
TIMELINE
1 week
SKILLS
UX Research & Problem Framing, Problem solving, User testing & feedback iteration,
IMPACT
60% reduction in ops follow-up calls
3x faster user conversion
20% higher slot booking conversion
After enrolling in a CuriousJr course (via MLP), parents had no clue what came next. The system sent them to payment — and then... radio silence. and they wonder, “When does my child’s class start?”
There was no visible next step — only a phone call from the ops team to manually book slots. But here’s the issue:
Many ignored unknown numbers
Some expected automation
And others forgot entirely
Let parents book class
slots directly after payment
Eliminate dependency on
ops calls
Guide users smoothly into
the learning journey
Handle Edge Cases
Limited slot availability
Retry scenarios
(if users drop off)
Dynamic timing based on
days (e.g. Monday logic)
I didn’t redesign the system. I just spoke to the user. We added section as soon as user comes on the payment page.
Post-PG success, user is shown a “Book Your Slot” screen.
Available time slots shown, and there are three scenarios.
User can choose whatever date they want
Limited slot for particular day eg. 2 slots are available on Monday but on Tuesday all slots are available.
All slots are booked for Monday, then next day slots will appear. In this case Tuesday and Wednesday slot will appear.
60%
reduction in ops follow-up calls
3x
Faster user confirmation
20%
higher slot booking completion
within the same session
Why It Worked
Because we did three simple things:
Shifted responsibility from ops → product
Visualized clarity at the right moment
Handled edge cases without making the UI heavy