Senior Customer Support Representative
Job description, salary, sourcing, interview questions and a 30/60/90 plan to hire a Senior Customer Support Representative in a German SMB.
Compiled by the Join team from public data and our hiring experience.
Updated
At a glance
- Median salary€44,000€37,000 – €54,000
- Time to fill45–70 days
- Experience6–12 years
How to hire a Customer Support Representative for your SMB
Before you write the job posting, settle three questions. They decide whether a new hire is the right lever and which profile you actually need.
Question 1: Are you looking for a Customer Support Representative, a Customer Success Manager or a pre-sales person? The three roles share customer proximity, but their posture differs fundamentally. The Customer Support Representative reacts to incoming tickets from any customers with no assigned portfolio; the Customer Success Manager proactively steers a defined portfolio of strategic accounts and carries net revenue retention; the pre-sales person qualifies incoming leads and supports sales on technical questions before the close. Hiring a support representative and then assigning them pre-sales questions or portfolio steering is the most common mistake of SMBs at the end of the seed phase. If your main need is to reduce ticket response time and you handle incoming queries of any customer size, hire a support representative; for net revenue retention on a defined portfolio you need a CSM; for pre-sales volume you need an SDR or a pre-sales engineer.
Question 2: Over which channels and in which languages should your support work? Email alone, live chat plus email, or live chat plus email plus phone produce different profiles. A pure email support rep can be a very strong writer without typing fast enough in live chat; a live-chat rep needs 60+ WPM typing speed and multi-tasking; a phone rep needs a clear voice, good pace and stress resistance in direct conflict. The language profile similarly: German C1 as the base, English B2 in B2B SaaS, every further language (French, Dutch, Spanish) as a plus with a concrete salary premium in the market. Define the channel mix and the language profile explicitly in the posting; a mismatch here costs you 3 months.
Question 3: What SLA targets are you aiming at, and how do you measure? First response time under 1 hour plus resolution time under 24 hours plus CSAT at least 4.3 out of 5 is a realistic trio for a B2B SaaS SMB with medium ticket complexity. More aggressive SLAs (first response under 15 min) require several shifts or a larger team and drive labor costs up disproportionately; weaker SLAs (first response over 4 hours) are no longer competitive in the B2B SaaS market and cost you conversion and retention. Settle the targets before hiring and communicate them in the interview; candidates who have never worked under an SLA framework need more coaching in the first 60 days, which you must plan for.
If the three answers converge on a full-time Customer Support Representative (and not a CSM, SDR or pre-sales engineer), use the posting template below.
JD template
Customer Support Representative (m/w/d), German SMB
[Company name], a B2B or B2C SMB in [sector] based in [city], [X] employees, [X] M€ revenue, is looking for a Customer Support Representative to handle incoming customer queries over [channels: email / live chat / phone] in [languages: German / English / others].
Mission
As Customer Support Representative you handle incoming customer tickets daily over [channels], ensure clear and friendly responses within the defined SLA windows and actively contribute to improving our knowledge base and self-service content. You report to the [Head of Customer Support / Head of Customer Experience / Operations Manager].
Key responsibilities
- Handling [X] tickets per day over [email / live chat / phone] with consistent writing quality and a friendly tonality.
- Meeting the SLA: first response time under [1 hour], resolution time under [24 hours] for standard tickets.
- Triaging complex or escalation-worthy tickets to Tier 2, engineering or the manager with a compact summary.
- Keeping structured notes in the ticketing tool [Zendesk / Intercom / Freshdesk] and in the CRM [HubSpot / Salesforce]; consistent use of tags and macros.
- Contributing to the internal knowledge base and the self-service portal: proposals for FAQ articles, macro extensions and documentation improvements from recurring tickets.
- Structured feedback of customer concerns to product and engineering with business context; participation in weekly team rituals (stand-up, ticket review, writing coaching).
- Participation in shift rotations and SLA readiness according to the defined shift plan.
Profile
- Required: first experience in a customer-facing role (customer service, retail, hospitality, call center); German C1 spoken and written; very good writing quality (spelling, grammar, clear sentences); a service mindset with demonstrable resilience under load.
- Desired: experience with a ticketing tool (Zendesk, Intercom, Freshdesk, HubSpot Service); English B2 or higher; a further language (French, Dutch, Spanish); familiarity with B2B SaaS or a technically complex product.
- Disqualifying: typos in the cover letter; no concrete examples of interactions with dissatisfied customers; no willingness to do shift rotations, if relevant for the role.
What we offer
- Gross annual compensation: fixed [30-42] k€ depending on experience and language profile. An optional variable component up to 5 % indexed to CSAT, if part of the bonus program.
- Model: [full-time, hybrid 2-3 days per week on-site, based in [city] / fully remote within Germany].
- Benefits: [company pension, bike leasing, employee shares, vacation, home-office policy, professional development].
- Stack: [ticketing tool, CRM, Slack, Notion / Confluence, product-usage analytics].
Salary band
Base salary, gross annual
- 25th percentile
- €37,000
- Median
- €44,000
- 75th percentile
- €54,000
Gross fixed salary per year for a senior Customer Support Representative (6 to 12 years of experience) at a German B2B or B2C SMB. Stepstone's dedicated Senior-Kundenberater:in data shows a clear step-up over the general population: profiles with 5 to 7 years sit toward the lower end of this range, profiles with 10+ years toward the top. SaaS and tech scale-ups in Berlin, Munich and Hamburg trend upward; classic e-commerce, telco or mail-order employers trend downward. Ownership of complex escalations, mentoring of junior reps, and a second or third language typically place a profile in the upper half of the band. A small variable component (up to 5 % of the fixed), indexed to CSAT or first-response time, remains possible but is not standard at senior level either.
Sources: Stepstone Gehaltsdaten Senior-Kundenberater/in Deutschland 2026; Stepstone Gehaltsreport 2026; kununu Gehaltscheck Kundenberater / Kundensupport (Methodik: Selbstauskunft, als Kontrolle nutzen)
Where to source this role
Stepstone
From €995 / 30 daysThe strongest channel for entry-level support profiles in Germany. Stepstone aggregates the largest volume of actively searching candidates with experience in customer service, call centers or e-commerce support. For an entry role, expect 60 to 100 applications in 3 weeks; what is decisive is the filter logic in screening, not the reach. Keep the job ad under 400 words and make the language profile (German C1 plus English B2 as a minimum for B2B SaaS) clear.
Indeed
€150-300 / month as a sponsored jobHigh reach to entry-level and career-changer profiles, especially from retail, hospitality and tourism, who want to move into customer support. A weaker signal than Stepstone on structured SaaS support profiles, but strong on profiles with a high service affinity and a natural feel for language. Activate a sponsored job from €3 per click; organic visibility drops sharply after 7 days.
LinkedIn
€200-400 / month for Job SlotsImportant for English-speaking support profiles at SaaS scale-ups in Berlin, Munich and Hamburg, especially for applicants with an international background. Weaker for classic German SMB profiles outside the tech hubs. Job Posts plus targeted sourcing via Recruiter Lite for profiles with first tool experience (Zendesk, Intercom, Freshdesk); with a pure job-post strategy, low output for this role.
Evaluation playbook
The Customer Support Representative role reveals itself across five evaluation stages. The written ticket response (stage 4) is the most predictive; that is where empathy, writing quality and product understanding come out at once. Validation comes from accumulation, not from a single stage.
Stage 1: CV and cover-letter review
Watch for two signals: the writing quality of the cover letter (spelling, sentence structure, tone) and consistency in the CV on customer-facing stations. A candidate with 2 years of hospitality, 1 year of retail and a short stint of travel often has more service reflexes than one with a pure internship CV with no customer contact. Check the language profile: German C1 minimum, English B2 for B2B SaaS, every further language (French, Dutch, Spanish) as a plus. Typos in the cover letter for a role that communicates in writing daily are a no-go.
Stage 2: Phone screen (20 min)
Three questions, no more: (1) Tell me about your last interaction with a dissatisfied customer or guest, (2) What do you know about our product, and what would you want to read up on next?, (3) How do you structure yourself when 30 tickets are open at the same time? Listen for clarity of voice, pace and natural empathy; this role lives on tonality on the phone and in chat. Go/no-go in a 5-minute debrief, no more.
Stage 3: Structured interview (60 min)
Use the set of 15 questions below, alternating behavioral, situational, technical, case and values. Insist on concrete examples; the role is concrete, abstract answers are a warning sign. At least 2 interviewers, one from the support team and one from People or Operations, independent scoring before the debrief.
Stage 4: Practical ticket test (45 min)
Send the candidate 3 fictional customer tickets in advance: a simple product-understanding ticket, an angry customer ticket after a delivery delay, a technical ticket with an unclear error description. Ask for written responses in 30 min plus a 15-min live debrief: why this wording, what would they have escalated further, what would they have asked back? This stage is the most predictive: writing quality, tonality, escalation instinct and the need to clarify show up together here. A calm, clear response to the angry customer without talking over them is the strongest single signal of the entire evaluation.
Stage 5: References (20 min)
Call a former direct manager. Four questions: How did they come across under load (Black Friday, a busy season, a crisis week)? What was the writing quality of their customer correspondence? How well did they pick up new products or processes? Would you hire them again tomorrow? For external career changers with no prior support experience, the 1st question (behavior under load) carries the highest signal value.
Structured interview questions
BehavioralEmpathy and tonality Tell me about a situation where a customer or guest was openly angry. How did you react, and how did the interaction end?
What a strong answer surfacesA concrete narrative with context, reaction and outcome. Empathy in the wording (understanding rather than defense), the ability to listen without talking over and to reformulate the concern. Bonus: the candidate names what they would do differently today. Warning sign: the candidate blames the customer or external circumstances.
BehavioralStructuring under load Describe a situation where you were at your limit, for example on a Black Friday, in a crisis week or under high ticket load. How did you structure yourself?
What a strong answer surfacesA concrete structuring mechanic: prioritization by urgency, bundling similar tickets, clear break discipline, a query to the manager on escalation. Maturity in handling high load without aggressive behavior toward customers or colleagues. Candidates who have never worked under load are at high risk of fast burnout in this role.
BehavioralProduct curiosity and learning ability Tell me about a moment when you actively learned something new about a product or process because a customer asked a question you could not answer.
What a strong answer surfacesA learning posture: concrete steps (asking a colleague, reading the internal docs, coming back later), the ability to admit not knowing openly without damaging the relationship. Bonus: the candidate describes how they then shared the answer for others. Warning sign: no concrete memory of such a situation in the last 6 months.
SituationalEmpathy and tonality A customer writes in chat in capital letters that they have had no response to their ticket for 4 days. In the system you see that the ticket is indeed open and was assigned to no one. What do you write as the first sentence, and what as the second?
What a strong answer surfacesFirst sentence: a clear acknowledgment of the lapse without an excuse (I'm sorry your ticket has gone unanswered since Thursday). Second sentence: a concrete next step with a time window (I'm taking the ticket over personally and will get back to you today by 5 p.m. with a solution or a status). Candidates who start with an explanation about internal processes or shift the state onto colleagues weaken trust.
SituationalEscalation and clarification instinct A customer asks about a feature that you know the product does not offer and does not plan. How do you phrase the answer without damaging the relationship or making a false promise?
What a strong answer surfacesA clear negation without evasion (this feature is not in the product today and is currently not on the roadmap), followed by a genuine attempt to understand the underlying concern and offer an alternative (what would you like to achieve with it? is there another way?). Maturity in separating expectation management from relationship care. Bad: the feature is coming soon (a false promise) or I'll gladly pass it on to the product team (a deferral with no benefit to the customer).
SituationalEscalation and clarification instinct You notice that a technical ticket exceeds your competence. The customer has been waiting 30 min for an answer. What do you do concretely in the next 10 min?
What a strong answer surfacesA fast escalation reflex without pride: a first message to the customer with a time window (I'm checking this with a colleague right now, will get back to you in 30 min with a status), a parallel escalation to the right internal person (Tier 2, engineering, product) with a compact summary of the ticket, never silent holding. Candidates who research alone for another hour before escalating lengthen the SLA and burn out in the medium term.
TechnicalTool familiarity Which ticketing tools have you used? What were the strengths and weaknesses from your daily point of view?
What a strong answer surfacesConcrete familiarity with at least one tool (Zendesk, Intercom, Freshdesk, HubSpot Service, Front, Help Scout). The ability to talk about macros, tags, routing rules and saved replies, not just the login interface. Bonus: the candidate names workflow frictions and how they adapted. If there is no tool experience, expect a clear willingness to learn and plan for 4-6 weeks of onboarding investment.
TechnicalTool familiarity In your experience, what are the most important 2-3 metrics a support team should watch daily or weekly? Why?
What a strong answer surfacesFirst response time (or first reply time), resolution time, CSAT as the standard trio. Bonus: the candidate distinguishes between quantity metrics (volume, backlog) and quality metrics (CSAT, reopen rate) and understands that chasing only CSAT burns writing quality. Candidates who name only volume numbers miss the quality dimension of the role.
TechnicalWriting quality How would you design the response to a recurring ticket (for example a password reset) efficiently, without every answer feeling like copy-paste?
What a strong answer surfacesAn understanding of saved replies / macros with placeholders for name, order number, and personal adjustment in the first and last sentence. An awareness that a pure copy-paste answer distances the customer; the middle can be standardized, the frame must be human. Bonus: the candidate proposes using the ticket as an occasion for an FAQ update or a self-service article.
CaseEscalation and clarification instinct A customer demands a refund outside your policy (for example after 45 days instead of 30). You have no authority to grant it. How do you proceed?
What a strong answer surfacesProcess maturity: (1) understand and reformulate the concern, (2) explain the policy in a friendly and clear way without a defensive posture, (3) offer an alternative (a voucher, an exchange, a partial refund), (4) escalate to the manager with a short proposal in case of legitimate hardship. A separation between what is heard empathetically and what can be promised commercially. Warning sign: stubbornly reading off the policy without an attempt at an alternative.
CaseStructuring under load You take over a shift and see 25 open tickets in the inbox, 6 of them with a red SLA warning and 4 cc'd to management. What do you do in the first 30 min?
What a strong answer surfacesA clear prioritization logic: first the 6 SLA-critical tickets after a quick triage (check the content, answer the fast responses first, provide a short acknowledgment of receipt on the more complex ones), then the 4 cc-management tickets with an internal escalation to the right colleague, then the rest in chronological order. Bonus: the candidate names when they inform the manager (backlog volume, SLA risk). Bad: linear working from top to bottom with no triage.
CaseProduct curiosity and learning ability A customer reports an error you cannot reproduce. How do you structure the diagnosis without frustrating them?
What a strong answer surfacesClarification steps in the right order: browser and device, the steps to reproduce (click by click), a screenshot or a short screen recording, the same step in incognito or another browser. Tonality: every clarification question with context (this helps me solve the problem faster). Bonus: the candidate escalates after 2-3 iterations if the error remains non-reproducible, rather than sending the customer into an endless loop.
ValuesEmpathy and tonality In your view, what distinguishes a good support response from an excellent one?
What a strong answer surfacesA mature answer: excellent answers solve the problem AND make the customer feel understood; good answers only solve the problem. Bonus: the candidate names details such as remembering the customer's name, referring to previous tickets, a friendly closing sentence that keeps the door open. A weak answer: being fast is everything or being friendly is everything, with no connection of the two dimensions.
ValuesProduct curiosity and learning ability How do you take feedback from a colleague or a manager when they criticize your response to a customer?
What a strong answer surfacesOpenness: the ability to separate the feedback from a personal judgment, asking a concrete question (how would you have phrased it?), applying it on the next similar ticket. Bonus: the candidate names a concrete example of a behavioral change. Warning sign: a defensive explanation of their own logic instead of listening; in a role with heavy writing iteration, coachability is the lever for performance in the 2nd half-year.
ValuesEmpathy and tonality How do you react if a colleague on the team treated a customer curtly or impatiently in their response?
What a strong answer surfacesA team posture: a bilateral conversation first (Hey, I saw your response to X, how were you doing just then?), no public reprimand, escalation to the manager only on repetition. Maturity in separating a one-off bad moment from structural behavior. Bad: I report it to the manager immediately or I don't get involved, those aren't my tickets.
How to recognize a great hire
| Trait | Below bar | On bar | Above bar |
|---|---|---|---|
| Empathy and tonality | A reactive service posture with defensive or lecturing phrasing; overlooks the emotional part of the customer request. Defends the company instead of addressing the concern. Comes across hectic or annoyed on the phone. | Recognizes the emotional signal in the customer request and names it briefly before moving to the solution. Tonality consistently friendly, even after 30 tickets; clear and simple language without clichés. | Addresses the emotional concern with a phrasing the customer remembers (I'm genuinely sorry) before solving. Writes humanly, without platitudes; adapts the tone to the channel (chat looser, email more formal). Is cited internally by the team as an example of good responses. |
| Writing quality | Spelling or grammar errors; long unstructured sentences; unclear or ambiguous phrasing; inconsistent address (a Sie-to-Du switch). Uses copy-paste responses with no recognizable adjustment. | Clean spelling and grammar, clear and short sentences, a consistent Sie form, an opening sentence and a closing sentence that feel human. Uses macros with individual adjustment at the start and end. | Stylistically high-quality: short sentences, precise terms, no filler word, unambiguous instructions for the customer, a closing question that keeps the conversation open. Proposes FAQ or self-service improvements from recurring tickets. Is used by the team as a writing reference in onboarding. |
| Tool familiarity | Can operate the ticketing tool superficially (open a ticket, reply, close), but does not understand tags, routing rules and macros. Maintains CRM or ticketing notes patchily. | Masters a classic tool (Zendesk, Intercom, Freshdesk) in daily work, uses macros and tags consistently, keeps structured notes. Understands the difference between quantity and quality metrics. | Actively optimizes the tool stack: proposes macro-library extensions, corrects wrong routing rules, builds simple reports in the tool itself, simplifies tags. Can onboard a junior colleague in the tool from a standing start. |
| Escalation and clarification instinct | Holds tickets longer than necessary without escalating, or escalates with no prior triage and preliminary research. Escalates nothing to the manager and burns out in the medium term through a complexity backlog. | Escalates to the right internal person with a compact summary of the ticket within an appropriate timeframe. Informs the customer in parallel with a time window, holds the SLA through expectation management even when the solution takes longer. | Anticipates the need to escalate from early signals in the ticket (a technical error message, legal phrasing, a demand outside the policy) and prepares the internal handover before the ticket gets old. Is perceived by the team as a reliable triage instance. |
| Product curiosity and learning ability | Learns the product only reactively, when a ticket forces it; falls back on guesses when an answer is missing. Little initiative for internal docs or new features. | Takes time each week for internal docs and release notes, actively asks colleagues from product and engineering, tests new features themselves before customer tickets about them arrive. | Becomes the internal product reference within 6 months; answers 90 % of incoming tickets without escalation to Tier 2 or product; maintains own cheat sheets for complex use cases that the team adopts. |
| Structuring under load | Works linearly with no triage, breaks down under a high backlog (forgets breaks, answers hectically, escalates to the manager too late). Becomes unstable in season or crisis weeks. | Triages consistently by SLA criticality and complexity, holds break discipline even in dense shifts, informs the manager about a critical backlog in good time. | Steers their own shift anticipatively: bundles similar tickets, blocks focus time for complex cases, coordinates the handovers at shift end with colleagues, raises the right alarm to the manager 2-3 days before the load peak. |
30 / 60 / 90 day success plan
By day 30
- Full product onboarding and internal certification validated; independent responses to the 10-15 most common ticket types
- Familiarity with the ticketing tool (Zendesk / Intercom / Freshdesk) confirmed: macros, tags, routing rules, notes discipline
- Shadowing of 30-50 tickets at different complexity levels with a debrief by the manager or mentor
- First independent shifts with a buddy review of the outgoing responses in the first 2 weeks
By day 60
- Independent handling of the standard ticket types with writing quality that goes live without a prior review
- First response time and resolution time within the range of the team median; CSAT on incoming responses at least 4 out of 5
- First escalation reflexes established: knows when to hand over to Tier 2, product or the manager and with what summary
- A contribution to the internal knowledge base: 2-3 FAQ articles or macro proposals from recurring tickets submitted
By day 90
- Fully autonomous on the standard repertoire; takes on more complex tickets in at least one area (technical, billing, complaint)
- CSAT consistently above the team median; reopen rate below the team average
- A first involvement in writing reviews of junior colleagues or in the onboarding of the next hire
- A formal review with the manager: ramp validated, an improvement plan on 1-2 priority areas for the next quarter
Common hiring mistakes for this role
Confusing Customer Support and Customer Success Manager
The Customer Support Representative reacts to incoming tickets from any customers with no assigned portfolio; the Customer Success Manager proactively steers a defined portfolio of strategic accounts and carries net revenue retention. Blending both in one posting produces two classic outcomes: either you pay 50 k€ fixed for a profile that in truth only handles tickets (frustration on the CSM side), or you pay 30 k€ for a profile expected to deliver proactive steering without portfolio authority. Clarify the expected posture (reactive vs. proactive) and the ratio of tickets to accounts explicitly in the posting.
Treating writing quality as secondary
A Customer Support Representative spends 70 to 85 % of their working time on written communication (chat, email, ticket notes). Yet recruiting is often done on empathy and phone voice alone, without testing writing quality in practice. The result: responses with spelling errors, ambiguous phrasing and Sie-Du switches that damage the brand perception and lower CSAT. The practical task with real ticket responses is not optional; it is the core of the evaluation.
Hiring on pure empathy without testing technical receptivity
Many SMBs recruit their support staff on relational warmth without checking whether they understand a ticketing tool, an API logic or a simple error message. The result: after 3 months they answer only the easy tickets, and all technical tickets pile up with the manager or with Tier 2. A question about the last tool experience and a technical ticket in the practical task filter this risk without effort.
Playing response-time SLA and quality off against each other
Optimizing for first response time alone produces fast, superficial answers that drive up the reopen rate and lower CSAT. Optimizing for CSAT alone produces long, unproductive answers that lengthen the wait time for other customers. Define the target ratio before hiring: typical at an SMB is first response time under 1 hour plus CSAT at least 4.3 out of 5 plus a reopen rate under 12 %. Profiles who have never reflected on these trade-offs in a structured way will slip into one of the two extremes in the 1st quarter.
Skipping ticketing-tool familiarity
The learning curve on Zendesk, Intercom or Freshdesk takes 3 to 6 weeks, during which a new colleague reaches only 40 to 60 % of the standard speed. Anyone who ignores tool familiarity in screening lengthens the onboarding by these weeks and ties up the team with training effort. Between two comparable profiles, pick the one with prior experience on the tool used; if you absolutely prefer the career-changer profile, plan for 4-6 weeks of onboarding investment.
Frequently asked questions
What does a Customer Support Representative earn at an SMB in Germany?
The reference range for an entry-level Customer Support Representative (0 to 3 years of experience) at a German SMB is 30-42 k€ fixed salary per year (median around 35 k€). SaaS and tech scale-ups in Berlin, Munich and Hamburg trend upward (38-45 k€); classic e-commerce or telco employers trend downward (28-33 k€). Profiles with a second language (English C1 plus French or Dutch at B2) typically sit 3-5 k€ higher. A variable component is not standard; if present, typically up to 5 % of the fixed, indexed to CSAT or first response time.
What is the difference between Customer Support and a Customer Success Manager?
The Customer Support Representative reacts to incoming tickets with no assigned portfolio and measures performance by response time, resolution time and CSAT. The Customer Success Manager proactively steers a defined portfolio of strategic accounts (10 to 80 customers), nurtures the relationship over time and carries net revenue retention plus expansion. Both professions are complementary, but skills, cadences and compensation differ fundamentally (Support 30-42 k€ fixed, CSM 40-65 k€ fixed plus variable). Promoting a support representative to CSM without reducing the ticket load is the most common mistake.
How long does it take to hire a Customer Support Representative in Germany?
Expect 30-50 days between the publication of the job posting and a signed contract for an entry-level profile. The pool of available candidates is large; the volume bottleneck is usually not acquisition but the filter quality in screening (writing quality, language profile, tool experience). Cutting below 30 days usually comes at the expense of the written practical task, which is the most predictive step for future performance. With multilingual requirements (German C1 plus 2 further languages), plan for the upper limit.
Which tools should a Customer Support Representative master?
A classic ticketing tool: Zendesk, Intercom, Freshdesk, HubSpot Service, Front or Help Scout. Zendesk dominates in Germany in medium and large structures; Intercom is common at SaaS scale-ups; Freshdesk and HubSpot Service at smaller SMBs. Prior experience with the tool used saves 3-6 weeks of onboarding; a career change with a clear learning posture works but requires dedicated buddy support in the first 6 weeks. A first familiarity with Slack, Notion or Confluence and a CRM (HubSpot, Salesforce, Pipedrive) is recommended in the B2B SaaS environment.
What legal requirements apply to customer-support job postings in Germany?
Three central requirements: (1) a gender-neutral job title with (m/w/d) or colon spelling (§ 11 AGG), (2) the obligation of pay transparency in the ad or before the first interview (EU Pay Transparency Directive 2023/970, implementation by 7 June 2026), (3) transparency about the use of AI tools for pre-selection and guaranteed human oversight (EU AI Act, from 2 August 2026). Questions about age, origin, family situation or pregnancy are not permitted in the interview. If the sector is tariff-bound (retail, mail-order, call centers), additionally check the minimum-salary and shift-premium requirements.
How many tickets does a Customer Support Representative handle per day?
The ticket count depends on channel, complexity and product. In classic B2C e-commerce support with short standard queries: 50-80 tickets per day per person. In B2B SaaS support with longer, technical tickets: 25-40 tickets per day per person. In B2B enterprise support with complex multi-iteration cases: 10-25 tickets per day per person. Above 80 tickets per day per person is usually a signal of understaffed teams or too weak a self-service infrastructure; writing quality and CSAT break down significantly above this threshold. Volume alone is not a sensible KPI; the combination of volume plus CSAT plus reopen rate is the right steering level.