A service desk that is honest about time.
Most desks let a late ticket become an on-time ticket the moment somebody resolves it. This one writes the miss once, and the miss stays written.
What happens to a promise between made and kept.
Four moments where a desk usually loses the truth, and what this one does instead. With motion off, all four are laid out together.
Two clocks, and the priority picks the calendar.
First response and resolution run separately. The urgent ones count every hour; the rest count only the hours you are actually open, so a Friday evening does not quietly burn a commitment you never agreed to work through.
A stopped clock is never a silent one.
When a ticket is waiting on somebody else it can be parked. It leaves the queue and the resolution clock stops — and the panel says out loud that it stopped, rather than leaving somebody to work it out from a number that is not moving.
Written once, and never rewritten.
A missed commitment is marked once. Resolving the ticket afterwards does not go back and tidy it away — the record of the miss survives the fix, which is the only version of this anybody can actually rely on.
Check before sending.
A drafted reply is read back for the things only a person may promise — a price, a time, an escalation, “it is fixed” — with the exact words shown. It is a caution on the draft, not a block on the agent.
Example data, real behaviour. The screens show how the software behaves; no real person’s information appears in them.
Everything here exists because a desk usually gets it wrong.
None of it is exotic. It is the ordinary behaviour a service desk should have had all along.
Ordered by what is closest to late, not by what arrived.
A queue sorted by arrival is a queue that guarantees the wrong thing gets done first. This one continuously re-orders by which commitment is nearest to being missed, and warns before the miss rather than reporting it afterwards.
Progress, and nothing that invites them to police you.
They never see internal notes, the clock, or where they sit in the priority ladder. Those are the desk’s instruments, and a countdown shown to a customer only invites them to watch it.
A resolved ticket becomes an article, and later replies cite it.
Draft the article from the ticket that produced it, publish, and a reply built from that article carries the citation into what the customer actually receives. The answer someone was given can be traced back to the thing that produced it.
Analytics that refuse to name a person.
How long somebody waited before a human answered, and a place of their own for the tickets nobody answered at all. Durations per agent are withheld — and the screen says they are withheld, in words, rather than quietly leaving them out.
What Iatros does not do yet.
Including the awkward one about its own name.
- The desk console is real — nine live screens. The service behind it has never been deployed.
- Nothing is running in a customer’s production. A hosted demonstration runs in a US region.
- “Iatros” is the name we use here. Inside our own code the same thing is called support, and the document reconciling the two is still a draft. If that matters to your procurement, ask and we will show you exactly what maps to what.
- We publish no response-time attainment, no breach rate and no satisfaction score. There is no live desk to measure.
The same engine as the other two.
Forms, the workflow, who may act and the audit trail are the same source in all three, which is why a service desk and a change-control system can share a clock and a history.
Tell us what you promised, and to whom.
If the answer is complicated, that is exactly the conversation worth having.