
For the Technical Support Representative role, Foundever needs to assess your systematic troubleshooting logic and how you interact with a stressed customer. The process-based questioning reveals whether you can follow protocol and adapt.
Outline steps in a clear, logical order: verify the issue with the customer, isolate (check other devices, cables, lights), restart, check configurations, and escalate if needed. Use the call flow as a structure and demonstrate patience. Mention how you'd document the interaction.
Start by setting a calm tone and repeating the customer's problem back to confirm you understand it, because a stressed caller often just wants to feel heard first. Then gather the simplest facts before touching anything: ask if other devices in the home can connect, whether the Wi-Fi light on the modem is steady or blinking, and if this is a sudden outage or a long-standing issue. Explain that you are isolating the problem step by step, so the customer knows why you are asking. Once you have that baseline, guide them through a physical check of cables and power, then a proper restart of the modem and router, waiting a full minute before powering back on. Use plain Taglish if the customer responds better to it, but keep your explanations short and actionable, like saying "let us refresh the connection" instead of technical jargon. If the connection still fails, check if their device sees the network at all, and if it does, verify the password or try a wired connection to rule out the router. Say plainly that you are documenting each step in the ticket as you go, which reassures the customer that their issue will not be lost. Only escalate after you have exhausted these steps, and hand over a clear summary of what you tried so the next agent does not repeat your work.
Some candidates jump straight to 'restart your computer' without gathering any information, which frustrates customers and wastes time. Others drop into heavy technical talk ('check your DHCP lease') that confuses the caller. Foundever wants a balanced approach: probe, listen, then explain in plain language.
Situation
A few months ago, my cousin's laptop suddenly couldn't connect to our home PLDT Wi-Fi, although his phone was still connected. He had a class presentation in 30 minutes and was panicking.
Task
I needed to quickly identify whether the problem was with his laptop, the router, or the internet provider, and get him back online before his presentation.
Action
I asked him first if any error message appeared and if he had recently changed any settings. I checked if other devices could connect to the same Wi-Fi (they could), then had him restart the laptop and router. When that didn't work, I checked the Wi-Fi adapter settings, found it was disabled, enabled it, and saw that the laptop still wouldn't get a valid IP. I opened Command Prompt, released and renewed the IP address, and finally assigned a static IP as a temporary fix.
Result
He connected in about 15 minutes and joined his class on time. Later that day I explained what happened and showed him how to check the adapter settings himself.
Logical isolation, from the most common cause outward, saves time. Keeping the user calm and asking clear questions is just as important as the technical fix.
Write your own answer, then get instant AI feedback graded against:
Get AI feedback on your answer — free.
3 free AI-graded answers + 1 free mock interview, no card needed.
Sign Up FreeAlready have an account? Log in
Sign in to join the conversation.
No answers shared yet — be the first to show how you'd approach this.