All features
31 · Support and service

Support reports

How long replies take, what breaks most and which queue is drowning.

The month, in four numbers
Cases Times Causes
Support reports · June
QueueFirst replyClosingStatus
Shop12 min4 hOn time
Bakery31 min9 hOn time
Delivery2 h 102 dDrowning

A good average can hide a drowning queue. That is why it is read per queue.

Reports are not another place: they are the summary of the same inbox. How long the first reply takes, how long closing takes and which queue arrives drowning.

And what breaks most, which is the question that ends up changing a supplier or a model of device.

What it does

First reply, measured
Not the monthly average: per queue, which is where the problem shows
What breaks most
By device and by model, with the asset register behind it
Breaches, in plain sight
How many cases went past their deadline and in which queue
Works well with
30

Case inbox

Cases from your customers, your colleagues and your partners, in a single inbox.

See the feature
32

Knowledge base

The answer is written once and the customer finds it without opening a case.

See the feature
33

Asset register

The customer's device, with its serial number, its warranty and its faults.

See the feature
Previous Case inbox Next Knowledge base

Which ones do you need?

You do not have to switch everything on. Tell us how you work and we will tell you where to start. ATAZEL is in testing: write to [email protected].

Write to us