Chat support interview questions, and what to listen for

By the time you interview a chat support applicant, you should already have seen them write. A short work sample shows that far better than a call can. Five chat tests to give before you hire a support agent has a set you can use.

So the call has a different job. It is for what writing cannot show: how the person thinks, what they have really done, and whether the job fits their week. Below are fifteen questions for that, with what to listen for in each answer.

How to run the call

• Keep it short. Thirty minutes is enough for a chat agent.
• Ask everyone the same core questions. Then you can compare answers afterward. Add follow-ups freely.
• Have their test answers open. Some of the best questions are about their own work.
• Ask "What happened next?" A real story has a next step. A made-up one usually stops.
• Write one line of notes per question while you listen. Memory blurs fast after three calls.

Questions about the work they have done

1. "Tell me about your busiest chat shift. How many chats were open, and how did you keep track?"

Listen for a number and a method. For example: closing quick questions first, sending short "checking that now" messages, keeping notes. A weak answer is "I'm good at multitasking," with nothing after it.

2. "Tell me about a chat that went badly. What did you do, and what would you do differently now?"

Listen for a real story where they own part of what went wrong. Be careful with "That never happened to me." Everyone who has done this job has a chat like that.

3. "Which chat or help desk tools have you used? What annoyed you about one of them?"

People who have really used a tool have opinions about it. Do not reject anyone for not knowing your tool. Tools can be taught; judgment is harder to teach.

4. "What did customers ask about most in your last job?"

Listen for details: order status, password resets, billing, bookings. Vague answers here are worth a follow-up question.

Questions about judgment

5. "A customer asks for something you are not allowed to give. What do you write first?"

A strong answer says no clearly, then offers what they can do. Watch for "I'd just give it to keep them happy." That habit costs money and trust.

6. "When do you pass a chat to someone else, and what do you tell the customer?"

Listen for clear limits and a handover the customer can follow: who will reply, and when. A weak answer passes the chat on and says nothing to the customer.

7. "You don't know the answer, and nobody on the team is online. What do you do?"

A strong answer does not guess. It tells the customer what will happen and when, and asks the team as soon as someone is back. A confident guess is the weakest answer here, because the customer acts on it.

8. "A customer is rude to you in the chat. How do you reply?"

Listen for someone who stays on the problem, does not take the bait, and knows when your rules say a chat can be ended. A weak answer either matches the tone or apologizes in every line and fixes nothing.

9. "You find out you gave a customer wrong information an hour ago. What do you do?"

This is one of the most useful questions on the list. A strong answer writes to the customer, corrects it, and tells the team lead. Someone who would "hope they didn't notice" will hide bigger mistakes later.

Questions about their own test

10. "In the test, you offered the customer a replacement. Why that, and not a refund?"

Pick a real choice from their own answers. Someone who wrote the reply can usually explain it. If they cannot, ask kindly how they wrote it, and judge them against the rules you gave before the test.

11. "If you could redo one reply from your test, which one, and what would you change?"

Good agents review their own work. Listen for a specific change, not "I think they were all fine."

Questions about the job's facts

12. "The shift is [days and hours, your time zone]. That is [the same hours in their time zone]. How does that fit your week?"

Always say the hours in their time zone. Then listen for a plain yes, or an honest problem you can solve now.

13. "Where will you work from, and what do you do if your internet or power goes out?"

Cuts happen everywhere. Listen for a real backup plan: mobile data, a second place to work, and telling the team right away.

14. "Do you have other work during these hours? When could you start?"

Some agents hold two part-time jobs. That can be fine, as long as the hours do not overlap.

15. "What questions do you have for me?"

Questions about your customers, your tools or how training works show real interest. No questions at all is not a reason to reject, but it is worth a note.

Signs worth a follow-up question

None of these is a verdict. Each is a reason to ask one more question.

• Every answer is general, with no example in any of them.
• They cannot explain a choice in their own test.
• They promise customers things in their stories that a company would not allow.
• They speak badly of every past customer or employer.

Questions to leave out

Ask only what helps you judge the work. Leave out questions about family plans, religion and health, and do not ask for a photo.

Do not ask for a birth date, or for an age in years or a bracket. If your applicants are in the Philippines, Republic Act No. 10911, Section 5(a), makes it unlawful to "require the declaration of age or birth date during the application process." You can read the full text of RA 10911, and what you can't ask Filipino applicants explains what to ask instead. HireFlow's own form asks every applicant only "Are you 18 or older?"

Marital status is out too. The Philippine Data Privacy Act (Republic Act No. 10173) lists it, with age, among "sensitive personal information."

This section is general information, not legal advice. Check with a lawyer for your own case.

A note sheet to copy

Use one sheet per applicant, with the same rows for everyone.

Applicant: [name]            Date: [date]

Question   Score (1-3)   One line of evidence
1          [ ]           [e.g. "8 chats, closes quick ones first"]
2          [ ]
...
15         [ ]

Biggest strength:
Biggest doubt:
Next step: [offer / second call / no]

Score each answer as you go, then write the strength and the doubt before the next call starts.

Using an interview guide

If you use HireFlow, each applicant's profile has an interview guide for this call: the same core questions for everyone, plus a few written for that person from their own test answers. You still run the call, and you still decide.

In short

• See them write before you call them. Use the call for what writing cannot show.
• Ask everyone the same core questions, and ask "What happened next?"
• Cover their past work, their judgment, their own test answers and the job's facts.
• Treat weak signs as questions, not verdicts.
• Leave out birth date, age in years or a bracket, marital status, family, religion and health.
• Score each answer while you listen, with one line of evidence.