Helpdesk & Support

A ticket knows which department raised it and, to the minute, how long it waited. It holds no hours, no rate and no cost — and hours are costed a module away, against a task that carries no department.

Japan gives a mail-order buyer eight days from delivery to send the goods back — and takes the right away if you published your own terms in the advertisement. The window is a property of a document, and our return row records neither the route nor the postage.

In Victoria, whether a repair is urgent is a closed statutory list, and it decides more than a deadline: one route lets the renter spend your money, the other brings in a regulator. Our categories hold the clocks and not the consequence.

Canada gives you two days to report a product incident, counted from the day you became aware. That is a date about your organization rather than about a record — and it is the one date no operations system holds.

Singapore presumes that goods failing within six months of delivery were faulty when they were handed over, and the seller has to establish otherwise. That makes the delivery date and the individual unit the two records that matter.

Indian e-commerce rules give a grievance officer 48 hours to acknowledge a complaint and one month to redress it. Three settings in an ordinary help desk decide whether either period is measured — and the one that matters is not a clock.

Satisfaction ratings can only be submitted by a requester with an account, through the self-service path. Everybody who reached the desk without one is missing from the average, and the average does not say so.

The most common way a support team hits its first-response target without responding is to write a note to itself. One condition in this codebase makes that impossible, and it is worth knowing which one before somebody helpfully removes it.

Our data export and erasure tooling takes a user account. An external ticket requester does not have one — that is the entire reason they were sent a tracking link. So the people most likely to ask are the people the tool cannot be pointed at.

The business day here is two clock times and one application timezone — simple and predictable for a single-site team. For a desk in Bengaluru promising four hours to a customer in Lagos, we can add per-desk business hours so each SLA counts in its own clock.

The breach alarm notifies the agent, then their manager, then the department — the right ladder in an organisation that has one. For a six-person business we can configure a flatter path, so the alert reaches somebody positioned to act on it.

A support contract makes two promises — we will answer by then, we will fix it by then — and they need two alarms. Giving them one shared "already notified" flag would have meant the first breach permanently silenced the second.