Short, specific, and about the work.
Notes on the parts of running a desk that are genuinely hard: writing an SLA that can be evidenced, setting a discount band that survives quarter end, and holding personal data the way the DPDP Act expects.
Nothing published yet
Rather than pad this page, here is what is being written and roughly why. If one of them would be useful now, say so and we will send the draft — it is more useful to us in front of somebody who runs a desk than sitting in a folder.
There are no case studies here because Simcomm does not publish a customer's name, logo or numbers without written permission on file. When that permission exists, the case study appears; until then, words rather than borrowed credibility.
In the queue
What is being written
Writing an SLA you can actually evidence
What to put in a contract so that the target is measurable, which pause conditions cause arguments, and why a single clock hides two of your three promises.
Setting discount bands that hold at quarter end
Choosing bands by percentage or by absolute margin, who should sign each, and what happens to a policy the first time somebody senior wants to bypass it.
Migrating from a shared mailbox without losing history
What is worth bringing across, what is not, and how to run the old and new desks in parallel for a fortnight without answering everything twice.
DPDP for a servicing desk, in plain terms
Consent that is specific and unbundled, retention that is executed rather than stated, and what "evidence of consent" means when somebody asks for it two years later.
Meanwhile, the product itself
The most useful reading on AcuityQ™ is the platform pages, which describe behaviour rather than benefits — what pauses which clock, what stops a quote, what the audit trail records.
Want one of the drafts?
Tell us which and we will send it. No newsletter, no sequence — just the document.