cx-complaints-slalisted

# Complaint deadline clocks Regulated complaint handling runs on deadlines that are not negotiable and not business-as-usual SLAs: missing a final-response deadline is a reportable failure in several regimes, not a dashboard amber. The arithmetic looks trivial and is not. Almost every hand-rolled complaint clock is wrong in at least one of the ways below, and the errors are systematically in the optimistic direction — they make you look compliant when you are not. ## This skill does not know your deadlines **Deadline lengths and rules vary by jurisdiction, sector, product and complaint type, and they change.** This skill deliberately hard-codes none of them. It gives you the clock mechanics; the deadlines come from your compliance function or the applicable rules, as configuration. If you do not have an authoritative source for the deadlines, that is the finding — stop and get one. Computing precise breach counts against a half-remembered deadline is worse than not computing them, because it produces a number people act on. The same applies to interpretation: **whether a specific case breached, and whether a breach is reportable, is a determination for compliance and legal.** Produce the clock and the evidence; do not rule. ## The clock decisions that change the answer **1. When does the clock start?** Options that all exist somewhere in practice: when the complaint was received by anyone at the firm, when it was *identified* as a complaint, or when it reached the com