“I already restarted it three times.”
Read the previous attempts before sending another polished support reply.
The question
Bellmere is a fictional healthcare group with clinics, offices and a supply warehouse. A colleague needs to join a supplier call in fifteen minutes. The support history and alternate route below are authored practice evidence.
- 09:30
- User reported no microphone audio in the browser meeting application.
- 09:33–09:42
- User restarted the browser, restarted the laptop and signed out/in. The microphone still does not work. The user is frustrated.
- AI draft
- I understand how frustrating this is. Please restart your laptop and sign in again.
- Unasked comparison
- No record shows which microphone is selected or whether it works in the approved local audio test.
- Approved fallback
- The meeting invitation includes an approved dial-in number. Support can offer that route while investigating browser audio.
“Give a short response that moves the case forward and protects the call.”
Not saved by this site. Your browser may restore text when you navigate back.
A strong answer, step by step
Open each step in turn. This is one strong answer, not the only one.
Step 1: Acknowledge the actual history
What would you do here? Open the move you’d make.
Send the AI draft to show empathy quickly
Tempting, but it misses something. It repeats failed work and shows that the history has not been used.
Name the completed steps
The strong move. Specific acknowledgment shows that the next support interaction starts from the existing record.
See how a strong candidate says it
“You have already restarted the browser and laptop and signed in again. I will not ask you to repeat those steps.”
Why it works: Specific acknowledgment shows that the next support interaction starts from the existing record.
Step 2: Request one new comparison
What would you do here? Open the move you’d make.
Ask for every available system log first
Tempting, but it misses something. A broad collection delays a simple, discriminating check and may collect unnecessary data.
Check the selected input and local audio test
The strong move. One relevant check is more useful than another general reset.
See how a strong candidate says it
“Please check the selected microphone and run the approved local audio test. That will help separate the device/input path from the browser meeting application.”
Why it works: One relevant check is more useful than another general reset.
Step 3: Protect the immediate task
What would you do here? Open the move you’d make.
Offer and verify the approved dial-in route
The strong move. An approved workaround can protect the task without claiming a repair.
Promise that another browser restart will fix it before the call
Tempting, but it misses something. The prior attempts do not support that promise.
See how a strong candidate says it
“The call is soon. You can use the invitation’s approved dial-in route while we continue the microphone investigation. Please confirm that it connects.”
Why it works: An approved workaround can protect the task without claiming a repair.
Step 4: Keep ownership
What would you do here? Open the move you’d make.
Ask the user to contact the next team directly
Tempting, but it misses something. That loses context and transfers the work of the handover back to the user.
Preserve the history and state the next update
The strong move. The next owner should not make the user start again.
See how a strong candidate says it
“I will record the input/test result and the steps already tried. If the next check does not isolate it, I will hand that record to the audio-support owner and update you after the call.”
Why it works: The next owner should not make the user start again.
The answer, in short
- Decision
- Use the history, ask one new comparison, and protect the call with the approved fallback.
- Because
- The AI draft repeats three unsuccessful actions and does not address the immediate work deadline.
- What would change it
- The local audio test and selected input will determine the next technical path; the fallback is not a microphone repair.
Common traps
- Replacing useful acknowledgment with generic empathy.
- Treating a workaround as closure.
Check your answer
- Did you name the steps already tried?
- Did you ask for one new discriminating check?
- Did you verify an approved way to join the call?
- Did you retain ownership and the history?
Last reviewed Nov 10, 2026