The proposed feature introduces Inbox-owned automatic ticket closure, where Thread manages the full lifecycle of a ticket using a deterministic, timer-based system rather than relying on PSA automation. Administrators would define clear closure timing rules—such as closing a ticket after a set number of hours in a “waiting on customer” state—ensuring predictable, explainable behavior. This eliminates split ownership between Inbox and the PSA, creating a single system of truth where conversation state and ticket status remain fully aligned. To balance intelligence with safety, the system would allow limited AI-assisted timing adjustments within strict guardrails. For example, Inbox could delay a closure timer once if a user partially responds or skip delays if resolution is clearly confirmed, but it would never independently decide to close a ticket. All behavior remains bounded by predefined limits, ensuring consistency and preventing unpredictable outcomes while still improving timing sensitivity compared to rigid PSA rules. The experience would be fully orchestrated within Inbox, with visible countdown-based reminders, escalation of tone, and a clear final closure action, all tied to the configured timer. Built-in safeguards—such as minimum and maximum time limits, audit logs explaining why a ticket was closed, and manual override options—ensure the system remains transparent and controllable. This approach delivers the benefits of centralized lifecycle management and reduced PSA dependency, while maintaining the determinism and trust required for a safe, adoptable first version.
