Complaints
LCCP 6.1 register · 24h ack / 14d first / 8w final · OP-GREENTUBE
Register (6)
| Ref | Received | Jurisdiction | Category | 24h ack | 14d first | 8w final | Status | Outcome |
|---|---|---|---|---|---|---|---|---|
| GT-2026-0145 | 2026-06-02 | ggl | Responsible Gambling | OVERDUE | OVERDUE | on track | Open | — |
| GT-2026-0142 | 2026-06-02 | mga | Deposit / withdrawal | OVERDUE | OVERDUE | on track | Open | — |
| GT-2026-0144 | 2026-06-01 | mga | Marketing | OVERDUE | OVERDUE | on track | Open | — |
| GT-2026-0138 | 2026-05-30 | ggl | Bonus terms | ✓ done | OVERDUE | on track | Acked | — |
| GT-2026-0128 | 2026-05-16 | ukgc | Responsible Gambling | ✓ done | OVERDUE | on track | Acked | — |
| GT-2026-0067 | 2026-03-31 | ukgc | KYC / AML | ✓ done | ✓ done | OVERDUE | Responded | — |
How this works
Every state-change anchors a player_complaint_attested claim in the evidence ledger — chain-hash linked to your tenant's posture root. The worker tick scans every 30 minutes and raises a Finding on COMPLAINTS.HANDLING when any of the three SLA clocks breach. Severity escalates: medium at 24h ack, high at 14d first response, critical at 8w final response. Findings auto-route via your org-units and never replace the MLRO's substantive decision — KURAL is the workflow rail, not the decision-maker.