Ticketing
Browse 10 articles tagged ticketing across approvals, auditability, plugins, and controlled AI operations.
Self-Hosted Ticketing Evaluation Checklist
Evaluate self-hosted ticketing across data flows, identity, customization, approvals, recovery and source rights. Use a practical evidence worksheet.
Read article →When Native Zendesk Approvals Are Enough
Zendesk supports waiting and sequential approvals. Evaluate native workflows against your deployment, action review, integration and evidence requirements.
Ticket Routing Rules vs AI Triage
Compare ticket routing rules with AI triage: where rules work, where model suggestions help, and why operator corrections remain the control.
What Is New in Latch: April and May 2026
A customer-facing product update on recent Latch improvements across ticket queues, SLA visibility, ticket filtering, governed API access, and operational ti...
Shared Inbox vs Unified Triage: When the Queue Needs Rules
Compare shared inboxes and unified triage across ownership, routing, SLA state, approvals, exception handling, and ticket evidence.
Why Ticket Status Workflows Need Hard Edges
Permissive status models produce unreliable reporting. Why ticket state transitions need hard edges, and how to constrain them safely.
Asset Context Is the Missing Layer in Field Service Tickets
Field service ticketing gets sharper when every ticket carries asset history: faster diagnosis, fewer repeat visits, cleaner handoffs.
How to Move from Mailbox Triage to Governed Case Handling
Moving from a shared inbox to a governed ticket queue: what changes in routing, ownership, approval steps, and the audit trail.
Duplicate, Rejected, and Cancelled Ticket States
Duplicate, rejected, and cancelled tickets are normal volume, not exceptions. How to model them so reporting and SLA figures stay honest.
Closed Does Not Mean Gone: Designing Safe Reopen Paths
Reopening a closed ticket should restore the work without erasing history. How to design reopen rules, ownership handoff and honest queue metrics.
Start with one workflow
Follow a request through triage, review, and a plugin action. See the record that each step leaves behind.