Outcome. A ticket that has been waiting on the customer with no reply for N days after a warning closes automatically, keeping open-ticket counts honest instead of drifting upward forever.
flowchart TD
A[Warning sent = true, status still Waiting on contact] --> B[Wait 5 more days]
B --> C{Still waiting on contact?}
C -->|yes| D[Close ticket]
D --> E[Set close reason = customer-inactive]
E --> F[Notify ticket owner]
C -->|no, replied| G[Skip - conversation resumes]

When to use it, when not to
- UseUse it as the natural follow-on to the 48-hour wait-and-warn workflow (tickets-sla-006), once the warning has gone out and nothing came back.
- UseUse it to keep reporting accurate when customers simply stop replying instead of formally closing the loop.
- SkipDo not use it to auto-close tickets waiting on your team; only ones waiting on the contact qualify.
- SkipDo not set N so short that customers feel rushed; typical windows are 5 to 14 days after a warning, not after the first wait.
or the tickets and sla pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.





