Omnichannel
A customer writes, then calls, then fills in a form. Without one queue that is three separate cases and three different answers.
Why connect them
Omnichannel is not about having many channels — most companies already do. It is about the same case keeping its identity when the customer switches between them.
E-mail, call, form, SMS, portal message and API event sit on the same timeline, so nobody asks the customer to repeat themselves.
Categories, priorities and deadlines work the same way regardless of where the request came from.
Volume and handling times are comparable across channels, which shows where work actually piles up.
How it works
Every channel lands in the same ticket structure — the difference is only how the message arrives.
Who it is for
Wherever customers move between channels and expect the company to keep up.
Roneberg cut e-mails needing manual handling by 78% and raised call answer rate by 38%.
Patients call, write and use forms — Stacja Zdrowie handles around 150 calls a day alongside written requests.
One operator collects phone, dozens of mailboxes and a returns form into a single system across Poland and 19 EU countries.
When deadlines are contractual, they have to hold across every channel, not just e-mail.
Software that collects requests from every channel into one queue and keeps a single history per customer, so a case does not restart when the channel changes.
E-mail, phone, web forms, SMS, the customer portal and API — in the plan appropriate to each.
Yes, through the customer portal, which is part of the Comprehensive plan.
Yes. Categories, deadlines and reporting are shared, so a phone case is measured like a written one.
Yes, through API — used for example to bring orders and shipment data into the conversation.
Plans are priced per agent: 119, 149 and 169 PLN net per user per month, with a 10% discount on annual billing.