Operations
Browse 36 articles tagged Operations across approvals, auditability, plugins, and controlled AI operations.
Introducing nested choice fields for tickets
Create ticket-type choices with sub-options, save one final answer, and clear stale selections when an operator changes branches.
Read article →
Introducing reporting workspaces and Service delivery
Use seven Latch report destinations to inspect the tickets, date basis, and denominator behind an operational signal.
Report on the Fields Your Team Actually Uses
Group reports by tag folders and Issue Data Fields, then show the ticket-log columns that explain each result.
Latch Approvals: Features, Review Screens, and Audit Reports
See Latch approval features with screenshots: two-person gates, saved request review, expiry, separate execution, and approval audit reports.
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.
Field Work Is Not Complete Until the Evidence Is Complete
How field service teams define required ticket evidence, enforce complete records at closure, review AI troubleshooting, and report on outcomes.
Build an Operations Dashboard Around the Work You Monitor
Choose the dashboard sections each operator needs, save the layout, and set reporting ranges for SLA and resolution views.
Find and Group Tickets by Issue Type, Tag, Asset, or Result
Filter by issue type, tag, asset, and matching rules, then group results into an operational queue that matches the question at hand.
Latch Product Update: Clearer Queues, Site Operations, and Better Intake
July adds ticket subcategories, stronger queue filters, site tagging and import, form attachments, and dashboards that remember each operator view.
Latch Release: SLA Policies That Follow the Work
Apply complete SLA policies by ticket tag, including objectives, priority targets, working hours, reporting, and policy history.
How to Build Repeatable Operational Reports in Latch
Use standard reports and the report builder to filter, group, save, and rerun operational analysis without starting from a spreadsheet.
From Field Repairs to Planned Maintenance: Operational Reporting in Latch
Track ATM, cash deposit machine, POS, and printer service work, then report on replenishment and preventive maintenance without rebuilding spreadsheets.
Governance, Rollback, and the Implementation Order That Works for KYC and Reconciliation
Governance, rollback, and the implementation order that works when adding AI to KYC and reconciliation case handling.
AI Case Management for KYC and Reconciliation Starts With the Case, Not the Model
AI case management for KYC and reconciliation starts with the workflow, not the model. What to fix before adding intelligence.
Audit Logging for Compliance Operations
What compliance operations teams should record in an audit log so a reviewer can reconstruct a decision without asking anyone.
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...
Authorization Logic Audit for Case Management
Audit authorization logic with a free role-action matrix tester. Check refund thresholds, independent review, missing rules, and export reusable test cases.
What Is a Plugin Action?
A plugin action runs on an external system from inside the ticket with role checks, governed approvals, and immutable audit logging.
The Runtime Control Layer: What This Category of Software Is and Why It Exists
Ticket workflows need a control layer between the suggestion and the action. What that layer does, and why existing tools leave it out.
AI Raises the Value of Control-First Software
AI increases the value of control-first case platforms that combine governed execution, immutable audit logs, and cross-system integration.
AI Triage Needs a Control Plane, Not Just Better Prompts
AI ticket triage is not a prompt problem. What a queue needs around it, ticket routing, approval gates, execution records, and a model you host yourself.
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.
System of Record vs System of Action for Case Management
Compare a case-management system of record with a system of action across handoffs, policy, downstream execution, and evidence capture.
When AI Triage Should Recommend the Next Step and When It Should Stay Silent
AI triage should recommend a next step only when it has enough signal. When silence is the safer and more useful output.
The First Three Workflows to Govern with Action Providers
Plugins should start with workflows that need governed approvals, immutable audit logs, and safe external execution in production.
Approval Design for High-Risk Operations Workflows
How to design approval gates for high-risk operations that shrink blast radius, enforce two-person review, and keep the evidence on the case.
Audit Trails That Answer the Real Questions
An immutable audit log is only useful if it answers real questions. What to record so reconstructing a decision does not depend on memory.
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.
Brute-Force Protection for Self-Hosted Help Desks
Lockouts, layered rate limits, and audit logs that stop password guessing without locking out the operators who run the help desk.
Confidence Scores Are Not Enough for AI Ticket Routing
Confidence thresholds alone will not make AI ticket routing safe. What to measure instead, and where a human decision still has to sit.
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.
Operations Dashboard Metrics That Matter Beyond First Response
Build an operations dashboard around queue ageing, handoffs, blocked work, outcomes, data quality, plugin health, and AI readiness.
Turn Reprocessing from Tribal Knowledge into a Governed Action
Make reprocessing explicit, permissioned, and auditable so teams can retry failed work without tribal knowledge or weak controls.
Plugin Action Audit Log: Required Fields and Event Sequence
What a plugin action audit log must record from request and authorization through downstream completion, failure, and evidence retention.
How to Roll Out AI-Assisted Issue Resolution Safely
A stage-gated rollout for AI-assisted ticket resolution, with exit evidence for shadow mode, operator review, bounded execution, and expansion.
Start with one workflow
Follow a request through triage, review, and a plugin action. See the record that each step leaves behind.