3. The compensation model is activated. Based on the data entered regarding the customer’s issue, the system automatically suggests a solution to the operator: whether compensation is needed, in what form (pizza, promo code, size, validity period), and what the associated costs will be for the partner.
For example: «the toppings ran», product — «medium carbonara», high average check, customer orders regularly → the system suggests issuing a 30 cm pizza with a specific validity period.
The operator does not come up with a solution on their own; the Dodo IS system makes an objective, rather than an emotional, decision on their behalf.
4. The operator resolves the issue right then and there. The main goal is to resolve the problem on the first line of support without passing the customer around: apologizes; explains exactly what will be done and by when; if necessary, contacts the pizzeria according to their algorithm — whether the order is still being prepared, in transit, and so on; records the outcome in the system.
5. The business aspect — the partner doesn’t lose money. All compensation is based on revenue, so support isn’t a cost center but a tool for retaining customers and growing revenue. Dodo IS tracks how much the partner spends on compensation and support, what margin customers generate within a month after a complaint, and whether the investment pays off. According to statistics, every ruble spent on compensation generates several rubles in revenue.
6. Customer inquiries turn into data. Every «my order is cold» or «dry pizza» complaint doesn’t go to waste, because the system collects statistics by issue type, automatically classifies them, and shows where problems occur most frequently — for example, cold orders account for 22% of all inquiries, and for a specific product, there are many reviews mentioning dryness or insufficient toppings.
7. The cycle closes, and the system improves. Based on accumulated inquiries and metrics:
- Bots and workflows are refined so they can resolve more common issues without human intervention.
- Interfaces and tools for support agents are simplified so they spend less time clicking buttons and more time focusing on the customer.
- Care standards and principles are reviewed.
- New features are tested, such as automatic compensation for a missing sauce without human intervention.
A simple customer story: there was a problem → I wrote in → I got a solution — is built on a vast layer of processes, algorithms, data, and economics that allow support to be a caring service, not just a phone for unanswered calls.
A video on how we’re developing customer support from customer support lead Sasha Sedlacek: