Escalation email templates with the contact tree they use
Escalation email templates built on one escalation contact tree: issue category, primary and backup owner, hours, response deadline and fallback. Emails to the owner, your manager, a vendor and the customer, a no-response follow-up, an urgent version and the closing email, plus a filled example, Word and Excel.
Made by Anatolii Ulitovskyi 
Fact-checked by RH Fardin Updated 1. The escalation contact tree: who owns what, by when
Fill firstEvery escalation email template on this page takes its facts from one table: the escalation contact tree, also called an escalation matrix. One row per issue category, five fields per row. Fill it once and share it with the team.
Tree row (one per issue category)Issue category: category
Primary owner: name, role, phone
Backup owner: name, role, phone
Hours: when they can be reached, for example Mon-Fri 9:00-17:00
Response deadline: Critical 30 minutes / High 2 hours / Normal 24 hours
Fallback: what happens if nobody answers by the deadline
Severity and response deadline
| Severity | When | Respond within |
|---|---|---|
| Critical | Safety risk, data exposure, or many customers affected | 30 minutes, any time, by phone |
| High | One customer cannot use the service, or money or a dated commitment is at risk | 2 hours, in the owner's hours |
| Normal | A workaround exists, or a decision is above your role | 24 hours |
How to fill it
- 5 to 8 categoriesFaults, delivery, billing, complaints, outages, data: the reasons customers really escalate.
- One owner, one backupPeople, not shared inboxes. The backup can make the same decision.
- Hours and phoneWhen each owner can be reached; a phone for Critical.
- Deadline by severityResponse means 'I have it' with the next step and a time, not the fix.
- FallbackWhat happens at the deadline. Review the tree after every miss.
Example: the tree of Kettlebrook Coffee Service, a fictional company that leases and services office coffee machines. Deadlines follow the severity table.
1.1Machine fault or repair
OwnerMarco Bianchi, service manager
BackupRuth Okoye, operations director
HoursMon-Fri 7:00-17:00; Critical any time
FallbackRuth sends a loan machine the same day. Critical: phone Ruth, then Hannah.
1.2Delivery or supplies
OwnerRuth Okoye, operations director
BackupNadia Flores, warehouse lead
HoursMon-Fri 6:30-16:00
FallbackNadia sends a same-day courier.
1.3Billing or contract
OwnerLeo Park, accounts
BackupHannah Price, founder
HoursMon-Fri 9:00-17:00
FallbackHannah takes it. Refunds over $500 always need Hannah.
1.4Complaint or legal threat
OwnerHannah Price, founder
BackupRuth Okoye, operations director
HoursMon-Fri 8:00-18:00
FallbackRuth calls the customer the same day.
1.5Outage or many customers
OwnerRuth Okoye, operations director
BackupHannah Price, founder
HoursAny time, by phone
FallbackPhone Hannah. Email affected customers every hour until it is fixed.
1.6Data or security
OwnerHannah Price, founder
BackupLeo Park, accounts
HoursAny time, by phone
FallbackPhone Leo. Lock the affected account first.
Never promiseA fix time in the tree. It promises a response by the deadline, not a solution.
2. Internal escalation email to the issue owner
Send this when the standard fix failed and the issue belongs to someone else in the tree. Send it to the primary owner only; copy the backup for Critical issues or at the deadline (tab 6).
SubjectEscalation, High: issue in 5 words, customer, respond by time
EmailHi owner first name,
I am escalating this to you as the owner for issue category. Severity: High. Please respond by deadline time with the next step and a time.
Customer: name, company, contact
Issue: what is wrong, in one or two sentences
Impact: who is affected, what they cannot do, what is at risk by when
What I tried: step, time, step, time. Result: result
The ask: one clear ask, for example a technician visit before Thursday
The customer will hear from us by customer update time. If I do not hear from you by deadline time, I will pass this to backup owner, as the tree says. The chat history is on the contact in where the record is.
Your name, role
Cross-team handoff (the next step is theirs)Hi name, I am handing issue for customer to your team, because the next step, next step, sits with you. Severity: Normal. Respond by deadline. Confirmed so far: facts. The customer was told: update and time. If nobody has it by deadline, it goes to backup owner. Your name
Fill in before sending
- Category, severity, owner and backup from the tree row.
- Deadline: the time you send plus the tree deadline.
- Impact in facts, and what you tried, with times.
- One ask that takes a yes, a no or a time.
Never promiseAn outcome to the customer on the owner's behalf. Promise only the next update time.
3. Escalation email to manager: sample for a decision
Use this when the next step is a decision above your role: a policy exception, money above your limit, a customer you may lose.
SubjectDecision needed by time: issue for customer
EmailHi manager first name,
I need your decision on issue for customer by deadline time. It is above my role because reason, for example the refund is over my $100 limit.
Impact: who is affected, what is at risk, by when
What I tried: steps, with dates
Option 1: option, cost amount, outcome result
Option 2: option, cost amount, outcome result
I recommend option number, because one reason.
If I do not hear from you by deadline time, I will default action within my authority. A 5-minute call works too: phone.
Your name, role
Short version for team chatManager first name, decision needed by time: issue for customer. Option 1: option. Option 2: option. I recommend number because reason. Details in my email. If there is no answer by time, I go with default action.
Fill in before sending
- The decision, in the subject and the first sentence.
- Why it is above your role.
- Two options with cost and outcome, and your pick.
- The deadline, and your default action within your authority.
Never promiseThe exception to the customer before the manager agrees. Say you asked for a decision and when you will update them.
4. Escalation email to a vendor or supplier, with evidence
Use this when a vendor's normal support has stalled: no owner on the ticket, a part that does not arrive, a date that passed. Write to the account manager, not only the ticket queue, and let dates and costs carry the urgency.
SubjectEscalation: ticket ticket number, open since date, named owner needed by date
EmailHi name,
I am escalating ticket ticket number, opened on date, because normal support has not resolved it and it now affects our customers.
Issue: what is wrong, in one sentence
Impact on us: customers affected, hours or orders lost, money at risk
History:
- date: reported by channel, reference reference
- date: followed up, answer: what they said
- date: followed up, no answer
Evidence attached: photos, screenshots, order confirmations, logs
Our agreement: contract reference and the response time it sets, if any
The ask: a named owner and a resolution date by date and time. If I do not have both by then, I will next step, for example ask your manager to assign an owner.
Your name, role, company, phone
Second follow-up if the vendor does not answerHi name, following up on my escalation of date about ticket ticket number. I asked for a named owner and a resolution date by deadline and have neither. The impact is now updated impact, so I am now next step taken. If you can name an owner today, I will gladly keep working with you. Your name
Evidence to attach
- The ticket or order number and the date you first reported it.
- Each follow-up with its date and the answer.
- Photos, screenshots or logs, with dates, and the terms that set a response time.
Never promiseYour customer a date the vendor has not confirmed in writing. Say what you asked for and when you will update them.
5. Customer escalation email: who has it, next update
Send this within 15 minutes of the internal escalation, in the customer's channel: who has the issue, when they hear from you next, and what they need to do.
SubjectYour issue is escalated to owner name, update by time
EmailHi first name,
Thank you for your patience while we tried what you tried. It did not fix issue, so I have escalated it.
Who has it: owner name, our owner role, who handles issue category.
Your reference: reference
Next update: by update time and day, even if the fix is not finished.
What you need to do: nothing for now / one thing
You do not need to explain anything again: owner first name has the full history. If anything changes on your side, reply to this email and it reaches me directly.
Your name, role, company
Chat versionI have escalated this to owner name, our owner role. Your reference is reference. You will hear from us by update time today, even if the fix is not finished. You do not need to repeat anything; owner first name has this chat.
When the customer escalated firstHi first name, I am sorry it reached the point where you had to escalate. I have passed issue to owner name, our owner role, with the full history. Your reference is reference, and you will get a real update, not a holding message, by update time. Your name
Fill in before sending
- Owner name and role from the tree row.
- Update time: the owner's deadline plus about 20 minutes.
- One action for the customer, or 'nothing for now'.
Never promiseA fix time, a refund or compensation before the owner confirms it. Keep the update time, even with no news.
6. No response: follow-up email and the fallback step
At the deadlineSend this at the deadline, not a day later. The escalation passes to the backup, and one email tells both people. The customer's update time does not move.
SubjectNo response by deadline time: issue for customer passes to backup first name
EmailHi owner first name, hi backup first name,
Owner first name, my escalation of time about issue for customer got no response by the deadline time deadline. Backup first name, you are the backup for issue category in our contact tree, so it passes to you now.
Issue: issue, severity High
Impact: impact, updated if it changed
What I tried: steps
The ask: the same ask
The customer expects an update by customer update time.
Backup first name, please reply 'I have it' with the next step by backup deadline. If I do not hear from either of you by then, I will third level, for example phone the founder.
Your name, role
Third level, if the backup is silent tooName, issue for customer is unanswered: owner missed the time deadline and backup missed time. Impact: impact. The customer update is due at time. I need one person to say 'I have it' now, and I will call you at time.
Customer update when the owner changesHi first name, as promised, an update on issue: backup name, our backup role, now has your case. Next step and when. Your reference stays reference. Your name
Rules
- Follow up once, at the deadline, to the owner and the backup together.
- The backup gets half the original deadline: 1 hour for High.
- The customer update goes out on time, whoever owns the case.
Never promiseThat 'the owner is on it' when nobody has replied. Say who has it now.
7. Urgent or outage escalation: short, for chat or phone
CriticalCritical issues do not start with an email. Phone the owner and post the short message in team chat or by text at the same time. The email is the written record after the call.
Team chat or text messageURGENT, Critical: issue since time. Affects who and how many. Tried: one line. Owner name, please call me now on phone. No answer by time: I call backup name.
Phone scriptHi owner first name, it is your name with a Critical escalation. Issue since time, affecting who and how many. I have tried one line. I need you to ask. Can you take it now?
If yes: I will tell customers you have it and that the next update is at time.
If no: who should I call?
VoicemailOwner first name, it is your name, Critical escalation: issue in one sentence. Please call me back on phone within 15 minutes. After time, I am calling backup name.
Email after the callSubject: Critical: issue, owner name, next update time
Our call at time: issue since time, affecting who. Owner: name, who will next step. Customers told: what and when. Next customer update: time.
Your name
Never promiseA cause or a fix time during an outage. Promise the next update time, and send it even if nothing changed.
8. Closing the escalation: outcome, lesson and the log
Completion checkAn escalation is closed only when the owner confirmed the outcome in writing, the customer was told, and the log row has the closed date.
SubjectResolved: issue, ref. reference
Email to the customerHi first name,
A short summary for your records.
What happened: issue, in one sentence
What we did: outcome, with dates
Who handled it: owner name, owner role
What we changed: one sentence, or 'nothing needed'
If the problem comes back, reply with your reference reference and it comes straight to me.
Your name, role, company
Internal close noteClosed: reference, issue category, severity, customer
Outcome confirmed by: owner name, date
Responded in time: Yes or No. Backup used: Yes or No
Customer told: date and channel
Lesson: one sentence: what caused the escalation or the delay
Change to the tree: change, owner and date, or 'none'
Completion check
| Check | Done when | Filled example |
|---|---|---|
| Owner confirmed the outcome | In writing: email, task summary or note | Marco, 7 October, 10:05 |
| Customer told | Sent, not only drafted | Closing email, 7 October, 10:15 |
| Log row closed | Outcome and closed date filled | Closed 7 October 2026 |
Silence does not decide itA customer who does not reply does not keep it open. An owner who never confirms does.
For small sales and support teams
Hand chats over from the AI agent and track every escalation to closed.
In CRMsoftware.pro the AI agent hands a chat to your team in Live Support, and the escalation becomes a task with an Assignee, a Deadline and a Priority. History and notes stay on the contact. The app does not route escalations by itself.
- Human handover in Live Support: Awaiting agent, Claim, Resolve
- Tasks with assignee, deadline, priority and a required status summary
- Launch, $19 a month billed yearly for 8 users; basic tasks on Free
Free plan: 3 users, AI chat, leads inbox and basic tasks, no credit card.
Filled example
A machine-down escalation: owner silent, backup took over
An office coffee machine fails for the second time in three weeks, two days before a client breakfast. Jess, the support lead, escalates to the owner in the contact tree and tells the customer when she will hear back. The owner misses the 2-hour deadline, the backup takes it, and the customer gets her update on time.
Escalation email to the owner, 6 October, 09:41
| Issue category | Machine fault or repair |
| Severity | High: client breakfast on 8 October at risk |
| Owner and backup | Marco Bianchi, service manager; Ruth Okoye, operations director |
| Deadline | 2 hours: respond by 11:41 |
| Fallback | Ruth sends a loan machine the same day |
| Impact | 40 staff without coffee; second fault since 15 September |
| What was tried | Power off for 10 minutes, then a descale cycle: still E14 |
| Ask | A technician visit before Thursday, or a loan machine today |
What happened next
| Time | Event | Who |
|---|---|---|
| 09:45 | Customer told: owner, reference ESC-031, update by 12:00 | Jess |
| 11:41 | Deadline passed: Marco on an install, no signal | Marco |
| 11:43 | No-response email to Marco and Ruth | Jess |
| 11:52 | 'I have it': loan machine by 15:00, new machine Wednesday 08:00 | Ruth |
| 11:58 | Customer told: Ruth has the case, loan machine by 15:00 | Jess |
| 14:40 | Loan machine installed and working | Nadia |
| 7 Oct, 09:20 | New machine installed, old one collected | Marco |
Completion check and CRM record
| Item | Recorded | Status |
|---|---|---|
| Owner confirmed outcome | Marco, task status summary, 7 Oct 10:05 | Done |
| Customer told | Closing email 7 Oct 10:15 | Done |
| Log row | Closed 7 October 2026, backup used: Yes | Done |
| Task | ESC-031, Assignee changed from Marco to Ruth at 11:43 | Done |
| Lesson | Install days count as out of hours: Ruth covers High machine faults | Done |
Why it matters
Why an escalation email needs an owner, a deadline and a fallback
Most escalation emails fail the same way: they go to a group, ask for a reply 'as soon as possible' and end without a next step. Nobody owns them, and the customer waits.
Teams that run on-call for live systems have written the fix down. Google's site reliability engineering book gives typical response times of 5 minutes for user-facing or highly time-critical services and 30 minutes for less time-sensitive systems, and describes a secondary on-call who catches the pages the primary misses1. PagerDuty's incident response guide recommends a 5-minute escalation timeout, always a backup schedule, and the whole team as the third level after the backup2.
A small support team does not need a pager rota, but it needs the same three things: one owner per issue category, a response deadline by severity, and a backup who takes over at the deadline. Your deadlines can be longer, like 30 minutes for Critical and 2 hours for High here, as long as they are written down and kept.
5 minutes
typical on-call response time for user-facing systems at Google
30 minutes
for less time-sensitive systems in the same practice
3 levels
owner, backup, then the whole team, in PagerDuty's guide
Excel matrix and log
Escalation matrix template and log in Excel
Three sheets: Escalation matrix (the contact tree), Escalation log with the filled case and 7 more sample rows, and Summary. Shaded columns fill in by themselves. Opens in Excel, LibreOffice and Google Sheets.
| Column | What it does |
|---|---|
| Matrix: category, severity, owner, backup, hours, deadline, fallback | One row per category and severity, deadline in hours. The log reads from here. |
| Escalated at, customer, category, severity | When it went out and what it is about; category and severity from lists. |
| Owner, backup Auto | Looked up from the matrix, or 'Not in matrix'. |
| Deadline Auto | Escalated at plus the response deadline for that row. |
| Responded at | When the owner or the backup replied 'I have it'. |
| Responded in time Auto | Yes by the deadline; No if later or not at all. |
| Backup used, customer told, outcome, closed | Yes or No, the outcome confirmed by the owner, the closed date. |
| Status Auto | Overdue (no response, deadline passed), Open or Closed. Closed needs a closed date, an outcome and Customer told = Yes. |
The Summary sheet counts escalations by category and by severity, the share answered within the deadline, how often the backup was used, and how many are open or overdue. In the sample log, 6 of 8 were answered within the deadline, the backup was used 3 times, and 1 is overdue.
How to use
How to use the escalation email templates
- 1
Fill the contact tree
Owner, backup, hours, deadline and fallback per issue category, on the Escalation matrix sheet.
- 2
Escalate and log
Send tab 2, 3 or 4 with the fields filled, and log the row with its deadline.
- 3
Tell the customer
Send tab 5 within 15 minutes, with an update time after the owner's deadline.
- 4
Act at the deadline
No response: send tab 6 to the owner and the backup. Critical goes by phone first (tab 7).
- 5
Close and review
Close with tab 8. Once a month, review the misses and change the tree, not only the people.
Set it up in CRMsoftware.pro
- My Bots > choose the bot > Connect tab: Send email notifications sets the address that gets an email when a chat needs human support; Assigned users lists who can manage the bot. Live Support > Notification Settings adds Email Alerts, Browser Alerts and Mobile Alerts.
- A handed-over chat shows as Awaiting agent in Live Support. The support lead clicks Claim and tries the standard fix.
- Create the escalation: Tasks > New Task, Task title 'ESC-031 Machine fault, High', Assignee the owner, Deadline the response deadline, Priority High (Urgent for Critical), Linked deal if any. Turn on Status summary required on completion, so the owner writes the outcome before Mark done.
- At the deadline, check Overdue in Tasks: change the Assignee to the backup and send tab 6.
- Tag the chat (Settings > Conversation Tags > New tag 'Escalated') and write the timeline, outcome and lesson in Notes on the contact.
- On Growth, save the chat version of tab 5: Settings > Saved Replies > New reply, Shortcut (for example /escalated), Title, Reply body, Share with team.
There are no automatic escalation rules and no escalation matrix feature in CRMsoftware.pro: the tree is your document, and the task deadline is what you watch. Human handover: Launch, $19 a month billed yearly for 8 users. Saved replies: Growth, $49. Free: AI chat and basic tasks for 3 users.
Monthly escalation review, 20 minutes
- The share answered within the deadline meets your target, by category.
- A reason that repeats in Backup used rows changes the tree.
- Every closed row has an outcome, Customer told = Yes and a closed date.
FAQ
Questions about escalation emails
How do I write an escalation email?
Put the issue category and severity first, then the impact, what you tried and one clear ask. Name the response deadline and what happens if nobody answers by then. Send it to one person: the owner in your contact tree.
What should an escalation email template include?
The five contact tree fields: issue category, primary and backup owner, hours, the response deadline for the severity, and the fallback. Add the impact, what was tried and the ask. Without a deadline and a fallback, an escalation can sit unanswered with nobody responsible.
How do I write an escalation email to my manager?
Ask for one decision in the subject and the first sentence, say why it is above your role, give two options with cost and outcome, and recommend one. Set a deadline and say what you will do within your own authority if no answer comes.
How do I tell a customer their issue has been escalated?
Name the person who has it and their role, give a reference and the time of the next update, and say whether the customer needs to do anything. Keep the update time, and do not promise a fix time the owner has not given.
What is an escalation matrix or escalation contact tree?
A table of who handles which issue, in what order and by when: issue category, severity, primary owner, backup owner, hours, response deadline and fallback. The Excel file has one ready to edit, with a log that reads from it.
What do I do if nobody responds to my escalation?
At the deadline, email the owner and the backup together: the escalation passes to the backup now. Give the backup half the original deadline. If the backup is silent too, phone the third level, such as the founder. Keep the customer's update time either way.
How do I escalate an issue to a vendor?
Write to the account manager, not only the ticket queue. List the ticket number, every contact with its date and answer, and the impact on you, and attach the evidence. Ask for a named owner and a resolution date by a set time.
When is an escalation closed?
When the owner confirmed the outcome in writing, the customer was told, and the log row has the closed date. A customer who goes quiet does not close it, and neither does a fix nobody confirmed. The Excel log shows Closed only when all three are filled.
Can CRMsoftware.pro escalate a chat automatically?
No. There are no automatic escalation rules and no escalation matrix feature. The AI agent hands chats to your team in Live Support (status Awaiting agent), and you create the escalation as a task with an Assignee and a Deadline. Human handover comes with Launch, $19 a month billed yearly.
Related templates
Free tools
Sources
- On-call response times and secondary rotation, read 8 October 2026: Google SRE book, Chapter 11: Being On-Call
- Escalation timeout and backup levels, read 8 October 2026: PagerDuty Incident Response Documentation, Being On-Call
- Unclear severity rule, read 8 October 2026: PagerDuty Incident Response Documentation, Severity Levels
- Plans and prices: CRMsoftware.pro pricing
Give every escalation a name and a clock.
Start free with 3 users, AI chat and basic tasks. Launch, $19 a month billed yearly for 8 users, adds human handover and the unified inbox. Growth, $49, adds saved replies.