Customer Care / Support

Customer Care / Support, also known as customer support, responds to customers’ questions and difficulties with a product or service. The person in this role understands the problem, provides an answer within their remit and directs cases they cannot resolve to the right person. The role also involves following up on conversations and reporting recurring difficulties so that the company can improve its service.

The role may cover questions about use, complaints or incidents reported by customers. The support professional listens, asks focused questions, restates the need and adapts their response. They may work by phone, email, chat or another channel chosen by the organisation. No particular channel is inherent to the role: its remit depends on the customers, the product and the existing team.

Support records requests, responses and actions already taken. This record means customers do not have to explain everything again when a case is handed over. When a request exceeds the person's authority, they pass it to the relevant team. The division of responsibilities and reporting line vary between companies and contact centres. The role may report to a service manager.

Customer Care / Support, Customer Success and commercial account management: who does what?

• Customer Care / Support: deals with obstacles customers encounter day to day and follows up on the response given to them.
• Customer Success: focuses more on helping customers achieve their goals over time. The boundary between the two depends on the organisation.
• Commercial account management: may include sales or managing a portfolio of accounts. These responsibilities are outside the core of the role described here.

Support may flag points of friction and suggest improvements. That does not, as a matter of course, give the role authority over product decisions or commercial relationships.

The quality of support depends first on understanding the request. A quick response based on the wrong diagnosis may leave the problem unresolved. The role therefore calls for a clear exchange: listen, ask questions, restate the issue, then check that the customer understands the response. When several requests arrive at once, the person must also set priorities according to the situation and their team's guidance. No single response-time rule suits every organisation.

Continuity of case handling is another concern. A case without a clear history is harder for a colleague or another team to take over. Recording the request, the conversations and the actions already taken shows what remains unresolved. The company must specify who takes over a complex case, what information accompanies the handover and who then updates the customer. Passing on the case alone does not settle these responsibilities.

Hypothetical example: a customer describes a problem that an initial response does not resolve. Support reviews the symptoms, records the steps already tried and passes the case to the relevant team. The person explains the planned next steps to the customer according to their organisation's procedures. This illustrates one possible approach; it does not assume that support can carry out the technical fix.

Repeated requests can also help improve the service. Support may flag an unclear explanation, a process that causes difficulties for customers or a recurring problem. Depending on the company, these reports go to the service manager or the teams concerned, including product teams. The role is to describe and document the problem clearly, not to decide on a product change alone.

For hiring, the key question is the actual remit: which requests will the person handle, how far can they respond independently and when must they hand a case over? Someone suited to a role with guided support may not suit one requiring more diagnosis and coordination.

• Receive customer requests through the channels chosen by the organisation.
• Ask questions and restate the problem before suggesting a response.
• Diagnose the situation and adapt the explanation to the customer.
• Prioritise requests when their volume or urgency calls for it.
• Check that the customer understands the response given.
• Record conversations, actions taken and case follow-up.
• Pass unresolved or more complex cases to the relevant team.
• Flag recurring difficulties and suggest improvements to the service or product.

No single qualification captures all the skills useful in Customer Care / Support. When assessing a candidate's background, look at how they handle a real request: listening without jumping to conclusions, asking useful questions, explaining a response and keeping a record of conversations. Customer service experience may develop these skills, provided it involved solving problems and following them up.

The French vocational qualification conseiller relation client à distance is one possible route. It covers receiving customers, identifying needs, giving advice and handling difficult situations, among other activities. It is a level 4 qualification and can also be obtained through experience. Its scope is broader than the support role described here, however: any commercial activities it includes should not become an implicit requirement for the job. The UK occupational profile illustrates other possible routes, through training, an apprenticeship or direct application. These are routes specific to their contexts, not UK rules to apply in France.

Ask candidates to describe the requests they handled, the responses they could give independently and the cases they passed on. An anonymised case file or a detailed explanation can show how they followed a resolution and kept the customer informed. For a product specific to your company, identify what they will need to learn after joining and the resources available to help them learn it.

The existing pay grid distinguishes Support Agent / Support Officer (0-2 years), Experienced / Specialist (2-5 years), Team Lead (5-8 years) and Head of Support (8+ years). These grid categories do not replace an assessment of the responsibilities actually held: handling requests directly, expertise in complex cases or supervising the service.

To assess a candidate, start with the requests the role will handle and the limits of its autonomy. The steps below are suggestions to adapt to your organisation; they do not describe a documented GetPro method.

1. Set the criteria before the interview

Describe the requests the person will handle, the channels used and the cases to pass on. Distinguish between responding to customers, following up on cases and improving the service. Choose observable criteria: the quality of their questions, the clarity of their response, their record of actions and their judgement about handovers. Specify who can approve a sensitive or technical response. A positive sign is a candidate who explains the limits of what they can do. A warning sign is a promise to resolve every problem alone without knowing the product.

2. Examine a past example

Ask the candidate to describe a difficult request: what the customer said, what information they sought, the response they gave and what happened next. Ask what they recorded and who took over the case if needed. Look for a verifiable sequence of events rather than a general statement about customer satisfaction. A good answer distinguishes established facts, assumptions and information to find before responding to the customer. Watch for examples that leave out follow-up after handover.

3. Present a case close to the role

Present a request representative of your product, with some information deliberately missing. Ask the candidate to formulate their questions, then write a short response to the customer. Have them explain what they would record in the case file and when they would ask a colleague for help. A written and oral exercise is consistent with the abilities described in the French occupational standard; it remains an assessment choice, not a hiring requirement.

Hypothetical example: a customer reports a fault without explaining the steps they took. The candidate asks for the missing details, restates the problem and says what they can check. If the case needs to be passed on, they share the relevant facts without announcing an unconfirmed solution. Also observe whether their message to the customer is easy to understand.

4. Observe communication and prioritisation

Add a complaint or a second request to the exercise. Ask how the candidate would keep the exchange calm and choose the next action under the team's guidance. A strong answer explains the priority chosen and what will be communicated to the customer. A warning sign is an abrupt response or arbitrary ranking of requests. If the role includes managing others, assess separately how the person would help colleagues take over cases.

5. Compare observations and take references

Compare notes from the interview and exercise with the criteria set at the outset. Ask permitted referees to describe responsibilities the candidate actually held: types of request, autonomy, follow-up and handovers. If your team lacks expertise in some cases, involve someone who can assess the diagnosis and quality of the handover. Assess customer communication separately from technical problem solving, so that verbal confidence is not mistaken for mastery of the role.