You picked a carrier. You picked a telecom billing platform. Service delivery is mapped. First wave of customer accounts is close to going live.
Then someone asks how agents are getting paid.
Most IT MSPs hit this wall in the same spot. Mid-implementation. No plan. A whiteboard full of red flags. Here's what nobody on the billing demo asked you:
This post walks you through what makes telecom agent commissions different, why the tools you already have can't run them, and the 5 capabilities your platform actually needs before you launch. If you're adding voice to your stack anytime soon, read this before you sign anything.
IT sales comp is simple. Quotas. Year-end bonuses. A spiff when someone lands a big logo. Finance runs the math once a month in a spreadsheet and moves on.
Telecom rewrites that entire model. IT and telecom have already converged in most MSP books, and the minute you add voice, UCaaS, or connectivity, your comp structure can't keep up.
Here are the four shifts that catch IT MSPs off guard.
In the telecom channel, external agents don't take a finder's fee and walk away. They earn a percentage of the customer's monthly billings every single month, often for the life of the account. The rate is typically 15 to 20% of Monthly Recurring Charge, known as MRC.
Quick math on one account:
Now do that across 50 accounts and four different agents. That's $6,000/month of commission liability you have to calculate correctly, every cycle, or you're paying people wrong. Which you will.
Agents commission on base service revenue. Not on taxes. Not on USF. Not on E911. Not on state surcharges. Not on one-time install fees.
That sounds obvious until you look at your invoice structure. If your billing system doesn't cleanly separate service revenue from regulatory fees at the line-item level, your commission math runs on the wrong number. A few bad percentage points every month, stacked across every agent, adds up fast.
Two outcomes, both bad:
Most MSPs adding voice end up running both structures in parallel:
Try to run both through one spreadsheet and errors start month one. The platform has to handle both models natively, not as a workaround.
They're standard in the telecom channel. Here's what shows up in the average agent contract:
None of this is unusual. All of it has to run without someone calculating on a notepad.
| What’s different | IT Sales Comp | Telecom Agent Comp |
|---|---|---|
| Payout type | One-time spiff or quota bonus | Residual, monthly, for life of account |
| Payout basis | Closed deal value | Current month’s MRC |
| Rate | Flat or quota-tied | 15–20% of MRC, often tiered |
| Tax treatment | N/A | Must exclude taxes and surcharges |
| Splits | Rare | Common on referred or co-sold accounts |
| Clawbacks | Rare | Standard inside contract window |
| Update cadence | Per close | Every billing cycle |
First instinct for most MSPs: shove it into Salesforce or HubSpot. The CRM already knows which rep owns which account. Can't we just build a workflow on top of it?
No. Here are the four reasons the CRM breaks the minute you try.
CRMs are built around the sales lifecycle. Leads become opportunities. Opportunities become closed deals. Each record has a contract value, a close date, and a renewal flag.
Telecom agent commissions don't care about any of that. They care about one number: what the customer actually got billed this month. That number lives in your billing system, not your CRM. The CRM can't reach in, pull it, rate it, or calculate a payout against it.
Different system. Different data. Different job.
Here's how this falls apart in the real world:
Repeat that across 50 accounts making small changes every month. Some payouts run hot. Some run cold. Nothing gets caught until an agent calls in.
Manual CRM updates don't fix this. Nobody has time to hand-update every account every time a customer adds a line or drops a service. So nobody does.
Telecom agents commission on MRC. Not on taxes. Not on USF. Not on E911. Not on state surcharges. Not on one-time install fees.
A CRM doesn't know the difference between any of those. It sees "deal value" or "ARR" and stops there. Even if you piped billing data in, the CRM has no logic to strip regulatory fees out of the commissionable base before calculating a payout.
Every commission run overpays. Every cycle. Forever.
Standard telecom agent commissions logic includes:
None of that is native to any CRM. You'd have to build custom fields, custom workflows, and custom formulas for every edge case. Then rebuild the logic every time an agent contract changes.
Two options. Both bad.
Both paths add maintenance load to a stack that's already stretched. Neither fixes the root issue: the CRM isn't built to run this. No amount of configuration changes that.
Generic MSP billing software has the opposite problem from a CRM. It knows exactly what every customer owes. The data is clean. The monthly run is reliable. What it can't do is calculate what each agent is owed.
Here are the four places your current MSP billing software breaks on telecom agent commissions.
Most PSA most IT shops run on was built for the managed IT model:
Residual commissions tied to variable MRC weren't on the roadmap. The system literally doesn't have the logic to pay someone a percentage of a changing bill every month.
Taxes, USF, E911, and state surcharges have to come out of the base before commission math runs. Most IT-native billing tools don't separate those fees cleanly at the line-item level. So the agent payout runs on the full invoice amount instead of pure MRC.
You overpay every cycle. The overpayment compounds.
Two agents on one account. Rate bumps at volume thresholds. Clawbacks for early churn. Rate resets at renewal. None of this lives in standard billing logic. It gets ignored, calculated by hand, or both.
A person on your team becomes the bridge. Every cycle, they:
That's not MSP billing automation. That's a part-time job with a dashboard.
It works at 10 accounts with two agents. It hurts at 50. It's not a business process at 200. MSPs who try to scale telecom agent commissions through a manual workflow end up in the same spot: agent disputes stacking up, month-end eating a full-time seat, and a late decision to buy real software to commission agents in telecom while the manual process keeps running during migration.
The lesson: commission capability belongs on your platform requirements list before you sign, not after.
Telecom agent commission errors aren't just dollar errors. They're relationship errors. And both sides of the cost add up faster than most MSPs realize.
Here are the four real costs MSPs hit when commission math runs wrong.
When your billing tool commissions on the full invoice instead of pure MRC, you're paying agents on tax and surcharge dollars that were never revenue to begin with. A few percentage points on every account, every month, compounded across the whole channel for years.
Every wrong payout is margin you won't get back.
Independent research puts revenue leakage MSPs never catch at 5 to 15% of annual revenue across the whole billing process. Commission math sits squarely inside that range. Where it hides:
Every one of those is money walking out the door. Quietly. For years.
The dollar side is recoverable. The agent relationship is not.
Telecom agents can move their customers. Operational friction breaks the trust that keeps them selling for you. When payouts are wrong, agents notice. When they can't see their own accounts without calling in, they notice. When it takes three emails to resolve a split question, they notice.
Agents talk to each other. When a payout goes bad, the story travels.
The fallout:
15% of MSPs now list phone services and UCaaS as one of their fastest-growing service lines. More MSPs chasing the same agents every quarter. You don't want to be the one they're warning each other about.
Four cost categories is easy to shrug off. Your own book is not.
Plug your voice customers, average MRC, commission rate, and a realistic error rate into the calculator below.
The math runs live. That 3-year number is usually what stops a conversation and starts a budget cycle.
If you're evaluating a telecom billing platform and your roadmap includes agents, these five capabilities have to be native. Not on the roadmap. Not a third-party integration. Working, in the demo, on day one. If the tool you're looking at calls itself software to commission agents in telecom but can't show you all five, keep shopping. True agent commission management lives in the billing engine, not on top of it.
Here are the five must-haves.
Every account maps to one or more agents with a defined rate or split. After each billing run closes, the system pulls current MRC line items, calculates the payout, and generates the statement. No export. No sync. No Excel.
When an account gets reassigned mid-cycle, the assignment updates and the commission history stays intact.
Taxes, USF, E911, state surcharges, one-time install fees. All excluded from the commissionable base automatically.
Configure it at setup. Forget it. Never manually back anything out again.
One system handles:
No second tool. No reconciliation spreadsheet in the middle.
Agents log in and see:
This is the single most underrated capability in a billing platform. Most of your agent disputes come from agents who can't see their own data. Give them a portal and disputes drop on their own.
If two agents share an account, the split runs automatically. If an agent crosses a tier threshold, their rate adjusts without someone rewriting a formula. If a customer churns inside a clawback window, the credit flows back to the next payout cycle.
Edge cases are where errors live. Native logic closes them.
When you run a commission demo against a vendor, these are the warning signs:
If any two of those show up in the first demo, move on. How the top 20% of MSPs run their ops comes down to not accepting "we can build it later" on critical capabilities.
If agent commissions aren't on your platform requirements list today, the gap catches you mid-implementation. Manual spreadsheets, agent disputes, and a full-time reconciliation seat every month are the standard price of treating commissions as a post-launch problem. It's expensive, it's embarrassing, and it costs partner relationships that take years to rebuild.
Rev.io was built for the telecom billing model. Telecom agent commissions management is part of the core engine, not an afterthought. Account-level agent assignment, automatic exclusion of regulatory fees, live commission calc tied to billing runs, an agent portal with real account visibility, and native support for splits, tiers, and clawbacks are all in the product.
For IT MSPs launching voice for the first time, Rev.io pairs a telecom billing platform and a PSA with commission management on day one. The platform ships faster than the legacy billing stacks you're comparing against because the dev team is AI-native, which is why the capability gap keeps widening.
Request a demo to see the full platform end to end.