Loading…
Customers had to check three different places to find out what happened to their requests, and most gave up and phoned the call centre instead. I merged them into a single list where every request looks the same and shows exactly which step it is on.
The cabinet's "My family" form was four fields long and had a problem in every layer: you could add yourself as your own relative, it demanded an ID nobody remembers, impossible dates crashed it, errors ignored your language, the dropdown wouldn't close, and backspace didn't delete. This is the whole repair — backend rules, state-service integration, and frontend polish — of one deceptively simple form.
Booking a doctor on a corporate medical policy meant messaging a Telegram bot. I moved that into the cabinet — a five-step form that reaches the operators' group in seconds. The interesting part was deciding how little the browser is allowed to say.
Corporate medical insurance existed in people's accounts as a name and nothing else. I built the endpoint behind it and wired the cabinet to it, so the page now answers the questions people actually have: what's covered, how much has been spent, and what happens next.