Call Center / Phone Support Specialist (SMB, Entry-Level) Hiring Guide

Attention to Detail Tasks

These tasks are designed to assess the candidate's ability to catch errors, follow detailed information, and maintain accuracy in typical call center documentation scenarios. Each task includes a specific data set or text where the candidate must spot issues or inconsistencies. The tasks are deterministic - meaning there are clear, correct answers that an attentive person should identify.

• Task 6.1: Proofreading a Customer Email Draft - Spelling/Detail Check. The candidate is given a draft of an email that a support specialist might send to a customer, but the draft contains several errors. For example: "Hello John, Thank you for reaching out. Your case ID 4590 has been resolv. We appologize for any incovenience. If you have any further question, don't hesitate to contact us. Sincerely, Support Team" The task: Identify at least three errors or issues in the above email draft. The expected correct details are: the word "resolv" should be "resolved"; "appologize" is misspelled (should be "apologize"); "incovenience" is misspelled (should be "inconvenience"); "question" should be plural ("questions") or phrased as "any further questions"; and there's a missing apostrophe in "don't" (should be don't). The candidate should list the specific mistakes. This tests attention to written accuracy and professionalism - a critical skill when sending written communications to customers.
• Task 6.2: Data Consistency Check (Customer Record) - Cross-verifying information. The candidate receives two pieces of information that should match, and must spot if they do not. For example, they might see an account name in a CRM and a name in an email and verify if they are the same. Specifically: Record in CRM: "Martina Lopez - Account #100567" Email from customer: "Hello, this is Martina Lopes, I need help with my account (ID 100567)..." The task: Determine whether the customer's name in the email matches the official record, and highlight any discrepancy. In this case, the last name spelling differs ("Lopez" vs "Lopes"). The correct action would be to notice the one-letter difference - an indication that either the customer mistyped or the record might be wrong - and double-check which is correct. A candidate with sharp attention to detail will catch that minor discrepancy. Similar subtasks could include checking if an order number referenced by the customer exists in the system, or if two entries (like shipping address on file vs what customer says) are identical. The focus is on spotting one-off errors in alphanumeric data - akin to verifying account numbers, phone numbers, or names for accuracy

• Task 6.3: Invoice/Calculation Verification - Numerical accuracy. The candidate is given a short mock invoice or order summary and asked to verify if the totals are correct. For example: Support Ticket Note: "Customer was charged for 3 items: Item A - $50, Item B - $40, Item C - $50. Total billed = $150." The task: Spot the arithmetic error in the ticket note. Adding $50 + $40 + $50 actually equals $140, not $150. So the total billed is incorrect (or one of the item prices was recorded wrong). The candidate should identify that the sum does not match and specify the discrepancy. In a real scenario, an agent might catch such an error before telling the customer the wrong amount or before closing out a billing issue. This task ensures the candidate can do basic math and verify totals - a necessary skill for handling billing questions or adjusting charges. Other examples could include checking a discount application (e.g. 10% off $200 should be $20 off, see if the adjusted price is correct) or verifying times (call started vs call ended times to see if duration makes sense). The key is to present a clear factual inconsistency in numbers that a detail-oriented person will catch and correct.
• Task 6.4 (Optional Variation): Missing Information in a Call Log - Completeness check. Provide the candidate with a short call log entry or support ticket that is missing a crucial piece of information, and ask them to identify what is missing. For instance: Ticket #1234: "Caller: Mike Brown. Issue: Software crash when saving file. Actions: Provided workaround by saving to alternate location. Next step: - ." In this entry, perhaps the "Next step" is blank or the resolution is incomplete. The task: Notice that the ticket does not record whether the issue was fully resolved or if a follow-up is scheduled. The expected answer might be, "The log is missing the outcome/next step - it doesn't say if the issue was resolved or if Mike needs a follow-up call." This tests whether the candidate pays attention not just to what's there, but what should be there in a standard documentation. An attentive candidate would realize every ticket should have a clear resolution or next action listed, and flag if it's absent. (The assessment can include 3-5 of these micro-tasks. Each has a clearly correct answer or set of mistakes to find. The candidate's performance is measured by whether they correctly identify all or most of the embedded errors. In a scoring context, partial credit can be given if they catch some but not all issues, but all issues are predetermined and objectively verifiable.)

These tasks simulate real workplace communications - especially writing emails or messages - that a Phone Support Specialist would need to produce. The goal is to assess the candidate's written communication clarity, tone, and professionalism. Each prompt should elicit a short written response (a few paragraphs or less) that can be evaluated for content and tone. Example prompts include:

Task 7.1: Apology and Resolution Email to an Upset Customer - The candidate must write an email responding to a customer who had a bad experience. Scenario: A customer wrote in complaining that they had called twice about an issue and it still isn't fixed. They are very frustrated and mentioned possibly canceling their service. The task for the candidate: Draft an email that apologizes for the inconvenience, acknowledges the frustration, and outlines what will be done to resolve the issue. The tone should be empathetic and assuring. The email should include an apology (e.g. "I'm sorry for the repeated trouble you've faced..."), a statement of understanding ("I understand how frustrating this must be..."), and a clear plan or next step ("I have escalated your case to our senior technician and will personally follow up by [date] with a solution..."). This tests written empathy and the ability to restore trust. We expect proper business email format (greeting, body, closing) and a customer-centric tone that turns the situation around.

Task 7.2: Follow-Up Email Confirming Resolution - Scenario: You resolved a customer's issue during a call (say, a technical glitch that you walked them through). Company practice is to send a follow-up email summarizing the resolution and providing any additional info. The task: Write a brief follow-up email to the customer (who is no longer on the phone) summarizing what was done and offering further help if needed. For example, "Thank you for calling earlier. This email is to recap the solution we implemented..." The email should clearly state the issue that was resolved ("As discussed, we reset your account settings which resolved the login problem.") and encourage them to reach out if there are any more issues. The tone should be professional, concise, and friendly - no errors in grammar or detail. Essentially, we're looking at the candidate's ability to communicate technical steps or outcomes in plain language and leave a good final impression.

Task 7.3: Internal Chat Message for Help - Scenario: You're on a call with a customer who has a complicated question you're not sure about. Instead of placing the customer on a long hold, you decide to quickly ask a teammate in the company's Slack channel or Microsoft Teams chat for help. The task: Compose a chat message to a colleague (or a small team group) briefly explaining what you need without revealing any sensitive customer info (since chats are internal). For instance, "@Team - I have a customer on the line with [issue]. I recall you dealt with something similar. Can anyone confirm the fix for [specific scenario]? Thanks!" We are evaluating if the candidate can succinctly and politely ask for help, providing enough context to get an answer quickly. This also shows their collaboration style. The message should be respectful of colleagues' time (maybe tag the right person if known, use please/thank you) and clearly state the problem. It should not contain anything unprofessional (no slang or complaining about the customer). Essentially, can they use internal communication effectively under pressure?

Task 7.4: Customer Announcement Message - Scenario: There's a planned service outage (or an office closure, etc.) that will affect many customers. The support team is responsible for informing any customers who contact or perhaps sending a proactive notification. The task: Write a short, clear notification message about the situation, suitable to be emailed to a customer who inquires

or possibly posted on the company's support portal. For example, "Dear customers, we want to inform you that on [date] from [time] to [time], our servers will undergo maintenance, during which the service will be unavailable...". This tests the candidate's ability to convey important information in a concise and neutral tone, giving necessary details (time, impact, any action needed from customer) and apologizing for inconvenience if appropriate. In an SMB, support staff often have to draft such communications. We'd check that the candidate's draft is well-structured (perhaps bulleting key info), free of ambiguity, and professionally worded.

(All communication task responses will be evaluated on clarity, tone, correctness, and completeness. The assessor will have an ideal answer or checklist for each: e.g., did the apology email contain apology + ownership + next steps? Does the follow-up email recap accurately and politely? We look for a polite, helpful tone and error-free writing above all.)

Tasks (Simulations with Step-by-Step Expectations)

These tasks simulate actual process-oriented work the specialist would do, requiring the candidate to outline steps or demonstrate how they would handle specific technical/support procedures. Each task is deterministic in that there's a generally correct set of steps or actions expected, reflecting best practices and company policy. We will use realistic scenarios where the candidate must explain what they'd do, in order:

Task 8.1: Logging and Documenting a Support Call - Simulation: The candidate is asked to walk through how they would document a customer call they just handled. For example, "Describe the key details you would record in the ticketing system after resolving a customer's issue on a call." The scenario can provide a brief context: say a customer called because their software was erroring out, and you helped them by clearing their cache. Now you need to document it. The expected step-by-step answer should include:

Customer Identification: State the customer's name or account ID in the ticket.

Issue Summary: A concise description of the customer's problem (e.g., "Customer's application crashed when saving file").

Actions Taken: Note each troubleshooting step or solution applied (e.g., "Walked customer through clearing cache and restarting the app").

Outcome/Resolution: Indicate whether it was resolved (e.g., "Issue resolved; customer able to save file after cache clear") or if it's escalated/pending.

Next Steps if any: If follow-up is needed (callback, monitoring, escalation reference number), include that.

Time/Date and Agent: (The system often logs this automatically, but mention if needed that you ensure the correct time is logged and your name is on the ticket.)

Tags/Categorization: The candidate might mention selecting the appropriate issue category or priority in the system.

Essentially, we're looking for a thorough answer that hits all major points of a good call log. They should not omit crucial info (like what was the resolution or who the customer is). A top answer might even include documenting the customer's tone or satisfaction ("Customer was satisfied with the solution") if that's part of policy. Scoring will credit each element present. Missing a major element (like forgetting to record what solution was given) would be a mistake. Reference Best Practice: Good escalation documentation practices involve including customer info, issue, attempted solutions, and state for next agent

, so we expect similar thoroughness.

Task 8.2: Escalation Procedure - Simulation: The candidate is given a scenario where escalation is required and must outline how to handle it. Scenario Example: "You have a caller whose problem you cannot solve (it's beyond your access/knowledge), and the customer is getting angry. Describe the steps you take to escalate this call to a Tier-2 specialist or supervisor." The expected steps (which the candidate should articulate in order) include:

Recognize Need to Escalate: State that after attempting initial troubleshooting, you determine this

requires higher-level support (e.g., a technical bug or a policy exception outside your authority) .

Inform the Customer and Set Expectations: Tell the customer you will escalate to someone who can help further. Use a reassuring phrase like "I'm going to connect you with our senior specialist who has the tools to resolve this for you", and explain what will happen next (for instance, whether you will transfer them or have someone call back)

Promise they won't have to repeat themselves - you'll brief the next person.

Gather Key Information for Transfer: While keeping the customer on hold briefly (or just before transferring), compile all relevant details to pass on. According to best practices, document the customer's name, issue summary, what steps have been tried, what the customer wants, and the customer's mood/urgency

In an ideal answer, the candidate mentions taking notes like these either in the ticket or on paper to relay.

Warm Transfer if Possible: Describe attempting a warm transfer: contacting the Tier-2 or supervisor, conveying the situation (issue and steps attempted) while customer is on hold, then conference/transfer the call so the customer can continue seamlessly

If a warm transfer isn't possible, the next best step is scheduling a timely callback and informing the customer of that arrangement

Document and Follow-Up: After transferring or ending the call, ensure the ticket is updated to reflect the escalation and that the next team has all info. Possibly mention that you would set a reminder to check that the customer was indeed helped, especially in an SMB where follow-through is critical.

We will score the candidate on including the above steps in a logical order. A strong answer demonstrates not only knowledge of what to do (get a supervisor, etc.) but how to do it professionally (keeping customer informed, not making them repeat details). For instance, failing to mention explaining the situation to the next agent would lose points, since a good agent should never blindly transfer without context

Also, ignoring the customer's emotional state would be a miss - the candidate should mention acknowledging frustration and ensuring a smooth handoff. Essentially, do they know how to escalate properly without dropping the ball?

Task 8.3: Step-by-Step Troubleshooting Simulation - Simulation: Present a common technical problem and ask the candidate how they would troubleshoot it on a call, step by step. Scenario Example: "A customer calls saying they cannot log in to their account. What steps would you guide them through to resolve the login issue?" The expected solution approach:

Basic Credential Check: Ask the customer to verify they are using the correct username/email and password (often the simplest issues are typos or caps lock issues). Possibly have them try re-entering credentials carefully.

Password Reset if Needed: If they forgot the password or it's not working, walk them through the "Forgot Password" reset process. (Check if they have access to their email to receive the reset link, etc.)

Account Status Check: While they attempt that, the agent should check on their end if the account is locked or suspended (for security, etc.). Mention unlocking account if there were too many failed attempts, or ensuring no hold on the account.

Browser/Cache Step (if applicable): If credentials are correct but it still fails, ask them to try a different browser or clear cache, in case it's a browser issue.

Verification: Once reset, have them try logging in again. Confirm if successful.

Escalation if Unresolved: If these steps do not work (for example, it might be a deeper system issue), inform the customer you will escalate to IT. Possibly collect a screenshot of error if on phone or note error message for escalation.

Document Outcome: Note what was done (e.g., "reset password and user logged in successfully" or "unable to resolve, escalated to IT Tier2 - reference ticket #").

The candidate's answer should closely mirror a logical troubleshooting flow - start from simple/common causes, then to more involved solutions, and know when to escalate. We will have a checklist of key steps expected: e.g., did they mention verifying password or resetting it? Did they consider account lock? Did they plan to escalate if not solved? Missing a fundamental step (like skipping straight to escalation without even trying password reset) would indicate poor problem-solving. Conversely, a well-structured, calm approach shows technical aptitude and customer service mindset. Similar tasks could be posed (e.g., "customer's device won't turn on" expecting steps: check power, cables, battery, etc.), but the login scenario is broadly applicable. Scoring is based on whether they cover all reasonable steps in order and communicate that they would keep the customer informed throughout (e.g., not just silently doing things, but telling the customer "Let's try X next...").

• Task 8.4: Handling Concurrent Customer Contacts - Simulation: Describe how to handle a situation where multiple support channels collide. Scenario: "You are in the middle of writing an email response to a customer's query when that same customer unexpectedly calls the support line. You recognize it's the same issue you were about to email them about. What do you do?" Expected answer: The candidate should outline a process such as: pause drafting the email and take the call (since live call takes precedence), help the customer on the phone, then afterwards update/close the email query to avoid duplication. Steps might include finding the email/ticket to use context during the call, informing the customer "I see you emailed us; I'm glad we connected by phone so we can resolve this faster," then resolve on phone, and finally log that the email ticket is resolved via call (or send a brief follow-up email stating that per the call, the issue is handled). This scenario checks if they can keep information synchronized across channels and not double-handle or confuse the customer. A candidate who fails to mention one of the channels (like forgetting to close the loop on the email) would lose points. We look for an answer that shows organizational ability and awareness of multi-channel coordination (common in SMB support where the same person may handle all channels). (Each of these technical/process tasks has a clear ideal approach. During evaluation, the candidate's listed steps will be compared to the expected steps. Credit is given for each correct step or decision in sequence. Skipping critical steps or taking them out of order (where order matters) would be marked as a mistake. These simulations also allow assessment of the candidate's practical knowledge of tools and policies - for instance, knowing to check account status in a login issue, or how to properly perform a warm transfer. They should demonstrate both technical reasoning and adherence to good customer service process.)