Chat and Email Support Interview Questions

"A little, if I'm honest, but it's not the main reason. The bigger reason is that writing is where I'm strongest. In college I ran the helpdesk inbox for our fest, and I liked that I could check a fact before I replied and get the wording right. I also know non-voice isn't the easy option. You're handling more than one customer at a time, everything you type is on record, and a badly worded line can upset someone as much as a rude tone on a call. That's the part I actually enjoy: getting a clear, kind answer out fast. If a customer needs a call to sort something out, I'm fine arranging that too."

"I finished my commerce degree last year and spent the last eight months at an online store doing order support by email. Before that I tutored school students, which taught me to explain things simply. The proof I'd point to is a set of reply templates I wrote at the store for delivery delays. My lead liked them enough that the whole team started using them, and the number of customers writing back with 'I still don't understand' went down. I want to do this full time now because I like the mix of solving a real problem and getting the words right, and chat adds the speed I'd like to get better at."

"I won't pretend it's never repetitive. What helps me is using my breaks properly, actually getting up from the screen rather than scrolling my phone, because my typos go up when my eyes are tired. I also set myself small goals in a shift, like rewriting one of my saved replies so it's clearer, or getting through the day without a single customer asking me to repeat something. And I remind myself that the tenth person asking about a late order is still asking for the first time. If I start sounding bored in writing, they can tell, even without hearing my voice."

"I'd first collect a few examples, like chats where customers replied to that template asking what it meant, so it's not just my opinion. Then I'd write a suggested version, because it's easier for people to say yes to a fix than to a complaint. I'd take it to my lead or whoever owns the templates, and frame it as something I noticed rather than 'this is wrong'. Something like, 'I've seen a few customers get confused by this line. Would it help if we tried this wording?' Being new, I'd also ask if there's a reason it's written that way, because sometimes there's a legal or policy reason I don't know about."

"On a typing test I usually get around forty-five words a minute with very few errors. In live chat my raw typing isn't really the limit, though. The slow part is reading the customer's message properly and finding the right order or policy. So what I work on is knowing where things are in the tools, using saved replies for the standard parts, and typing only the personal bits fresh. I also never skip a quick read-through before I hit send, because a typo in a refund amount or an order number costs far more time than the two seconds it takes to check."

"For typing, I'd do short timed tests every day and focus on accuracy first, because most tests penalise errors and speed comes with practice. For grammar, I'd revise the things people slip on under pressure: tenses, articles, subject and verb agreeing, commonly confused words like 'your' and 'you're', and punctuation. For the email task, I'd practise with a few typical scenarios, like a late delivery or a refund refusal, using one structure every time: greeting, answer first, details, next step, sign-off. On the day, I'd leave a couple of minutes at the end to read my email once, slowly, because that's where I catch most mistakes."

"There are three word mistakes: 'recieved' should be 'received', 'complain' is the verb when we need the noun 'complaint', and 'with in' is one word, 'within'. But I'd also change the tone. 'Kindly co-operate' sounds like we think the customer is being difficult, and it doesn't tell them when they'll actually see the money. I'd rewrite it as: 'Thanks for letting us know about this. I've raised your refund today, and it will be processed within 7 working days. Your bank may take a few more days to show it, so if it isn't there after that, just reply to this email and I'll chase it for you.' It's correct, it's warm, and it tells them exactly what to do if something goes wrong."

"A customer asked why her refund hadn't arrived, and I replied, 'As mentioned in our policy, refunds take up to ten working days.' Every word was true, but she wrote back that I was lecturing her and asked for a manager. Reading it again, 'as mentioned' sounded like I was saying she hadn't bothered to read. I apologised, told her the exact date her refund was sent, and she calmed down. Since then I avoid phrases that point at the customer's mistake, like 'as mentioned' or 'you should have'. I lead with what I've checked for them, then the facts, and I read my reply once as if I were the one waiting for money."

"A customer wanted to cancel a flight add-on for a refund after the trip had already started, which our rules didn't allow. I didn't want to hide the no in a vague paragraph, because people read that as dodging. So I wrote that I understood why he wanted it removed, then said clearly that I couldn't refund it once travel had begun, with the reason in one short line. Then I told him what I could do, which was make sure the add-on wasn't renewed on his next booking, and I'd already done that. He wasn't thrilled, but he replied thanking me for being straight with him and didn't escalate."

"A customer wrote that her parcel was late and it was her mother's medicine. I was busy and sent our standard delay template, which starts with 'We're excited to have you as a customer!' She replied, fairly, that nobody was excited about this. I apologised straight away in my own words, said I understood it was urgent, and checked the courier tracking live. I found it was at the local depot, got the courier to prioritise it, and told her the exact delivery window. Since then I read the customer's message twice before choosing a template, and I always delete or change any cheerful line when someone is upset or worried."

"I'd answer lightly and honestly, something like, 'No, I'm a real person, and sorry if I sounded like a robot there. Let me sort this properly for you.' Then I'd take the question seriously, because it usually means my last few replies were too templated. So I'd look at what I've sent and change it: use their name and their actual order, cut the stock phrases like 'we regret the inconvenience caused', and write one clear sentence about what I'm doing right now. The customer asking that isn't rude, it's feedback, and it's much better to hear it mid-chat than in a low rating afterwards."

"I'd write something like, 'A week late is a long time to wait, especially when you've been checking the tracking every day. I'm looking into where it is right now.' It doesn't sound robotic because it mentions their real situation, a week late, instead of a phrase like 'we regret the inconvenience caused', which could be pasted into any chat. It's also short, and it goes straight to what I'm doing. Empathy in writing works best in one or two lines. If I write a whole paragraph of sorry before any action, the customer starts to feel I'm stalling."

"A good canned response is accurate, short and written in plain words, and it ends with a clear next step. It handles the part of the answer that's the same every time, like the steps to reset a password. What makes it feel personal is the bit I add. I always put in their name, their actual order or account detail, and one line that shows I read what they wrote, like 'I can see you've tried the reset link twice already.' That takes a few seconds. I also check the template still fits the mood, because a cheerful opening line reads badly to someone who's upset."

"I had three chats open and one was a long billing question. While I was digging into that account, a customer on another chat waited almost five minutes without a reply and left a one-star rating saying nobody was there. The problem wasn't the workload, it was that I gave all my attention to the hardest chat. After that I started sending a quick holding line whenever I knew a task would take more than a minute, something like 'I'm checking your order history now, give me two minutes.' I also glance across every open tab each time I send a message. My wait-time complaints dropped noticeably after that."

"I'd start with the angry payment customer, but only with a short line: 'I can see the payment failed and I'm checking it now.' That takes ten seconds and stops things getting worse. Then I'd answer the simple question, because if it really is one line, I can finish it before the payment check even loads. The quiet customer gets a friendly nudge asking if they're still there and whether they need anything else. After that, the payment issue gets my full attention, with an update every minute or two. If the quiet customer doesn't reply within our idle time, I'd close with a note saying they can come back any time. The goal is that no one waits in silence."

"The mistake usually happens when you type an answer, click away to check something, and come back to the wrong window. So my habits are simple. I type directly into the chat I'm answering, never in a notepad I paste from. Before I hit send, I glance at the customer's name and the topic at the top of the window, which takes a second. When I'm switching a lot, I keep a one-line note per chat, like 'Sam, refund, waiting on bank.' And I'm extra careful with anything containing personal details, like an address or order number, because sending that to the wrong person isn't just embarrassing, it's a privacy problem I'd report to my lead straight away."

"A customer asked how to move his subscription to a new card. My first draft was a long paragraph that explained why the old card had failed, then buried the steps at the bottom. When I read it back, I realised he'd have to read the whole thing to find what to do. I rewrote it with one line saying I'd help him update the card, then four short numbered steps, then one line saying his plan wouldn't lapse if he did it within the week. He replied that it worked first time. Now my rule is that the answer to their question goes in the first two lines, and the explanation, if any, comes after."

"Before writing anything, I'd read it twice and list the five complaints in my own notes, because the angriest one isn't always the most important. Then I'd open with one honest line acknowledging that a lot has gone wrong, without a long apology paragraph. After that I'd answer each point separately, numbered in the same order they raised them, so they can see nothing was skipped. For each one I'd say what I've found and what I've done, not just 'noted'. If one point needs another team, I'd say that and give a time. I'd end with a short summary of what happens next. The worst outcome is answering three of the five, because then they write back even angrier."

"I start with a subject that says what the email is about, like 'Your refund for order 4821', so they can find it later. Then I greet them by name and put the answer in the first two lines, because many people read only that far. After that come the details or steps, in short paragraphs or numbered steps if there's something to do. I close with what happens next and when, and how to reply if something's still wrong. Then a plain sign-off with my name. Before sending I check names, numbers and dates, and that I've answered every question they asked, not just the first one."

"In chat, the customer is there with me, so I write short messages, one point at a time, and check in as I go. It's a conversation. An email has to stand on its own. The customer might read it tomorrow, so it has to answer everything in one go, with a clear structure and a next step, because a back-and-forth by email can take days. Chat can be more relaxed, but it gets too casual when it turns into text-speak like 'u' or 'pls', no capital letters, slang, or a joke when the customer is upset. I usually match the customer's style a little, but I never go below the level I'd be comfortable having in a quality review."

"My quality lead marked me down because I kept closing chats without confirming the customer's issue was actually solved. I'd answer the question and then send the closing template straight away. At first I thought it was harsh, since the customers hadn't complained. But when I checked, a few of them had come back within a day with the same problem, which meant I'd closed too early. So I added one question before every close, asking whether what I'd done had sorted it or whether there was anything still unclear. My repeat contacts went down over the next month and that item stopped showing up in my reviews."

"I'd take the target seriously, but I wouldn't just type faster, because that's what caused the quality drop. I'd pull ten or so of my longer chats and see where the time went. Usually it's things like searching for the right article, asking questions one at a time instead of together, or long gaps while I'm in another chat. Those I can fix: I'd ask for all the details I need in one message, save my own shortcuts for common answers, and get quicker in the tools. Then I'd go back to my lead with what I found and what I'm changing, and ask to review both numbers together in two weeks, so we're not trading one score for the other."

"The main ones are first response time, which is how long the customer waits for a real reply, handle time, resolution rate, customer satisfaction and the quality score from reviews. I'd say handle time is the easiest to game. You can close chats early, push people to email, or send a link instead of solving it, and your handle time looks great while customers come back again. First response time can be gamed too, by sending an instant empty greeting. That's why I'd always look at handle time next to repeat contacts and satisfaction. If handle time drops but people are coming back more, nothing has really improved."

"First I'd make sure I know the confirmed facts, what's happened, what we're doing and what we can promise, so I'm not guessing in a hundred chats. Then I'd write or use one accurate saved reply for the common question and personalise it quickly, which lets me handle more chats without cutting corners. I'd still read each message properly, because in a spike some customers have a different or more serious problem hiding under the same topic. For my lead, I'd suggest things that stop chats arriving: a banner on the site or a message at the start of the chat with the latest update, and a proactive email to affected customers. I'd also note the common questions coming in, so the update can answer them."

"A customer typed, 'How do I delete my account?' The quick answer was to send the steps. But her contact history showed she'd written in the week before about a duplicate charge. So I asked, 'Happy to help with that. Can I ask what's made you want to close it? If it's something I can fix, I'd like to try first.' It turned out she'd been charged twice again and had given up. I found the duplicate payment, raised the refund, and set a flag so billing would check her account. She kept the account. If I'd just sent the delete steps, we'd have lost her and she'd still have been owed money."

"I'd correct it straight away in the same chat. The customer has my wrong answer in writing, and they might act on it tomorrow. I'd write something simple like, 'Sorry, I need to correct something I said earlier. The return window for this item is fourteen days, not thirty. That still gives you until the twentieth.' No long explanation of why I got it wrong. Then I'd check whether they've already done anything based on my first answer, and fix that if needed. After the chat, I'd note it on the ticket in case they come back, and look at why I got it wrong, whether it was my memory or an out-of-date article someone should update."

"A good close has three parts. First I confirm it's actually solved, like asking whether the new login worked. Then I sum up in one line what I've done and anything still to come, such as 'your refund's been raised and should reach your card in five to seven working days.' Then I tell them how to come back if it doesn't, and say goodbye warmly. The problem with a bare 'Anything else?' is that it skips the confirmation and the summary, and a lot of customers read it as 'please leave now'. They end the chat unsure, and then come back tomorrow with the same issue."

"First, I don't reply to the insult itself, and I don't type anything I'd be embarrassed to see in a quality review. If they're angry but still talking about the problem, I try to keep helping. Slurs are different. I'd follow the team's abuse policy, which usually means one clear warning, something like, 'I want to help sort this out, but I can't continue if the messages include abusive language.' If it happens again, I close the chat with a short, polite closing line and tag the transcript as abusive so there's a record. Some teams allow closing straight away for slurs or threats, and I'd follow that. Then I'd tell my lead, take a minute to reset, and make sure the customer's actual issue is still logged for someone to follow up."

"I move a chat on when I can't solve it within my access or knowledge, when it needs documents or investigation that will take hours, or when we're going round in circles in text and a call would sort it faster. I don't escalate just because a customer is annoyed. When I do move it, I tell the customer clearly who'll pick it up, why, and when to expect contact. My handover note says the problem in one line, what I've already checked or tried, anything the customer has sent, and what they actually want as the outcome. The test I use is whether the next person could act on it without asking the customer a single question again."

"First, I wouldn't copy it, repeat it back or use it for anything. Many chat tools have a way to mask or redact a message, so I'd use that straight away, and if ours doesn't, I'd flag the transcript to my lead or follow our data process so it gets removed. Then I'd tell the customer kindly, without making them feel foolish, something like, 'Thanks, but for your safety please don't share full card details here. I can check the payment using your order number and the last four digits.' If they had also shared the security code, I'd suggest they keep an eye on their statement and talk to their bank if they're worried, because it's been typed into a chat log."