Docs → Guides & how-tos
How support escalation works
What happens to your ticket after you send it — and how to raise the temperature when something matters more than the queue knows.
Last updated: August 2026
At a glance
- Tickets land with a human who knows your setup
- Escalate on the ticket, or call if it cannot wait
- Say the business impact, not just the symptom
- Escalating never gets anyone in trouble
The flow
1
Normal flow
Your ticket lands with someone who knows your environment — not a call center reading a script. Most requests resolve right here.
2
You escalate
Reply on the ticket and say clearly you are escalating and why — or call (931) 355-7256 if it cannot wait. Reference the ticket so context travels with the urgency.
3
What changes
More senior eyes, more frequent updates, and honest answers about what we know and do not know yet.
When to escalate
Hidden stakes
A “minor” printer issue that is actually blocking payroll. You know the stakes; we know the systems. Escalation is how those meet.
A deadline moved up
What could wait last week cannot wait today — say so.
It feels stuck
No visible progress and the updates stopped making sense. That feeling is a valid reason.
True emergency
Skip the ticket entirely: call, say it is urgent. See incident response.
Pro tip: tell us the business impact, not just the symptom. “The file server is slow” and “the file server is slow and invoicing stops at 3pm” get different responses.
Common questions
Will escalating annoy anyone?+
No. Escalating never gets anyone in trouble — if something feels stuck, saying so is exactly what we want.
What if it is a true emergency?+
Skip the ticket, call, and say it is urgent. See Incident response: what to expect.
Who ends up handling an escalated ticket?+
Someone with more context or more authority — and the original person stays involved, so nothing gets lost in a handoff.
Related docs
Incident response →
When it is not a stuck ticket but a genuine incident.
Maintenance windows →
Why something might be slow on purpose tonight.
Hosting & DNS changes →
The request flow for infrastructure work.
Something stuck right now?
Reply on the ticket with the word “escalate” and the business impact — that is all it takes.