Nonprofit service operations guide
Guide 2: Design humane support intake and triage
Give staff one understandable path from a software problem to the right response.
Make the front door easy
Choose one visible support path and tell people what information is safe and useful to provide. Avoid making staff diagnose the technical cause or select an obscure queue before they can ask for help.
Use structured choices for affected service, impact, urgency, request type, contact, and safe evidence. Do not invite passwords, protected records, or unnecessary personal information into a general ticket.
Triage by impact and urgency
Distinguish incidents, access requests, data questions, defects, how-to help, and improvement ideas. Set severity around disrupted mission work, affected people, time sensitivity, recovery options, and safety or compliance exposure.
Name the first responder, resolver, escalation owner, update interval, and closure evidence for each class. Seniority should not silently become the priority rule.
Learn from repeat demand
Review recurring requests for missing documentation, poor onboarding, confusing configuration, access design, capacity constraints, data quality, or vendor defects. Support volume is operating evidence.
Close the loop with the requester and publish reusable guidance when safe. Keep a separate improvement backlog so longer-term work does not disappear inside resolved tickets.