iTAB — a specialist consultation service
iTAB is a health and wellness store on the Russian market: supplements, lab discounts, expert content. I designed the consultation service for it: the mobile app first, then the web version, which is live. Specialists get a dashboard, a schedule and an application form that lists them in the catalog. Clients find, book and pay without leaving the store.
- Platforms
- Mobile app and web
- Roles
- Specialist and client, one account
- Outcome
- Web service shipped
Problem
iTAB sold supplements, but the people who recommend them — nutritionists, GPs, preventive-medicine doctors — lived outside the app. A client who wanted advice left for a messenger or a clinic, and the recommendation came back as a screenshot at best. The store had no way to host a consultation, and a specialist had no reason to bring clients into it.
Task
Design a consultation service inside the existing app: a way for specialists to get listed and paid, a way for clients to find, book and pay for a consultation, and everything in between: schedules, confirmations, cancellations, chat. It had to work as one account with two contexts, not a second app.
Users
Two roles with different needs. A specialist wants clients and as little paperwork as possible, but the platform can only pay them once their legal status and qualifications check out. A client wants to trust a stranger with a health question, so credentials, price and the next free slot come before anything else. I worked both roles out with the PM.
Solution
I designed a new consultation section inside the existing account. Specialists apply and manage their schedules and consultations there; clients find a specialist, book and pay.
1. Getting a specialist into the catalog
The entry point is the application form. It opens with the reasons to fill it in: recommendations for clients, a steady stream of clients, a payout every month — and a promise that it takes fifteen minutes. The form is cut into short steps with a progress bar. Closing it offers to keep the progress.
The order of the steps is the platform’s: without a registered employment status it cannot pay a specialist, so the form asks for that before the catalog ever shows them. The result goes to moderation and comes back within a working day.
The form is also where the specialist builds the storefront: they tick what they run — consultations, patient follow-up, a lab-results review — and price each line. The next step asks the format: online, in person at an address, or in person only. Those answers become the catalog card and the filters people search by.
2. One account, two contexts
A specialist is also a customer of the store, so the dashboard is a second context of the same account, not a second login. Before the form is submitted it holds one call to action and the referral code; after moderation it gains consultations, the schedule and recommendations, and a single button switches back to the client profile with its orders and appointments.
The dashboard also holds the partner program. Specialists bring clients into the store through a personal promo code: the client gets a discount, the specialist gets cashback on every order and a bonus once the month crosses a threshold. The code sits in the dashboard next to consultations.
3. Finding and booking a specialist
On the client side the service works like the rest of the store: a strip of specialties, sorting and filters for format, price and experience. The specialist card puts credentials, patient types, the next free slots and the price above the fold.
The card leaves the rating off: at launch nobody has reviews yet, and empty stars would spend the trust the card exists to collect. The highest qualification category, years of practice, patient types and the next free slot do that work instead — what a specialist has from day one.
Booking is date, time and format. Then a checkout with a comment for the doctor, the terms of service and the cancellation rule. Payment closes with a sheet that leads to the client’s consultations. The store home carries the new section next to the products.
4. Two clocks, one appointment
iTAB sells across a country eleven time zones wide, so a consultation has two clocks: the client’s and the specialist’s. The client picks a slot in their own zone, and the list says which zone that is. The specialist builds the schedule in theirs, under a line that says clients see their own time. Checkout is where the two meet: it prints both, 17:00 for the client and 10:00 in Moscow for the doctor.
A client may travel between booking and the appointment. The appointment keeps the moment it was booked for and shows it in the client’s current zone.
5. Running consultations
For the specialist the service is a schedule and a list. The schedule is set up in two steps: pick the dates open for booking, then the slots for each day. A repeat option covers a regular week. The list separates planned consultations from completed ones. A planned one can be confirmed, taken to chat or canceled with a reason the client receives.
Chat sits next to the booking. Moving a consultation is a message, not a phone call outside the app.
Alongside the main flow I designed the states a service lands in during its first weeks. All are built from the existing components and content. The riskiest: a form returned for fixes, a date with no free time, a slot already booked that cannot simply be removed.
6. The web version
Result
An extension of the store, not a second product: the service reuses the existing account, the catalog’s patterns and checkout instead of another login and a separate flow.
Mobile comes later: the mobile service was postponed, and its logic went into the web service, which I also designed.