How to Explain What Happened Step by Step in Tech Support Reply English
When a customer writes to tech support saying something broke, your job is to explain what happened in a clear, logical order. The best way to do that is to describe the steps exactly as they occurred, using simple past tense and time markers. This article shows you how to structure that explanation so the customer understands the sequence of events without confusion.
Quick Answer: The Step-by-Step Formula
To explain what happened, follow this structure: Start with the normal state, then describe the first action, then the next action, and finally the result. Use words like first, then, after that, and finally. Keep sentences short. Use past tense for completed actions. For example: “First, I opened the software. Then I clicked the update button. After that, the screen went blank.”
Why Step-by-Step Explanations Matter in Tech Support
Customers often describe problems in a jumbled way. They might say, “It just stopped working,” without telling you what they did before. When you write a step-by-step explanation, you give the customer a clear timeline. This helps them confirm what happened and helps you diagnose the issue faster. It also reduces back-and-forth emails because the customer can see exactly what you understood.
Key Language Tools for Step-by-Step Explanations
Time Markers
Use these words to show the order of events:
- First / Initially – for the first action
- Then / Next – for the following action
- After that / Subsequently – for actions after the second one
- Finally / Eventually – for the last action or result
Verb Tenses
Use simple past tense for each step. For example: “I clicked the button. The screen froze.” If you need to describe something that was already true before the steps, use past perfect: “I had already installed the update.” But keep it simple most of the time.
Connecting Words
Use and then, so, because, and which caused to link steps. Example: “I clicked the link, and then the page loaded slowly. This caused the browser to crash.”
Comparison Table: Formal vs. Informal Step-by-Step Explanations
| Situation | Formal (Email) | Informal (Chat or Phone) |
|---|---|---|
| Starting the explanation | “I would like to explain the sequence of events that occurred.” | “Here’s what happened step by step.” |
| Describing the first step | “Initially, I accessed the settings menu.” | “First, I went to settings.” |
| Describing the next step | “Subsequently, I selected the update option.” | “Then I clicked update.” |
| Describing the result | “As a result, the system displayed an error message.” | “So then it showed an error.” |
| Ending the explanation | “I trust this clarifies the situation.” | “That’s basically what happened.” |
When to use it: Use formal language in written emails to customers or managers. Use informal language in live chat or phone conversations where speed matters.
Natural Examples
Example 1: Software Crash (Email – Formal)
“Dear Support Team,
I am writing to explain what happened with the software crash this morning. First, I opened the application at 9:00 AM. Then I clicked the ‘Sync’ button. After that, the application stopped responding. Finally, I closed it using Task Manager. I had not made any changes before this happened.”
Example 2: Login Issue (Chat – Informal)
“Hi, here’s what happened. First, I typed my username and password. Then I clicked ‘Login’. After that, the page just refreshed and didn’t log me in. I tried twice, same result.”
Example 3: Hardware Problem (Email – Semi-Formal)
“Hello, I wanted to explain the printer issue step by step. First, I turned on the printer. Then I loaded paper into the tray. Next, I sent a print command from my computer. The printer made a noise but did not print. Finally, the error light started flashing.”
Common Mistakes
Mistake 1: Skipping Steps
Wrong: “I clicked update and it broke.”
Better: “First, I clicked the update button. Then a progress bar appeared. After it reached 100%, the screen went black.”
Why: Skipping steps makes it hard for the support agent to know exactly where the problem started.
Mistake 2: Using Present Tense for Past Events
Wrong: “I open the file, then it crashes.”
Better: “I opened the file, and then it crashed.”
Why: Present tense sounds like it is happening right now, which confuses the timeline.
Mistake 3: Mixing Up Order
Wrong: “The error appeared after I clicked save, but before that I had opened the document.”
Better: “First, I opened the document. Then I clicked save. After that, the error appeared.”
Why: Putting the result first makes the explanation harder to follow.
Better Alternatives for Common Phrases
| Weak Phrase | Better Alternative |
|---|---|
| “It just happened.” | “Here is the sequence of events.” |
| “Then it did something.” | “Then the system displayed an error.” |
| “After that it stopped.” | “After that, the application stopped responding.” |
| “I don’t know what happened.” | “I can describe the steps I took.” |
Mini Practice Section
Read each situation and write a step-by-step explanation. Then check the suggested answer.
Question 1
Situation: You opened a website, clicked a link, and the page showed a 404 error. Write a step-by-step explanation for a support email.
Suggested Answer: “First, I opened the website homepage. Then I clicked the ‘Downloads’ link. After that, the page showed a 404 error message.”
Question 2
Situation: You installed a new app, restarted your phone, and the app disappeared. Write a step-by-step explanation for a chat conversation.
Suggested Answer: “First, I installed the app from the store. Then I restarted my phone. After that, the app icon was gone from the home screen.”
Question 3
Situation: You connected a USB drive, copied a file, and the drive stopped being recognized. Write a step-by-step explanation for a support ticket.
Suggested Answer: “First, I plugged the USB drive into the port. Then I copied a 2GB file to it. Next, I safely ejected the drive. When I plugged it in again, the computer did not recognize it.”
Question 4
Situation: You changed a password, logged out, and could not log back in. Write a step-by-step explanation for a phone call.
Suggested Answer: “First, I changed my password in settings. Then I logged out. After that, I tried to log in with the new password, but it said ‘invalid credentials’.”
FAQ: Step-by-Step Explanations in Tech Support
Q1: Should I always use past tense?
Yes, for actions that are finished. Use simple past for each step. Only use present tense if you are describing something that is still happening, like “The error is still showing.”
Q2: How many steps should I include?
Include every step that is relevant. If a step did not affect the problem, you can leave it out. But if you are unsure, include it. It is better to have too many steps than too few.
Q3: Can I use bullet points in an email?
Yes, bullet points can make the steps very clear. For example:
– Opened the app
– Clicked ‘Sync’
– App froze
Just make sure each bullet is a complete thought.
Q4: What if I do not remember the exact order?
Be honest. Say something like: “I am not 100% sure of the order, but I believe the first step was…” Then describe what you remember. It is better than guessing wrong.
Final Tips for Writing Step-by-Step Explanations
Keep your language simple. Use short sentences. Read your explanation out loud to check if the order makes sense. If you can follow it easily, the customer will too. Practice writing explanations for common problems like login failures, software crashes, and connection errors. The more you practice, the more natural it becomes.
For more help with the first part of a support reply, visit our Tech Support Reply Starters section. If you need to make polite requests during the conversation, check out Tech Support Reply Polite Requests. You can also practice writing full replies in our Tech Support Reply Practice Replies category. For any questions about this guide, see our FAQ page or contact us.
