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...
Read What Is New in Latch: April and May 2026 →← Back to blogTag Archive
Ticketing
Browse 7 articles tagged ticketing across approvals, auditability, plugins, and controlled AI operations.
Browse tags
Operations30Auditability23approvals11Case Management10ai-triage9finance-controls9Field Service8action-providers7ai-governance7ticketing7Reporting6SLA5Workflow5workflow-orchestration5evidence4Guides4maker-checker4plugins4Product Updates4risk-controls4security4triage4ai3audit-trail3compliance3kyc3queue-management3reconciliation3Access Control2architecture2Attachments2authentication2authorization2change-management2email2eu-ai-act2extensibility2governance2integrations2iso-420012nist-ai-rmf2platform-architecture2status-management2ai-assistance1api1api-design1assets1auth1brute-force-protection1customer-operations1customer-support1Dashboards1Data Management1decisioning1defense-in-depth1developers1engineering1exception-handling1exceptions1implementation1ingestion1integration1legal-discovery1logging1mcp1metrics1Mobile1mobile-operations1monitoring1multi-tenant1oidc1Operations Management1Performance1platform1Policy Management1product-update1Public Forms1refunds1Reliability1reopen1reprocessing1runtime-control1saas1Search1segregation-of-duties1service-history1Sites1support1support-operations1technical-communication1ticket-routing1tickets1tutorials1unified-triage1workflow-design1
Unified Triage Is Not Just a Shared Inbox
Unified triage is not a shared inbox with more people in it. What changes when intake, routing, and ownership are enforced by the system.
Read Unified Triage Is Not Just a Shared Inbox →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.
Read Why Ticket Status Workflows Need Hard Edges →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.
Read Asset Context Is the Missing Layer in Field Service Tickets →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.
Read How to Move from Mailbox Triage to Governed Case Handling →Duplicate, Rejected, and Cancelled Tickets Are Not Edge Cases
Duplicate, rejected, and cancelled tickets are normal volume, not exceptions. How to model them so reporting and SLA figures stay honest.
Read Duplicate, Rejected, and Cancelled Tickets Are Not Edge Cases →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.
Read Closed Does Not Mean Gone: Designing Safe Reopen Paths →