How contact centres actually work

Contact Centre Insights

Attrition math, multi-client architecture, workforce forecasting, QA reality, compliance, bilingual operations — written for contact centre leaders.

Multi-Client Operations

The structural problem most contact centre software pretends doesn't exist.

Attrition Economics

Why 30-50% turnover is a business model, not a tragedy — and how to bend the curve.

QA & Coaching

Closing the loop from scorecard to behaviour change.

Workforce Management

Forecasting, scheduling, and adherence in a multi-client world.

Compliance & Privacy

PIPEDA, Quebec Law 25, SOC 2 — what audits actually look for.

The Buying Decision

HRMS vs WFM vs contact centre platform — and when each one wins.

Canadian Contact Centre Market

Bilingual operations, Atlantic Canada, cross-border CA + US.

Stay tunedComing soon

Founder Notes

Opinions, lessons, and arguments — from years spent inside the contact centre world.

Generic HR assumes one company with one policy, one pay rule, and one rulebook for every agent. A multi-client contact centre runs one agent across many clients, each with its own policy, pay rate, and compliance regime.

Featured readingMulti-Client Operations

Seven Reasons Your HR App Breaks in a Multi-Client Contact Centre

Generic HR software is built on one quiet assumption: one company, one workforce, one set of rules. The moment you take on a second client, that assumption starts to crack, and it keeps cracking as you add the tenth. Here are seven of the cracks, and why none of them show up in the demo.

Read the article

Recent posts

The latest, across every topic

Multi-Client Operations 6 min read

Seven Reasons Your HR App Breaks in a Multi-Client Contact Centre

Generic HR software is built on one quiet assumption: one company, one workforce, one set of rules. The moment you take on a second client, that assumption starts to crack, and it keeps cracking as you add the tenth. Here are seven of the cracks, and why none of them show up in the demo.

Workforce Management 8 min read

Your HRIS Remembers Salaries. Can It Remember the Roster You Billed?

Your HR system can almost certainly tell you what an agent earned on a day last spring. That is the easy half. In a multi-client contact centre, the record that protects your pay run and your client invoice is the roster: who was assigned to which client, at what rate, on which day. That one lives between your HRIS and your WFM tool, and a backdated change can rewrite it out from under an invoice you already sent.

The Buying Decision 8 min read

What BPO Software Actually Costs

The per-seat number is the one the vendor leads with. It is also the smallest number you will pay. In a BPO, the real cost of the software is the operating model it hands you: the integrations, the re-keying, the reconciliation, and the margin you cannot see. Here is how to price the whole thing before you sign.

Contact Centre Glossary of Terms

Plain-English definitions of the contact-centre vocabulary, from AHT to multi-tenant.

Open the glossary

Multi-Client Operations

3 posts

The structural problem most contact centre software pretends doesn't exist.

Seven Reasons Your HR App Breaks in a Multi-Client Contact Centre

Generic HR software is built on one quiet assumption: one company, one workforce, one set of rules. The moment you take on a second client, that assumption starts to crack, and it keeps cracking as you add the tenth. Here are seven of the cracks, and why none of them show up in the demo.

The Hidden Cost of Running Clients in Separate Tools

Most BPOs run each client account in its own copy of the WFM software: a separate tenant, a separate login, a separate report pipeline. It looks tidy. It costs you about 12% of your operating margin.

The Multi-Client Architecture Problem

Generic workforce software assumes the company that buys it runs one business. BPOs don't. The structural mismatch between single-employer software and multi-client operations cascades into attrition, billing accuracy, QA consistency, forecasting, compliance, and knowledge loss, and integration doesn't fix it. A name for the problem most BPO software pretends doesn't exist.

Attrition Economics

1 post

Why 30-50% turnover is a business model, not a tragedy — and how to bend the curve.

Why Your Stay Bonus Didn't Work, and the Math That Proves It

The retention bonus paid to every agent above a tenure threshold is the most popular and least effective attrition lever in BPO. A first-principles look at the math, and what actually moves the number.

QA & Coaching

4 posts

Closing the loop from scorecard to behaviour change.

Scoring French Calls with an English Scorecard: Bilingual QA Done Honestly

Grade a high-velocity French call off a rigid English rubric, then hand the coaching back in English, and you quietly punish your most fluent agents for sounding French. Split the corporate scorecard from the agent's coaching, and bilingual QA stops being a fudge. It starts paying you back in retention and CSAT.

The Disputed Evaluation: What Happens to Trust When QA Gets It Wrong

An agent who knows their 74% is wrong, with no clean way to challenge it, learns one thing fast: the scoreboard is rigged, so why try. Treat the dispute as a transparent, time-boxed protocol instead of a bureaucratic annoyance, and fairness becomes one of the cheapest retention levers a BPO has.

Nesting Graduation: "I Think They're Ready" Is a Labour-Relations File Waiting to Happen

Graduate an agent out of nesting on a supervisor's gut call and you've signed off on a termination you can't defend. Treat it as a gate where Training, QA, and HR sign the same evidence, and "speed to floor" stops generating labour-relations files.

QA as a Retention Lever, Not a Gotcha

Your quality program is either a surveillance tool that pushes agents out the door or a development engine that makes them stay. The difference isn't the scorecard; it's whether a score feeds a coaching session or a case file.

Workforce Management

2 posts

Forecasting, scheduling, and adherence in a multi-client world.

Your HRIS Remembers Salaries. Can It Remember the Roster You Billed?

Your HR system can almost certainly tell you what an agent earned on a day last spring. That is the easy half. In a multi-client contact centre, the record that protects your pay run and your client invoice is the roster: who was assigned to which client, at what rate, on which day. That one lives between your HRIS and your WFM tool, and a backdated change can rewrite it out from under an invoice you already sent.

Why Employee Management Technology Underdelivers in Contact Centres and BPOs

The platform is doing its job. It is making your existing operating model visible, gaps and all. In a BPO, where SLAs, billing, and compliance all run through that model, the gaps it surfaces are the ones you did not budget for. Here is where the value actually leaks, and what to fix before you blame the software.

Compliance & Privacy

4 posts

PIPEDA, Quebec Law 25, SOC 2 — what audits actually look for.

Asset Inventory for BPOs: A Security Control, Not a Storage Problem

Most BPOs treat asset inventory as a logistics chore: where's the laptop, who has the headset. Treat it as a security control instead, and the question becomes the one auditors and privacy regulators actually ask: can you prove, in minutes, where every data-bearing device is, and that the ones you retired were wiped? A device you can't account for isn't a hardware write-off. It's a breach-notification event.

SOC 2 for BPOs: What Type II Actually Tests

SOC 2 Type II is now the procurement gate for almost every US enterprise client a BPO wants to win. The audit isn't about whether your controls exist on paper. It's about whether they ran consistently for the past twelve months. A 2026 operator read of the AICPA framework.

PCI DSS for BPOs: Scope, Levels, and What Auditors Actually Look At

Most BPOs that take payment data on behalf of a client are classified as Service Providers under PCI DSS, not Merchants. The thresholds are tighter, the audit is heavier, and the scope-reduction levers are different. A 2026 operator read of v4.0.1.

Quebec Law 25 for BPOs: What Changed, What to Do

Quebec's privacy regime is now the strictest in North America. If you employ Quebec agents or serve Quebec consumers, and most Canadian BPOs do both; there are eight things to get right.

The Buying Decision

1 post

HRMS vs WFM vs contact centre platform — and when each one wins.

What BPO Software Actually Costs

The per-seat number is the one the vendor leads with. It is also the smallest number you will pay. In a BPO, the real cost of the software is the operating model it hands you: the integrations, the re-keying, the reconciliation, and the margin you cannot see. Here is how to price the whole thing before you sign.

Founder Notes

2 posts

Opinions, lessons, and arguments — from years spent inside the contact centre world.

Starting a BPO? Here's what we built for you.

The operational platform built for BPOs, client-aware on day one, SOC 2-ready, with a real client portal you can demo on the first call. Everything you'd otherwise stitch together or build yourself.

The Platform I've Been Dreaming of Building for Thirty Years

In BPO operations, workforce platforms break because client and LOB live in the reporting layer, not in the data model. FrontLine is what changes when scoping is baked into every row. A founder note on thirty years of watching the same pattern fail.

Contact Centre Insights — How contact centres actually work | FrontLine