When someone asks you "what additional information can you provide about the issue," they are not being difficult. They are trying to help you. But they cannot help you unless you give them the right pieces of the puzzle.
Most people stop too early. They say "it does not work" or "there is an error." That is not enough. That kind of answer forces the other person to ask more questions. Each question takes time. Each delay makes the problem worse.
If you want to solve an issue fast, you must learn what to share. You must give the other person exactly what they need the first time. This article walks you through every piece of information you should provide. No shortcuts. No fluff.
Why People Ask For More Information?
The person asking this question does not see what you see. They were not there when the issue happened. They do not know your screen, your device, or your steps. They only know what you tell them.
When you give too little, they cannot find the cause. They cannot guess. So they ask for more. This is not a test. It is a request for help so they can help you back.
Understanding this changes how you answer. You stop feeling annoyed. You start thinking like a helper.
Read Also: How can customers check Tim Hortons UK menu prices, calories, and breakfast items?
The First Piece Of Information: What You Were Trying To Do
Start with your goal. Tell the person what you wanted to happen.
Do not say "I clicked the button and nothing happened." That misses the goal. Instead say "I wanted to save my report as a PDF file. I clicked the green save button. The button made a click sound but no PDF appeared."
This small change matters. Now the other person knows your target. They know what success looks like. They can compare what happened to what should have happened.
Without the goal, they only see an error. With the goal, they see the full picture.
The Second Piece: The Exact Steps You Took
Write down every step. Do not skip any. Do not assume a step is too small to matter.
Many issues come from one small wrong click. One missed checkbox. One setting that was on when it should be off. If you leave steps out, the other person cannot find that small wrong thing.
List your steps like this:
This level of detail turns a mystery into a map. The other person can walk through your steps one by one. They can try to do the same thing on their end. If the issue does not happen for them, they know the issue is on your side. If it does happen, they know the issue is in the product itself.
The Third Piece: What Happened Instead
Be clear about what went wrong. Use the exact words you saw. Use the exact sounds you heard. Use the exact behavior you observed.
Do not change the words. If the error message said "connection timed out," do not say "it lost the connection." That changes the meaning. "Connection timed out" is a specific error. It points to a specific cause. "Lost the connection" is too loose. It could mean many things.
Also describe what did not happen. If a file should have opened, say "the file did not open." If a page should have loaded, say "the page stayed white."
What did not happen is as useful as what did happen.
The Fourth Piece: When The Issue Happened
Time is a big clue. Give the exact date and time if you can. If you cannot, give a clear window like "this morning around 10" or "last night after I restarted my computer."
Some issues only happen at certain times. They happen when the server is busy. They happen when many people are using the same tool. They happen after a recent update. Knowing the time helps the other person check logs. Logs are records of what a system did at each moment. Without a time, logs are too big to search. With a time, logs become a short list of possibilities.
The Fifth Piece: How Many Times It Happened
Tell the person if this was the first time or the tenth time. Tell them if it happens every time or only sometimes.
This changes what the other person looks for. If it happens every time, the issue is likely a broken setting or a missing file. If it happens sometimes, the issue is likely a connection problem or a timing problem.
For example, a button that fails one out of ten times is different from a button that fails ten out of ten times. The first case points to a problem with network traffic. The second case points to a problem with the button itself.
The Sixth Piece: What You Already Tried To Fix It
Many people try their own fixes before asking for help. That is good. But you must tell the other person what you tried.
If you restarted your computer, say so. If you cleared your saved files, say so. If you reinstalled the program, say so.
This stops the other person from telling you to try the same things again. It saves time. It also tells them something about the issue. A problem that survives a restart is different from a problem that goes away after a restart.
Be honest about what you tried. Even if your fix did not work, that information is useful. It rules out certain causes.
The Seventh Piece: What Changed Recently
Think back. Did anything change before the issue started?
A change could be many things. You installed a new program. You updated your computer. You added new hardware. You changed a password. You moved to a new building with different internet. You gave someone else access to your account.
Even small changes matter. Changing a single setting in one program can break another program. Installing a new app can change how your computer uses its memory.
Write down every change from the last few days. The other person will look at each change as a possible cause.
You May Also Like: How Can Travel Brands Improve Customer Engagement?
The Eighth Piece: Your Setup Details
Give the basic facts about your device and your connection. Do not assume these facts do not matter. They almost always matter.
Include these things:
The type of device (laptop, phone, tablet, desktop)
The name of the operating system (Windows 11, Mac OS, Android, iOS)
The name of the browser if you use one (Chrome, Edge, Safari, Firefox)
The version numbers if you know them
The type of internet connection (wifi, cable, mobile data)
The name of the program where the issue happened
You do not need to know every number. Just give what you can. A device name and a browser name alone can point to known issues.
The Ninth Piece: Screenshots Or Video
Words are good. Pictures are better. A screenshot freezes the exact moment of the issue. A video shows the full chain of steps.
Most programs have a built way to take a screenshot. On Windows, you can press the print screen button. On Mac, you can press shift command 3. On a phone, you usually press the power and volume down buttons at the same time.
Take a screenshot the moment the issue appears. Do not crop the image. Do not draw on it. Send the full screen. The other person can then zoom in on any part they need.
If the issue takes time to happen, take a short video. Many phones have a screen record feature. On a computer, you can use a free tool like the Xbox game bar on Windows or QuickTime on Mac.
The Tenth Piece: Error Codes Or Logs
Some issues show a code. The code looks like a mix of letters and numbers. "Error 404" is one example. "500 internal server error" is another. These codes are not random. Each code points to a specific family of causes.
Copy the code exactly. Do not change any letter or number. Send the whole message, not just the code.
If the program has a log file, offer to send it. A log file is a text file where the program writes down everything it does. It is not easy to read. But the person helping you knows how to read it. They can find the exact line where the issue started.
How To Put All Of This Together
You do not need to write a long essay. You just need to answer each piece in order. A good answer looks like this:
"I was trying to save my report as a PDF. I opened the program at 9 AM. I typed my name and email. I clicked the green save button. The button made a click sound but no PDF appeared. No error message showed up. This happened at 9:05 AM this morning. It happens every time I try to save. I tried restarting the program. That did not help. The only change recently was a Windows update last night. I am using a Dell laptop with Windows 11 and Chrome version 120. Here is a screenshot of the program after I click save."
That answer gives the other person almost everything they need. They can start looking for the cause right away. They do not have to ask six follow up questions. The fix comes faster.
What Not To Do
Do not guess. If you do not know an answer, say you do not know. Guessing sends the other person down wrong paths. It wastes time.
Do not use words like "maybe" or "perhaps" or "I think." Those words add doubt. The other person needs clear facts, not your guesses.
Do not leave out details because you think they are not important. You are not the expert. The person helping you is the expert. Let them decide what matters. Give everything.
Do not get defensive. The person asking for more information is not attacking you. They are trying to solve a problem with you. Keep your tone helpful and calm.
A Simple Checklist You Can Use
Keep this list ready. When someone asks you for more information, go down the list and answer each point.
If you answer all ten of these, you have given the best possible answer. The person on the other side will thank you. The issue will get solved faster. And you will become known as someone who knows how to ask for help the right way.
The One Sentence Summary
Give your goal, your steps, what went wrong, the time, how often, your failed fixes, recent changes, your setup, a picture, and any error code.
That is what additional information looks like. That is how you answer the question completely the first time.
Rajesh Kumar
When someone asks you "what additional information can you provide about the issue," they are not being difficult. They are trying to help you. But they cannot help you unless you give them the right pieces of the puzzle.
Most people stop too early. They say "it does not work" or "there is an error." That is not enough. That kind of answer forces the other person to ask more questions. Each question takes time. Each delay makes the problem worse.
If you want to solve an issue fast, you must learn what to share. You must give the other person exactly what they need the first time. This article walks you through every piece of information you should provide. No shortcuts. No fluff.
Why People Ask For More Information?
The person asking this question does not see what you see. They were not there when the issue happened. They do not know your screen, your device, or your steps. They only know what you tell them.
When you give too little, they cannot find the cause. They cannot guess. So they ask for more. This is not a test. It is a request for help so they can help you back.
Understanding this changes how you answer. You stop feeling annoyed. You start thinking like a helper.
Read Also: How can customers check Tim Hortons UK menu prices, calories, and breakfast items?
The First Piece Of Information: What You Were Trying To Do
Start with your goal. Tell the person what you wanted to happen.
Do not say "I clicked the button and nothing happened." That misses the goal. Instead say "I wanted to save my report as a PDF file. I clicked the green save button. The button made a click sound but no PDF appeared."
This small change matters. Now the other person knows your target. They know what success looks like. They can compare what happened to what should have happened.
Without the goal, they only see an error. With the goal, they see the full picture.
The Second Piece: The Exact Steps You Took
Write down every step. Do not skip any. Do not assume a step is too small to matter.
Many issues come from one small wrong click. One missed checkbox. One setting that was on when it should be off. If you leave steps out, the other person cannot find that small wrong thing.
List your steps like this:
This level of detail turns a mystery into a map. The other person can walk through your steps one by one. They can try to do the same thing on their end. If the issue does not happen for them, they know the issue is on your side. If it does happen, they know the issue is in the product itself.
The Third Piece: What Happened Instead
Be clear about what went wrong. Use the exact words you saw. Use the exact sounds you heard. Use the exact behavior you observed.
Do not change the words. If the error message said "connection timed out," do not say "it lost the connection." That changes the meaning. "Connection timed out" is a specific error. It points to a specific cause. "Lost the connection" is too loose. It could mean many things.
Also describe what did not happen. If a file should have opened, say "the file did not open." If a page should have loaded, say "the page stayed white."
What did not happen is as useful as what did happen.
The Fourth Piece: When The Issue Happened
Time is a big clue. Give the exact date and time if you can. If you cannot, give a clear window like "this morning around 10" or "last night after I restarted my computer."
Some issues only happen at certain times. They happen when the server is busy. They happen when many people are using the same tool. They happen after a recent update. Knowing the time helps the other person check logs. Logs are records of what a system did at each moment. Without a time, logs are too big to search. With a time, logs become a short list of possibilities.
The Fifth Piece: How Many Times It Happened
Tell the person if this was the first time or the tenth time. Tell them if it happens every time or only sometimes.
This changes what the other person looks for. If it happens every time, the issue is likely a broken setting or a missing file. If it happens sometimes, the issue is likely a connection problem or a timing problem.
For example, a button that fails one out of ten times is different from a button that fails ten out of ten times. The first case points to a problem with network traffic. The second case points to a problem with the button itself.
The Sixth Piece: What You Already Tried To Fix It
Many people try their own fixes before asking for help. That is good. But you must tell the other person what you tried.
If you restarted your computer, say so. If you cleared your saved files, say so. If you reinstalled the program, say so.
This stops the other person from telling you to try the same things again. It saves time. It also tells them something about the issue. A problem that survives a restart is different from a problem that goes away after a restart.
Be honest about what you tried. Even if your fix did not work, that information is useful. It rules out certain causes.
The Seventh Piece: What Changed Recently
Think back. Did anything change before the issue started?
A change could be many things. You installed a new program. You updated your computer. You added new hardware. You changed a password. You moved to a new building with different internet. You gave someone else access to your account.
Even small changes matter. Changing a single setting in one program can break another program. Installing a new app can change how your computer uses its memory.
Write down every change from the last few days. The other person will look at each change as a possible cause.
You May Also Like: How Can Travel Brands Improve Customer Engagement?
The Eighth Piece: Your Setup Details
Give the basic facts about your device and your connection. Do not assume these facts do not matter. They almost always matter.
Include these things:
The type of device (laptop, phone, tablet, desktop)
The name of the operating system (Windows 11, Mac OS, Android, iOS)
The name of the browser if you use one (Chrome, Edge, Safari, Firefox)
The version numbers if you know them
The type of internet connection (wifi, cable, mobile data)
The name of the program where the issue happened
You do not need to know every number. Just give what you can. A device name and a browser name alone can point to known issues.
The Ninth Piece: Screenshots Or Video
Words are good. Pictures are better. A screenshot freezes the exact moment of the issue. A video shows the full chain of steps.
Most programs have a built way to take a screenshot. On Windows, you can press the print screen button. On Mac, you can press shift command 3. On a phone, you usually press the power and volume down buttons at the same time.
Take a screenshot the moment the issue appears. Do not crop the image. Do not draw on it. Send the full screen. The other person can then zoom in on any part they need.
If the issue takes time to happen, take a short video. Many phones have a screen record feature. On a computer, you can use a free tool like the Xbox game bar on Windows or QuickTime on Mac.
The Tenth Piece: Error Codes Or Logs
Some issues show a code. The code looks like a mix of letters and numbers. "Error 404" is one example. "500 internal server error" is another. These codes are not random. Each code points to a specific family of causes.
Copy the code exactly. Do not change any letter or number. Send the whole message, not just the code.
If the program has a log file, offer to send it. A log file is a text file where the program writes down everything it does. It is not easy to read. But the person helping you knows how to read it. They can find the exact line where the issue started.
How To Put All Of This Together
You do not need to write a long essay. You just need to answer each piece in order. A good answer looks like this:
"I was trying to save my report as a PDF. I opened the program at 9 AM. I typed my name and email. I clicked the green save button. The button made a click sound but no PDF appeared. No error message showed up. This happened at 9:05 AM this morning. It happens every time I try to save. I tried restarting the program. That did not help. The only change recently was a Windows update last night. I am using a Dell laptop with Windows 11 and Chrome version 120. Here is a screenshot of the program after I click save."
That answer gives the other person almost everything they need. They can start looking for the cause right away. They do not have to ask six follow up questions. The fix comes faster.
What Not To Do
Do not guess. If you do not know an answer, say you do not know. Guessing sends the other person down wrong paths. It wastes time.
Do not use words like "maybe" or "perhaps" or "I think." Those words add doubt. The other person needs clear facts, not your guesses.
Do not leave out details because you think they are not important. You are not the expert. The person helping you is the expert. Let them decide what matters. Give everything.
Do not get defensive. The person asking for more information is not attacking you. They are trying to solve a problem with you. Keep your tone helpful and calm.
A Simple Checklist You Can Use
Keep this list ready. When someone asks you for more information, go down the list and answer each point.
If you answer all ten of these, you have given the best possible answer. The person on the other side will thank you. The issue will get solved faster. And you will become known as someone who knows how to ask for help the right way.
The One Sentence Summary
Give your goal, your steps, what went wrong, the time, how often, your failed fixes, recent changes, your setup, a picture, and any error code.
That is what additional information looks like. That is how you answer the question completely the first time.