Can this follow a known pattern?
Password resets, access requests, known-error fixes, and status questions that a documented process already answers.
Field note / support tiers
Not every ticket belongs at the same level - or with the same team.
"Help desk" is not one job. Splitting it into tiers is what makes it possible to decide, deliberately, which part stays close to your own staff and which part can move into a qualified fulfilment lane.
Three tiers, three different questions
Name the tier before naming the owner.
Does this need investigation?
Troubleshooting that requires diagnosing an unfamiliar cause, coordinating across a few systems, or applying judgment inside a defined technical boundary.
Does this need deep or vendor-level expertise?
Architecture-level problems, vendor case ownership, and anything that would consume a specialist's time even inside a fully staffed internal team.
Where firms usually draw the first line
Match each tier to a plausible owner.
| Tier | Common in-house pattern | Common fulfilment-lane pattern |
|---|---|---|
| Tier 1 | Whoever answers the phone first, informally. | The most repeatable candidate for a qualified lane. |
| Tier 2 | The person who "actually knows the systems." | Movable once tools, access, and documentation are qualified. |
| Tier 3 | Rare, and often already outsourced to a vendor or specialist. | Usually stays a named escalation path, not a recurring lane. |
What moves with the tier
A tier boundary is not just a difficulty level.
- The identity and intake channel must move with it - a client should not learn a new tier exists by being handed off awkwardly.
- Entitlement and context must travel with the ticket, not be rebuilt at each level.
- The return path for anything above the agreed tier needs a named owner before day one.
- A tier that "sometimes" gets handled by whoever is free is not a tier - it is unmanaged risk.
Getting the tiers right is a prerequisite for the rest of the handoff design, not a detail to settle after launch.
Related decision
The tier definition feeds a specific operating lane.
Naming the tiers is the easy part. The request path they feed into is where the boundary is actually tested day to day.
Bring your current tier split - even an informal one.
A rough sense of what Tier 1, 2, and 3 look like today is enough to test where a qualified lane could fit.