
«Poliklinika.ru 2.0»
Poliklinika.ru 2.0: how ASO and feedback work raised the app rating

Goal
We already covered how we relaunched the Poliklinika.ru app: we left third-party SDK limits behind, built our own architecture with a Middleware server, and created a scalable platform.
Technically everything worked. But the app’s potential as a digital channel and loyalty tool was still untapped:
happy users rarely left feedback — ratings stayed average
features improved usability, but communication with users was missing
there were no engaging mechanics for two-way feedback
We needed a system where feedback works for the product
What we did
Audited the review and ticket handling system
Consolidated all feedback channels into a shared inbox with the client
Set up ticket filtering by responsibility level
Launched a flexible trigger system for collecting ratings
Built a full interaction loop between the team, users, and the client

How we solved it
Support audit and setup
First we studied how users interact with store support and which issues they hit most often: registration, appointment cancellation, uploading lab results. Tickets originally went to email and the stores; we logged every request and routed it to the right level.
That paid off quickly. Early in the ASO work we saw isolated reports about document uploads. Over time it became a widespread issue: patients could not upload labs, extracts, and other medical documents. Thanks to clear communication we found it was local — only on devices of a specific brand. We identified the cause and shipped a fix fast
Reviews: from negativity to dialogue
Over time the inbox mixed technical and medical topics. Responses to negative feedback slowed down.
We consolidated every channel into a shared inbox with the client and set up filtering:
clinic operations and medical topics went to the client
app reviews, technical issues, and store friction stayed with IT CRON
Support from different sources moved into one channel with clear ownership. Response time improved, and the process became manageable
Flexible trigger system
At the start the usual problem showed up: positive reviews were rare. Google Play sat at 3.2 and the App Store at 2.9 — far below the real quality of clinic services.
We built a flexible trigger system that decides when and under which conditions to show a message, popup, or capture form. It is powered by the C++ Mathematical Expression Toolkit Library (ExprTk), wrapped for C#
How it works
The client sends an event variable to the server, for example an app open
The server runs an arithmetic check against the formula
Thanks to the C++ wrapper, calculations are instant
The server responds: if the trigger fires, it notifies the client
The mobile client shows the user a dialog with an action

Any logic you need
The formula checks every condition and shows a message only when the user crosses each threshold. For example: visited a section 5 times, booked an appointment, successfully added a document. The system approach lets us add new scenarios without rewriting code — just change server parameters.
Now prompts to rate the app, leave a review, or report a problem appear for a reason: at the right moment for the user
Result
Rating growth in 5 months
Google Play from 3.2 to 5.0, App Store from 2.9 to 4.0. Growth came from a mechanism that asked for a rating when the user had received the right level of service and was ready to leave a positive response


Higher-quality feedback
We started receiving not only technical bugs, but also positive reviews about doctors, service convenience, and the interface. A reliable portrait of the app and clinics took shape

Stronger customer focus
We found and fixed many incidents and built a direct dialogue with users. Patients saw that their opinion shapes the app. That raised loyalty to Poliklinika.ru 2.0

Разрабатываем цифровые решения, которые растут вместе с бизнесом
Mon–Fri, 9:00–18:00 (MSK)
