Skip to content
Anslation

Persona test · Communication

Customer Support Style test

Customer Support Style is a short self-reflection test on how you handle a customer's problem. Twelve statements place you on three patterns: whether the customer feels heard before the fix, how you settle a clear next step, and when you hand an issue to an owner who can solve it faster.

You sign in or create an Anslation account to take it; your answers save as you go.

By Anslation Editorial Team · Page updated · How scoring works

At a glance

Who it is for
Support agents, helpdesk and service desk staff, the team leads who coach them, and anyone who answers customers by phone, chat or email
Time
About 4 minutes
One question at a time
Questions
12 questions
One at a time
What you get
Where you sit on 3 patterns
A band for each, and practice steps in Grow
Account
Needed for a scored result
Your answers save as you go
Try first
Preview the first questions without an account
Nothing is scored

What it looks at

3 patterns, each a scale between two named ends. Neither end is better: each describes a way of working.

  • Empathy Signal

    Whether you go straight to the fix or first show the customer you understand what went wrong for them.

    Feeds the skill Communication

    What the 3 Empathy Signal bands mean

    Toward the high end, people tend to open with a line that shows they understand what the problem has cost the customer, such as a lost afternoon or a late order, before they start troubleshooting. Someone pressed for time may find that opening slow. Toward the low end, people tend to go straight to the steps that will solve it. That suits a customer who just wants it sorted, but an upset customer may not feel heard, even when the fix works.

    Fix comes first
    You tend to start troubleshooting straight away. The fix gets going quickly, though customers may not hear that you noticed the trouble it caused them.
    This week, open each first reply with one sentence that names what went wrong for the customer, then start on the fix.
    Varies what comes first
    Some customers hear that you understand their trouble before you start fixing it. With others, you go straight to troubleshooting without a word about what it cost them.
    Before each first reply this week, ask yourself whether this customer needs to hear that you understand first or wants the fix straight away.
    Acknowledgement comes first
    You tend to show customers you understand what went wrong for them before you start on the fix. That can settle an upset customer, though one in a hurry may want the fix sooner.
    This week, keep your acknowledgement to one sentence and put the first step of the fix in the same message.
  • Resolution Focus

    Whether you let a conversation run while the issue is messy or settle it on a next step you both confirm.

    Feeds the skill Execution

    What the 3 Resolution Focus bands mean

    Toward the high end, people tend to sort a messy issue into one clear next action and check that the customer agrees before the conversation ends. The issue moves on quickly, but the conversation can close before the customer has said all they wanted to. Toward the low end, people tend to let the conversation continue without confirming a next step. That gives the customer room to explain, but it can end with nothing agreed, and the customer may need to get back in touch to find out what happens next.

    Follows the conversation
    You tend to let a conversation run on while the issue is still messy. That leaves space for the customer to explain, and it can end without a next step you have both confirmed.
    This week, end every conversation by saying what happens next, who does it and by when, and ask the customer to confirm it.
    Confirms some next steps
    You turn many messy issues into a clear next action, though some conversations still end before anyone has confirmed what happens next.
    This week, note which conversations ended on a confirmed next step and which did not, and what was different about them.
    Confirms the next step
    You tend to boil a messy issue down to a single next action and confirm it before the conversation ends. That keeps things moving, though a customer who is still explaining may feel cut short.
    This week, ask the customer one more question about what they need before you name the next step.
  • Escalation Judgement

    Whether you work an issue through yourself or hand it to the owner who could solve it faster.

    Feeds the skill Collaboration

    What the 3 Escalation Judgement bands mean

    Toward the high end, people tend to bring in the person or team who owns that kind of problem as soon as it is clear the owner can solve it faster. The issue reaches its owner sooner, though the customer may have to start again with someone new. Toward the low end, people tend to hold on to an issue and work it through themselves. That can build their own knowledge and gives the customer one contact, but an issue can wait with them longer than it would with its owner.

    Works issues through
    You tend to keep an issue and work on it yourself, even when someone else might solve it faster. The customer keeps one contact and you build your own knowledge, though some issues wait longer than they would with their owner.
    This week, set a time limit before you start on a tricky issue, and when it runs out, bring in the team that owns that area.
    Hands some over
    You bring in another owner quickly on some issues, and on others you hold on longer because you want to solve them yourself.
    This week, each time you keep or hand over an issue, write one line on why, and at the end of the week check which of those choices made a customer wait.
    Hands over readily
    You tend to hand an issue on as soon as you see that its owner could solve it faster. Customers reach that owner sooner, though each handover is a point where they may have to explain the issue again.
    With each handover this week, send the new owner a short note of what you have already tried, so the customer does not have to start again.

About this test

Customer Support Style is a self-reflection test about what you do when a customer brings you a problem. It looks at three patterns: whether you show the customer you understand the trouble before you begin fixing it, how readily you turn a messy issue into a next step you both confirm, and when you hand an issue to someone who could solve it faster.

Read more about this test

It suits anyone who answers customers for a living: support agents, helpdesk and customer service staff, and the team leads who coach them. Your answers to twelve short statements set where you sit on each pattern, for example between the fix coming first and an acknowledgement coming first.

Neither end suits every customer. A customer who only wants the problem gone may prefer a quick fix to a line about how they feel. A longer conversation can bring out the real problem that a quick next step would miss, and keeping an issue spares the customer from explaining it again to someone new.

The result is your own account of how you work with customers now, not how they experience it. Use it to choose one habit to work on, then look for that habit in a few of your recent conversations, ideally with a colleague or team lead. It is not a rating of your support work and should not be used to hire, rank or review support staff.

What you will answer

The test asks 12 questions, one at a time. Answers are saved as you go. The examples below are answered on a 5-point scale, from "Strongly disagree" to "Strongly agree".

  • Empathy Signal

    Before I start on a fix, I show the customer I understand what went wrong for them.

  • Resolution Focus

    I turn a messy issue into one clear next action.

  • Escalation Judgement

    I hand an issue on when another owner could solve it faster.

Examples from this test, shown as text. There are no right or wrong answers.

What you get

A result is a map of your patterns, not a type or a label.

  • Where you sit on Empathy Signal: what comes first when a customer brings you a problem.
  • Where you sit on Resolution Focus: how a conversation reaches a next step you both confirm.
  • Where you sit between solving an issue yourself and handing it to an owner who can solve it faster.
  • A band name for each pattern, written for this test, that describes the habit rather than labelling you.
  • Practice steps in Grow, picked from your result by fixed rules.
Anslation Persona · Customer Support StyleSample
Sample: a result places you on each pattern's scale and names the band you are in. The dots here are an illustration, not anyone's answers. Sample rows: Empathy Signal: Varies what comes first; Resolution Focus: Confirms the next step; Escalation Judgement: Works issues through.

Who it is for and your answers

Who it is for

For support agents, helpdesk and service desk staff, the team leads who coach them, and anyone who answers customers by phone, chat or email.

Your answers and your result

  • Before the first question, you are asked to agree to how your answers are used.
  • A completed result is visible to you and to Persona managers, who can also open your answers in Persona's data tables.
  • A share link is your choice: it shows the test, when you took it, your headline and the band you fall in on each pattern, never your answers, positions or scores, and every link expires.
  • Managers see group figures only once at least 5 people have results, and never a ranking of people.
  • How long each answer takes is recorded, to find questions that are hard to answer.
What you agree to before the first question
I understand this is a self-reflection about how I deal with customers' problems, not a diagnosis or a hiring decision. I agree to my answers being saved to build my result, and to the time each answer takes being recorded to find questions that are hard to answer. People with Persona manager access can open my answers and my result in Persona's data tables.
Self-insight, not a diagnosis or a hiring decision.

Sharing a result safely

Is this test accurate?

It is a self-report: it shows how you see your own habits today, not how others see you, so read it as a starting point. Persona publishes no accuracy or reliability figure for any test. These are the rules this one follows.

  • ConfidenceAnswer at least 11 of its 12 questions for Strong confidence, and at least 6 for Moderate; fewer reads Limited. It says how much a result rests on, not whether it is right.
  • Band edgesEvery pattern: 0–34, 35–65, 66–100. A position between two bands takes the nearer one, and exactly halfway goes to the higher band. Neither end of a scale is better.
  • Enough questionsA test page goes into search only when the test has at least 6 scored questions; this one has 12.
  • Reliability checksOnce 10 people have answered every question, Studio checks how well each pattern's questions agree (Cronbach's alpha). Persona publishes no reliability figures.
  • Version 2Published 10 Nov 2026. A result keeps the scoring of the version it was taken on.

Questions about this test

What is a customer support style test?

It is a test of what you tend to do when a customer's problem lands with you. This test is a short self-reflection, not a skills exam or a hiring screen: twelve statements ask whether you acknowledge the trouble before the fix, whether a conversation ends on a next step the customer has confirmed, and whether you pass an issue to its owner or keep working on it yourself.

How long does the Customer Support Style test take?

About 4 minutes. Twelve statements come one at a time, four per pattern, and for each you choose how far you agree, from strongly disagree to strongly agree.

Do I need an account to get a result?

Yes. A scored result needs an Anslation account. Because every answer is saved, you can stop when a customer needs you part-way through and carry on later.

Does this test measure how empathetic I am?

No. It asks how you usually handle a customer's problem, as you see it, not how much you care. A high position on Empathy Signal means you describe yourself as acknowledging a customer's trouble before you start the fix. Neither end is better: acknowledging first can help an upset customer feel heard, while a customer with no time to spare may want the fix at once, and the same holds for the other two patterns.

Who can see my result?

Besides you, people with Persona manager access can open a completed result. Outside Persona, nobody sees it unless you share it. Sharing gives a link with your band names alone, never your answers, and each link expires and can be turned off sooner. Team figures need at least 5 people other than the reader, and they never rank anyone.

How can I use my result with customers?

Pick the pattern that seems to cost your customers most and try one small change on your next few shifts, such as confirming the next step before each conversation ends. Grow also suggests practice steps, picked from your result by fixed rules. You can retake the test after a few weeks and see where you sit then.

Take Customer Support Style. About 4 minutes, one question at a time. Your answers save as you go.

Persona test · About 4 minutes

Customer Support Style

Start the test