Operating practices¶

The playlist suggests several practices that make the product more valuable over time.

Protect the unassigned queue¶

Review it daily and correct routing rules after assigning immediate work.

Record what caused the issue and exactly how it was resolved; this improves weekly Knowledge Base suggestions.

Keep specialists informed without changing ownership or personal performance metrics.

Use Radar for future or ambiguous items, Signals for monitoring alerts, tickets for assigned work, and incidents for coordinated security response.

Add notes to Signal acknowledgements and dismissals so future reviewers understand the decision.

Review coverage, assignment, and Signal rules whenever an exception reveals a routing problem.

Use SharePoint or Google Workspace integration for internal Docs when that aligns with the district’s records strategy.

Review Lumen-generated ticket details, articles, privacy analysis, briefs, and plans before acting or publishing.

Reserve sensitive incident records for administrators and designated security technicians.