Loading…
Cancellation requests arrive in a staff chat with the customer's signed paperwork attached — except the link was usually dead by the time anyone clicked it. I replaced it with one that never expires and still can't be guessed.
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.
A policy isn't really sold when the customer pays — it's sold minutes later, when it's actually issued, long after the browser has closed. Our marketing numbers never saw that step, so I built the part that reports it back.
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.
On a fast connection, the site opened as a gray void for seconds, then images crawled in one by one. The fixes turned out to be small. The work was proving why every slow thing existed —because each one, it turned out, was somebody's earlier fix.
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.
We added a reason step with an optional PDF to our policy-cancellation wizard. My first upload design had two new endpoints, a new table, and a cleanup cron — what shipped has none of them. How walking the real user flow one more time made the feature smaller, safer, and done faster.
A three-day sprint on the gross.uz personal cabinet: switching it to a single trustworthy data source, finding policies users didn't know they had, and polishing the interface until it feels like an app instead of a website.