When you report a problem in an app, the most helpful thing you can do is explain exactly what happened, in the order it happened. This article shows you how to write a clear, step-by-step explanation in English so the support team can understand your issue quickly and fix it without asking you to repeat yourself. You will learn the right phrases, the best order to present your steps, and how to adjust your tone for different types of feedback.
Quick Answer: The Three-Step Formula
To explain what happened step by step, use this simple structure:
- Start with what you were doing. Example: “I was trying to upload a photo.”
- Describe the first thing that went wrong. Example: “The app froze for a few seconds.”
- Explain what happened next. Example: “Then a blank screen appeared, and I had to close the app.”
This formula works for both formal support emails and quick in-app messages. Keep your steps short and use time words like first, then, next, and finally to make the order clear.
Why Step-by-Step Explanations Matter
App support teams receive hundreds of messages every day. If your explanation jumps around or leaves out key details, they may need to write back and ask for more information. That slows down the fix. A step-by-step explanation helps them reproduce the problem on their end, which is the fastest way to get a solution.
This skill is especially useful for App Feedback Message Problem Explanations, where clarity and order are more important than fancy vocabulary.
Key Phrases for Each Step
Here are the most useful phrases to describe each part of your experience. Use them to build your explanation.
Starting the Explanation
- “I was in the middle of…”
- “I had just finished…”
- “While I was trying to…”
- “After I clicked on…”
Describing the First Problem
- “The first thing I noticed was…”
- “Suddenly, the app…”
- “It stopped responding when I…”
- “An error message appeared that said…”
Continuing the Sequence
- “Then, after a few seconds…”
- “Next, I tried to…”
- “After that, the screen changed to…”
- “When I tapped the button again…”
Ending the Explanation
- “Finally, I had to force close the app.”
- “In the end, nothing happened.”
- “That is when I decided to report the problem.”
- “I have not been able to use the feature since then.”
Formal vs. Informal Tone
Your choice of words depends on where you are writing. A quick in-app message can be more direct, while an email to support should be polite and complete.
| Situation | Tone | Example Phrase |
|---|---|---|
| In-app chat | Informal | “I tried to log in, but it just kept spinning.” |
| Support email | Formal | “I attempted to log in, but the loading indicator continued without success.” |
| Feedback form | Neutral | “I tried to log in, but the page did not load.” |
In formal writing, use full sentences and avoid slang. In informal messages, you can use contractions like didn’t or couldn’t and shorter sentences.
Natural Examples
Here are three complete examples that show how to explain a problem step by step. Each one follows the three-step formula.
Example 1: App Crashes During Payment
Informal (in-app message):
“I was trying to pay for my order. First, I entered my card details. Then I tapped the ‘Pay Now’ button. The app froze for about five seconds. Then it crashed and went back to my home screen. I tried twice, and the same thing happened.”
Formal (email):
“I am writing to report a recurring issue during the payment process. I entered my card information as usual. After I tapped the ‘Pay Now’ button, the application became unresponsive for approximately five seconds. It then closed unexpectedly and returned me to the home screen. I attempted the process two more times, and the same result occurred each time.”
Example 2: Search Function Not Working
Informal:
“I typed a keyword in the search bar. Nothing showed up. I waited a few seconds, but it was just blank. Then I tried a different word, and still nothing. The search bar seems broken.”
Formal:
“I entered a keyword into the search bar, but no results appeared. After waiting several seconds, the screen remained blank. I then tried a different search term, and the same issue occurred. It appears the search function is not responding.”
Example 3: Upload Failure
Informal:
“I picked a photo from my gallery. Then I hit upload. A progress bar showed up and got to 90%. Then it stopped. I waited a minute, but it didn’t finish. I had to cancel.”
Formal:
“I selected a photo from my gallery and initiated the upload. A progress bar appeared and reached approximately 90% completion. At that point, the upload stopped. I waited for one minute, but the process did not resume. I was forced to cancel the upload.”
Common Mistakes
Even when you know the right words, it is easy to make small errors that confuse the support team. Here are the most common mistakes and how to fix them.
Mistake 1: Skipping Steps
Wrong: “The app crashed.”
Why it is a problem: The support team does not know what you were doing when it crashed.
Better: “I was scrolling through my feed when the app suddenly crashed.”
Mistake 2: Using Vague Time Words
Wrong: “It happened a while ago.”
Why it is a problem: “A while” can mean anything from five minutes to five hours.
Better: “This happened about ten minutes ago, and I have not been able to use the app since.”
Mistake 3: Mixing Up the Order
Wrong: “The screen went blank, and then I tapped the button, and then it crashed.”
Why it is a problem: The order is confusing. Did you tap the button before or after the blank screen?
Better: “I tapped the button. The screen went blank. Then the app crashed.”
Mistake 4: Giving Too Much Information at Once
Wrong: “I was trying to update my profile, and the app was slow, and I think my internet was fine, and I restarted my phone, and then it worked once but not again.”
Why it is a problem: The support team has to pick out the important details.
Better: “I was trying to update my profile picture. The app was slow, and the image did not save. I restarted my phone, and it worked once. The next time I tried, the same problem returned.”
Better Alternatives for Common Phrases
Some phrases are overused or unclear. Here are stronger alternatives.
| Instead of… | Use… | When to use it |
|---|---|---|
| “It didn’t work.” | “The action did not complete.” | Formal emails or reports. |
| “It was slow.” | “The app was unresponsive for several seconds.” | When you need to be precise. |
| “Something went wrong.” | “An unexpected error occurred.” | When you do not know the exact cause. |
| “I clicked on it.” | “I tapped the button.” | Mobile app feedback specifically. |
| “It stopped.” | “The process halted at 90%.” | When you want to give a specific point. |
Mini Practice Section
Test your understanding with these four questions. Write your answers in your own words, then check the sample answers below.
Question 1
You are trying to send a message in a chat app. You type the message, tap send, but the message never goes through. Write a step-by-step explanation in an informal tone.
Sample answer: “I typed a message and tapped the send button. The message showed a small clock icon for a few seconds. Then it disappeared. I tried again, and the same thing happened. The message never actually sent.”
Question 2
You are using a fitness app to log a workout. You select the exercise, enter the duration, and tap save. The app shows an error that says “Save failed.” Write a formal explanation.
Sample answer: “I selected a running exercise from the list. I entered a duration of 30 minutes. When I tapped the save button, an error message appeared that read ‘Save failed.’ I attempted to save the entry two more times, and the same error appeared each time.”
Question 3
You are trying to change your password in a social media app. You go to settings, tap “Change Password,” enter your old password and a new one, then tap confirm. Nothing happens. Write a neutral explanation.
Sample answer: “I went to settings and tapped ‘Change Password.’ I entered my old password and a new password. Then I tapped the confirm button. Nothing happened. The screen did not change, and no error message appeared.”
Question 4
You are using a note-taking app. You open a note, add a few lines of text, and close the app. When you open it again, the new text is gone. Write a step-by-step explanation.
Sample answer: “I opened a note that already had some text. I added three new lines at the bottom. I closed the app by swiping it away. When I opened the app again, the new lines were missing. Only the original text was there.”
FAQ: Explaining Problems Step by Step
1. How many steps should I include?
Include only the steps that are directly related to the problem. Usually three to five steps are enough. If you include too many unrelated actions, the support team may get confused. Focus on what you were doing right before the problem started, what happened during the problem, and what happened after.
2. Should I mention what I did to fix it?
Yes, but only if you tried something specific. For example, if you restarted the app or your phone, mention that. It helps the support team know what you have already tried. If you did not try anything, it is better to say nothing than to guess.
3. What if I do not remember the exact order?
Do your best to reconstruct the order. If you are unsure about one step, say so. For example, you can write, “I think I tapped the button first, but it might have been the other way around.” Being honest about uncertainty is better than giving a wrong order.
4. Can I use screenshots instead of writing steps?
Screenshots are helpful, but they should not replace your written explanation. A screenshot shows what happened at one moment, but it does not show the sequence of actions. Write the steps first, then attach screenshots to support each step. This combination gives the support team the clearest picture.
Putting It All Together
Now you have a clear method for explaining what happened step by step. Start with what you were doing, describe the first problem, and continue in order until the end. Use time words to make the sequence obvious. Adjust your tone based on whether you are writing a quick in-app message or a formal email. Avoid skipping steps, using vague time words, or mixing up the order.
For more practice with different types of feedback, explore our guides on App Feedback Message Starters and App Feedback Message Polite Requests. If you have questions about this guide, visit our FAQ page or contact us for help.
Comments are closed.