When you write a tech support message, the most useful thing you can do is explain what happened in the order it happened. Support teams read dozens of messages every day, and a clear step-by-step explanation helps them understand your problem quickly. This guide shows you exactly how to structure your explanation, what words to use, and what to avoid, so your message gets the right response the first time.
Quick Answer: The Step-by-Step Formula
To explain what happened step by step, use this simple four-part structure:
- Start with what you were doing. (e.g., “I was trying to log in.”)
- Say what happened first. (e.g., “I entered my username and password.”)
- Say what happened next. (e.g., “Then the page showed an error.”)
- Say what happened after that. (e.g., “I tried again, but the same error appeared.”)
Use time words like first, then, next, after that, and finally to make the order clear. Keep each step short and factual.
Why Step-by-Step Explanations Matter in Tech Support
Tech support agents cannot see what you saw on your screen. They rely entirely on your words to picture the problem. When you list events in the order they happened, you give them a timeline they can follow. This reduces back-and-forth questions like “What did you do before the error?” or “Did you try anything else?”
A step-by-step explanation also shows that you are organized and careful. Support teams often prioritize clear messages because they are easier to solve. If your message is confusing or missing steps, it may take longer to get help.
Key Time Words and Phrases to Use
These words help you connect your steps smoothly. Use them at the beginning of each new action.
| Time Word / Phrase | When to Use It | Example |
|---|---|---|
| First | For the very first action | First, I opened the app. |
| Then | For the next action | Then I clicked “Submit.” |
| Next | For the action after that | Next, the screen went blank. |
| After that | For a later step | After that, I restarted my computer. |
| Finally | For the last step | Finally, the error appeared again. |
Formal vs. Informal Tone
In a formal email, you might write: “First, I attempted to log in. Then, I received an error message.” In a chat message, you can write: “First I tried to log in. Then I got an error.” Both are correct, but the formal version uses complete sentences and words like attempted and received. The informal version uses shorter sentences and simpler words like tried and got.
Choose the tone that matches your situation. For a support ticket or email, formal is safer. For a live chat, informal is fine.
Natural Examples
Here are three realistic examples that show step-by-step explanations in different contexts.
Example 1: Email to Software Support (Formal)
“I am writing to report a problem with the invoice generator. First, I opened the program and selected ‘New Invoice.’ Then, I entered the client details and clicked ‘Preview.’ Next, the program froze for about 10 seconds. After that, it closed completely without saving. Finally, I reopened the program, but the invoice was not there.”
Example 2: Live Chat with Internet Provider (Informal)
“Hi, my internet stopped working. First, I noticed the Wi-Fi symbol had a yellow triangle. Then I tried to open a website, but it said ‘No Internet.’ Next, I restarted the router. After that, the Wi-Fi came back for about two minutes. Finally, it disconnected again.”
Example 3: Bug Report for a Mobile App (Semi-Formal)
“I found a bug in the photo editor. First, I opened the app and selected a photo. Then I tapped the ‘Crop’ tool. Next, I tried to drag the corner handle, but it did not move. After that, I closed the tool and opened it again. Finally, the app crashed.”
Common Mistakes
Even when learners try to explain step by step, they often make these mistakes. Avoid them to keep your message clear.
Mistake 1: Skipping Steps
Wrong: “I tried to log in and got an error.”
Why it is a problem: The support agent does not know what you did before the error. Did you enter your password? Did you click a button?
Better: “First, I entered my email and password. Then I clicked ‘Log In.’ After that, the page showed an error.”
Mistake 2: Using Vague Time Words
Wrong: “I did something, and then something else happened.”
Why it is a problem: Words like something and stuff do not give useful information.
Better: “First, I clicked the ‘Save’ button. Then the screen turned white.”
Mistake 3: Mixing Up the Order
Wrong: “The error appeared after I restarted. I had opened the file first.”
Why it is a problem: The order is confusing. The agent has to guess what happened first.
Better: “First, I opened the file. Then I edited the text. After that, I restarted the program. Finally, the error appeared.”
Mistake 4: Adding Unnecessary Details
Wrong: “I was sitting at my desk, and I had a cup of coffee, and then I opened the app.”
Why it is a problem: Extra details distract from the problem.
Better: “First, I opened the app.”
Better Alternatives for Common Phrases
Some phrases are overused or unclear. Here are better alternatives.
| Avoid This | Use This Instead | Why |
|---|---|---|
| “It didn’t work.” | “The button did not respond when I clicked it.” | Shows exactly what did not work. |
| “Something went wrong.” | “An error message appeared that said ‘Connection failed.'” | Gives the exact error. |
| “I tried everything.” | “I restarted the computer, cleared the cache, and tried a different browser.” | Lists the actual steps you took. |
| “It stopped working.” | “The program closed by itself after I clicked ‘Export.'” | Tells when and how it stopped. |
When to Use a Step-by-Step Explanation
Use this structure whenever you describe a problem that happened in a sequence. This includes:
- Reporting a software bug
- Describing a login issue
- Explaining a payment failure
- Telling a support agent about a crash
- Describing a setup or installation problem
Do not use this structure for simple problems that have only one step, such as “I forgot my password.” In that case, a short message is better.
Comparison Table: Good vs. Weak Explanation
| Weak Explanation | Good Explanation |
|---|---|
| “My email is broken.” | “First, I opened my email app. Then I clicked ‘Compose.’ Next, the app froze. After that, I closed it and reopened it. Finally, it crashed.” |
| “The website is not loading.” | “First, I typed the URL. Then I pressed Enter. Next, the page started loading but stopped at 50%. After that, I refreshed the page. Finally, it showed a blank screen.” |
| “I can’t print.” | “First, I opened the document. Then I clicked ‘Print.’ Next, the printer made a noise but did not print. After that, I checked the paper tray. Finally, I restarted the printer, but the same thing happened.” |
Mini Practice Section
Test your understanding with these four questions. Write your answers in a notebook or say them out loud.
Question 1: You tried to update an app. First, you opened the app store. Then you clicked “Update.” Next, the download started but stopped at 90%. After that, you tried again. Finally, you got an error. Write this as a step-by-step explanation.
Answer 1: “First, I opened the app store. Then I clicked ‘Update’ on the app. Next, the download started but stopped at 90%. After that, I tried to update again. Finally, an error message appeared.”
Question 2: You tried to send a file by email. First, you opened your email. Then you clicked “Attach.” Next, you selected the file. After that, you clicked “Send.” Finally, you got a message that said “File too large.” Write the explanation.
Answer 2: “First, I opened my email. Then I clicked ‘Attach.’ Next, I selected the file. After that, I clicked ‘Send.’ Finally, I got a message that said ‘File too large.'”
Question 3: Which time word should you use for the very first action?
Answer 3: “First.”
Question 4: Why is “It didn’t work” a weak explanation?
Answer 4: Because it does not tell the support agent what you did or what exactly did not work. A better explanation lists the steps and the specific result.
FAQ: Step-by-Step Explanations in Tech Support
1. How many steps should I include?
Include every step that is directly related to the problem. Usually three to five steps are enough. If you did many things, focus on the steps that led to the error or issue.
2. Should I include steps that did not cause the problem?
Only include steps that are part of the sequence that led to the problem. For example, if you opened a program, then opened a file, then the error appeared, include all three. If you checked your email before that, do not include it.
3. What if I do not remember the exact order?
Write the steps in the order you think they happened. Use words like I believe or I think to show uncertainty. For example: “First, I think I opened the file. Then I clicked ‘Edit.’ After that, the program froze.”
4. Can I use bullet points instead of full sentences?
Yes, bullet points are acceptable in chat messages and some support tickets. For example:
- Opened the app
- Clicked “Settings”
- Selected “Account”
- Error appeared
For formal emails, use full sentences.
Final Tips for Writing Step-by-Step Explanations
Keep your language simple. Do not try to sound technical if you are not sure of the terms. Use the words you know. Support agents can ask for clarification if needed.
Read your message before sending it. Check that each step is in the correct order and that you used time words to connect them. If a step is missing, add it.
For more help with the first part of your message, visit our Tech Support Message Starters section. To learn how to ask for help politely, see Tech Support Message Polite Requests. For more examples of explaining problems, explore Tech Support Message Problem Explanations. You can also practice your replies in Tech Support Message Practice Replies.
If you have questions about this guide, please contact us. For more information about how we create our content, read our Editorial Policy.
Comments are closed.