NewAI Content Creation is now live in Early Access
Turning Point Training Instituteby Training Center
Skip to content
0%
Module 13 — Escalation, Communication and DocumentationLesson 3 of 4
Video lesson

Communicating with Users and Documenting Every Incident

BeginnerVideo lesson
9 min readBeginner

Where you are: Module 13 — Escalation, Communication and Documentation · Lesson 13.3 · Based on Chapter 13 (§13.4–13.5) and Appendix B of Dr. Tahseen Al Doori's Troubleshooting Essentials.

What you'll be able to do

  • Apply the five principles of communicating with users during a live incident.
  • Rewrite jargon-filled or blaming messages in plain, respectful language.
  • Record an incident using the fields of the book's problem log template.
  • Explain how consistent records grow into an organisational knowledge base.

Watch: Communicating with Users and Documenting Every Incident

The video follows one stressful call, from first contact to closure, and shows what the technician says at each point. It then shows how the record of that call becomes knowledge that helps the next person. As you watch, consider:

  • At which moments does the technician update the user, and why then?
  • Why is the ticket not closed when the technician believes the fix works?
  • How does a single ticket become something that prevents future tickets?

Communication is part of the fix

A technically perfect repair can still leave a user unhappy, anxious or unsure whether to trust the system again. Communication is not decoration around troubleshooting: it is how you gather good information in Step 1 and how you confirm success in Step 6. Chapter 13 gives five principles.

1

Listen fully, acknowledge impact

Let the user finish before you speak, and recognise what the problem is costing them: a deadline, a customer, a lost morning.

2

Plain language, no blame

Avoid jargon and never suggest the user is at fault. Blame makes people hide the details you need.

3

Realistic expectations

Say what happens next and roughly when. A promise you cannot keep is worse than an honest estimate.

4

Keep them informed

Update the user on progress, especially when the fix takes time. Silence feels like being forgotten.

5

Confirm before closing

The problem is not solved until the user agrees it is solved.

Notice how these principles support the rest of the method. Listening fully and avoiding blame make it far more likely that the user will mention the change they made ("Well, I did install something yesterday..."), and Chapter 2 taught you that what changed is the most powerful question. Confirming with the user is Step 6, verify full system functionality: you repeat the action that originally failed, check related functions, and ask the user to confirm that the system works for them.

Plain language in practice

Instead ofTry
"Your DHCP lease failed.""Your laptop didn't receive a network address, so it couldn't join the network. I'm fixing that now."
"You must have deleted it.""Let's find out what happened to the file and whether we can get it back."
"It'll be done soon.""I expect to have an update by 11:30. I'll call you then, even if it's not fixed yet."
"That's a server issue, not my problem.""This needs our server team. I've passed on everything you told me, so they won't need to ask again."

The last row joins this lesson to Lesson 13.2: telling the user that you have escalated, and that you passed on everything, reassures them that the problem has not disappeared into a queue.

Why the user confirms the fix

Chapter 3 says a problem is not closed until the user has confirmed the fix, and Chapter 13 repeats it. There are three good reasons. First, the technician's test may not match what the user actually does: the email may send from the technician's test account but not from the user's shared mailbox. Second, the fix may have broken something else that only the user will notice. Third, confirmation ends the incident on a shared understanding, which protects trust and avoids the same ticket being reopened tomorrow.

Documenting every incident

Chapter 13 asks that every significant problem be recorded in a ticketing system, a log or a shared spreadsheet, using a consistent template. The book's problem log template (Appendix B) has these fields:

FieldWhat to write
Reference number; date and time reportedSo the record can be found and the timeline rebuilt
Reported by / contactWho to ask for more detail or to confirm the fix
Device, system and locationWhere the problem lives
Problem statement; exact error messageThe Chapter 4 statement and the exact text or code
Recent changes; theories tested and resultsThe evidence trail, including rejected theories
Root cause; solution applied; verified by (user) and dateWhat was really wrong, what fixed it, and who confirmed it
Preventive measures; time spent / escalated toHow recurrence is prevented, the effort involved and any escalation

Why consistent? Because records only become useful when they can be compared. If one technician writes "Outlook won't send" and another writes "SMTP auth fail", nobody notices that it is the same problem happening every month.

From records to a knowledge base

Over time, consistent records become a knowledge base. The book names three benefits:

Log every incidentUse one templateRecords build upSpot recurring problemsReuse solutionsNew staff learn
  • Recurring problems are spotted. Ten tickets with the same cause point to a root cause worth fixing (Chapter 12).
  • Solutions are reused. The second technician to meet a fault finds the first technician's answer in minutes.
  • New staff learn from previous incidents. The records are a training resource built from real cases.

Remember Tier 0 in the support model: self-help through the knowledge base, FAQs and checklists. Every well-written record is a candidate for a Tier 0 article, which means some future users will solve the problem themselves without ever opening a ticket.

Communicate so the user stays informed and confident; document so the organisation learns. A fix that is not confirmed and recorded is only half finished.

Worked example

The book's own worked example in Chapter 3 shows documentation creating knowledge. A user's email client showed Sending failed from 9:00, the morning after they changed their password. The client still held the old password; updating it fixed the problem, and the user confirmed. The Document step did two things: the ticket recorded the cause and fix, and a note was added to the password-change guide reminding users to update their email clients.

That second action turned one fix into prevention. The next person who changes their password reads the guide and avoids the fault altogether: a Tier 0 solution created from a Tier 1 ticket.

Try it

(Fictional scenario, paper exercise.) A user calls at 08:50: their laptop shows a blue error screen and they present to a client at 14:00. You find that a graphics driver updated overnight; rolling back the driver fixes the problem by 10:20.

  1. Write the three sentences you would say at 08:52 (acknowledge, plain explanation of next steps, realistic expectation).
  2. Write the update you would give at 09:45 while the fix is still in progress.
  3. Fill in every field of the Appendix B problem log for this incident.
  4. Write one sentence for a Tier 0 knowledge base article that could help the next user.

Completion criteria: no jargon or blame in items 1 and 2; every log field completed, including verified by (user); item 4 is understandable by a non-technical reader.

Knowledge check

A repair is taking longer than expected. Which principle from Chapter 13 matters most at this moment?

Why does the book ask for a consistent template when recording incidents?

Your test message sends successfully after a fix. What should happen before the ticket is closed?

Which statement follows the book's guidance on communicating with users?

Answers explained

  1. b — The book stresses updates especially when a fix takes time; confirmation comes at the end, silence leaves users anxious, and failed attempts must always be recorded.
  2. a — Consistency makes records comparable, which is how recurring problems and reusable solutions are found; it is not about speed or length.
  3. c — Step 6 and Chapter 13 both require user confirmation; your own test may not match how the user works.
  4. d — It sets a realistic expectation in plain language; the others use jargon, assign blame or make a vague promise.

Key takeaways

  • Five principles: listen and acknowledge, plain language without blame, realistic expectations, regular updates, confirm before closing.
  • User confirmation is part of Step 6: a problem is not closed until the user agrees.
  • Record every significant incident with one consistent template, such as the Appendix B problem log.
  • Consistent records become a knowledge base: recurring problems spotted, solutions reused, new staff trained, and Tier 0 self-help improved.

Sources

  • Dr. Tahseen Al Doori — Troubleshooting Essentials, University Edition (2026), §2.3, §3.6–3.7 and the worked example Email Not Sending, §13.4–13.5, Figure 13.1, Appendix B