Skills Compliance
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.
npx rulebase-skills install cx-complaints-slaWhen to use it
Reach for this when someone says any of these — they are the phrases the skill itself triggers on:
- “are we meeting our complaint deadlines”
- “complaint SLA breaches”
- “final response deadline”
- “which complaints are about to breach”
How it works
The method, in the order the skill runs it. The full procedure — tables, worked examples and the edge cases — is in the skill itself.
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.
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 complaints team. These can differ by days.
Compute it
The config carries your working week, holidays per market, and one entry per deadline — its length, unit, what it runs from, and what satisfies it. See references/clock-config.md for the shape and the conventions each option implies.
Monitoring, not reporting
A monthly breach count is an autopsy. The useful artefact is a daily queue of cases approaching a deadline, ordered by time remaining.
Related skills
Free and open source, and vendor-neutral — it reads the conversations from whichever helpdesk you already run. Browse all 149 skills · connect your helpdesk over MCP · source on GitHub
