spinhireLast time we covered what a support agent does and what languages pay extra for in the article "Support Agent at a Casino". What comes next is the management side of the track — the reason many people go into support from scratch in the first place. We break down the real path: agent → senior → shift lead → team lead → head of support, how many years it takes, what gets asked at each step, what a team lead does besides chats, what their KPIs are, and why salary on this path grows 2-3x.
The path up: timelines and requirements at each step
This is one of the most predictable career tracks in iGaming: clear rungs, understandable promotion metrics and no requirement for a specialist degree. The average path from day one on the front line to head of support is 6–8 years, but each rung has its own entry threshold. Job titles vary between operators — at some it is "supervisor", at others "floor manager", at others straight to "team leader" with no separate shift lead rung — but the set of duties and requirements matches almost word for word.
Shift Lead: a test of management
Formally this is not yet a team lead, but no longer a rank-and-file agent. The company watches whether the person can carry a shift without a senior nearby: whether they can defuse a conflict between agents, keep their head during simultaneous payment escalations and a VIP player complaint, and keep up with the occupancy and queue dashboard. The pay rise is usually 10–15% over senior agent — it is more of an apprenticeship for team leadership than a separate long-term seniority level. Some operators skip this rung altogether, and a senior agent moves straight into a team lead position if the team is small.
Team Lead: KPIs, hiring, and your first budget
To be considered for team lead, you usually need 6–12 months as a shift lead or the practical equivalent — experience of closing a shift with no support from above. At interview they check basic Excel/Google Sheets and reporting dashboard skills (Zendesk Explore, Looker or similar), the ability to run 1:1s and review QA scores with an agent, participation in candidate interviews, and an understanding of how overtime is calculated and why you will have to account for it to the head of support.
Head of Support: strategy and negotiating with C-level
You get here after 2–4 years specifically in the team lead role — not sooner, because it takes experience of managing several shifts or language teams in parallel. On top of that: managing the whole department's budget (headcount, overtime, outsourcing for peak hours), negotiating SLAs with the COO or Head of Casino on behalf of the business and, as a rule, English at the level of working negotiations with senior management — even if the support team's main language is different.
A team lead in iGaming isn't the same as one in an ordinary contact center
Some of what's required of a team lead in casino and betting differs from a typical BPO supervisor, and that's exactly what explains the salary premium:
- The responsible gaming protocol. A team lead handles escalations where an agent noticed signs of problem behavior — deposits that are too frequent, requests to lift a self-exclusion limit, emotional messages. This calls for empathy, but also for knowing where the conversation ends and mandatory logging in the compliance protocol begins.
- Escalations tied to AML/KYC. A withdrawal stuck on document review or over a fraud suspicion is a common complaint trigger, and a team lead needs to know what can be told to the player and what belongs to an internal procedure and can't be disclosed.
- VIP players on the edge of the general queue. Large sums and high-status players sometimes land in the general chat before a VIP manager picks them up — a team lead has to recognize a case like that and hand it off rather than handling a six-figure sum themselves.
- Operating under multiple licences. One operator can run under MGA, Curaçao, and UKGC licences at the same time — each has its own responsible-gaming wording and different document-handling requirements, and the team lead makes sure the team doesn't mix up markets.
- Peak load from sporting events. At betting operators, a shift's load can triple during a major tournament — planning for that ahead of time is also the team lead's job, not HR's.
A team lead's KPIs: SLA, CSAT, and shift staffing
An agent's personal metric is their own CSAT and QA score. A team lead's metrics are aggregated: they're responsible not for one conversation, but for how the whole shift looks as a whole.
| Metric | Typical benchmark | What it shows |
|---|---|---|
| First-response SLA (chat) | 30–60 sec | How fast the team responds to a new conversation |
| Ticket resolution SLA (email/escalation) | 4–24 hours | How fast deferred cases get closed |
| Shift CSAT | 88–95% | The share of players satisfied with the conversation, across the whole team |
| QA checklist score | 85–95% | Tone, accuracy, speed, adherence to the escalation protocol |
| Occupancy / adherence | 75–90% | The share of agents' time in actual conversations versus idle |
| Annual shift turnover | <15–20% | Team retention — one of the most painful KPIs in support |
| Headcount per team lead | 10–25 agents | The staffing norm, depending on language and channel |
A team lead doesn't calculate any of these numbers by hand — CSAT and QA are usually produced by the chat tool itself and the QA department, occupancy and SLA come from the WFM (workforce management) system. The team lead's job is to spot a deviation and deal with it before it reaches the head of support as the question "what happened to shift B?"
It's important not to confuse this with an agent's personal KPI: a team lead doesn't get fired because one player gave a low rating. They're judged on the month's trend — is shift CSAT rising or falling, does the team hit SLA during peak hours, does adherence hold up on the night shift. It's usually these numbers that determine the team lead's own quarterly bonus — 10–15% on top of base pay for consistently hitting the plan.
What a team lead does besides chats
A team lead rarely jumps into the chat queue — except during peak load or to keep a finger on the pulse. Most of their time goes elsewhere:
- Roster planning (WFM). Who's on which shift, language and time-zone coverage, a buffer for sick leave.
- 1:1s and coaching. Reviewing tough conversations and giving feedback on QA scores — regularly, not once a quarter.
- QA calibration. Aligning with QA analysts so the same agent mistake gets scored the same way across every team lead.
- Hiring and onboarding. Taking part in interviews and candidates' test conversations, tracking how fast a newcomer reaches independent work.
- Escalations from agents. Disputed cases, large payouts, difficult players — things an agent shouldn't resolve alone.
- Reporting. Weekly and monthly KPI summaries for the head of support, sometimes direct presentations at operational meetings.
- Liaising with other departments. Payments, compliance, VIP — when an agent's case outgrows a single chat.
- Tool administration. Configuring routing rules in Zendesk/Intercom, access for new agents, macros for standard replies.
- Overtime planning. Figuring out ahead of time where a beefed-up shift will be needed — a new bonus launch, a major sports tournament, a long weekend.
Pay bands by level in 2026
The ranges are realistic, take-home per month, not counting quarterly quality bonuses — those add another 10–15% at team lead level and above.
| Level | Malta/Cyprus, net/month | Europe (office), net/month | Remote, net/month |
|---|---|---|---|
| Shift Lead | €3.2–4K | €2.6–3.4K | €2.3–3.2K |
| Team Lead | €4–5.6K | €3.4–4.6K | €3–4.2K |
| Head of Support | €5.5–8K | €4.5–6.5K | €4–5.8K |
Compared with a junior agent at the start (€1–2K depending on location — see the ranges in the support agent profile), the jump to team lead is already 2.5–3x, and to head of support sometimes more. See the full catalog by level, region, and requirements in the support team lead profile.
Alternative forks: not just management
Managing a shift isn't for everyone — and that's fine. Here are tracks that stay close to support but don't require being a people manager:
- Support QA (Quality Analyst). Auditing conversations, calibrating checklists, reviewing specific cases with agents — without directly running a shift. Pay usually sits between senior agent and team lead, but with less administrative load.
- VIP manager. The same track through the player rather than through the team: a personal portfolio of high-value clients instead of the general queue. The best-paid of the neighboring options — covered in the profile of the VIP manager.
- Trainer / L&D. Building onboarding programs, training new cohorts of agents, work at the intersection of HR and support. A fit for people who like explaining things but don't want to be responsible for a shift's KPIs.
- Retention. If working with the player base and retention metrics appeals more than the here-and-now conversation, the neighboring profile of the retention manager.
From there, head of support often grows into a broader operations role — for example, a casino operations manager, where support becomes just one of several areas reporting up.
How to speed up the move at each step
- Ask for feedback on QA scores right away instead of waiting for the annual review — it's the fastest way to close gaps.
- Take on buddying a newcomer at the first opportunity — informally, that's already a test of management potential.
- Learn to read the shift dashboard (occupancy, backlog, SLA) before it becomes your job, not after.
- For a shift lead or team lead interview, prepare case studies of conflicts within the team, not just with players — a breakdown of common interview questions is in the article "Interviewing in iGaming".
- Keep a personal track record of metrics — if your CSAT and QA score sit consistently above the team average for several months in a row, that's a ready-made argument in a promotion conversation, not an abstract "I want to grow."
- If the company has no formal shift lead grade, ask to temporarily cover a shift for a team lead on leave — it's the most honest way to test whether the role fits you, before an official promotion.
Open team lead and shift lead positions by language and location are in the support jobs section, or search directly for the "Team Lead" query.
FAQ
Do you have to go through shift lead? No. It's a common step but not a universal one — in small teams a senior agent can sometimes go straight to team lead if they show the right metrics and are ready for hiring/reporting.
Can you become a team lead remotely? Yes, but less often than as an office-based agent: some operators require periodic office presence for interviewing candidates and calibrating QA in person.
Do you need negotiation-level English? For team lead, the support desk's working language is usually enough, but for head of support, negotiation-level English with C-level is almost always a requirement.
Does an outsourced BPO pay the same as a direct operator? No, at a direct operator the pay range is usually 15–25% higher at the same step — the team lead answers for the brand directly, not for one of a call center's client contracts. But a BPO makes it easier to build varied experience: in a couple of years you can run several different brands through one shift.
How many team leads does a head of support usually have reporting to them? A support staff of 60–120 agents typically has 4–8 team leads and shift leads — meaning a head of support almost always manages through a layer rather than agents directly.