Toll fraud and PBX hacking are the ones you have to defend against directly. Fraudsters get into the system, dial out, and the bill lands on you. Defense is partly your configuration and partly provider-side control, which is why securing the whole system matters more than any single setting. For the hardening checklist, see our guide to VoIP security best practices.
Detection is pattern recognition under time pressure. The signals are fairly consistent across the industry. Anomaly detection catches a call that does not fit how an account normally behaves. Watch call patterns and velocity, and sudden spikes or repeat-dialing to one destination jump out. Destination risk scoring asks a blunt question: is this country or prefix a known hotspot? Then real-time alerting lets a rule or a person act before the loss compounds.
The hard part is doing it fast enough to matter. Detection after the fact still leaves you the bill. The providers worth trusting screen at two moments: when an account is created, and on every call after that.
Here is how Avi Asraf, VP of R&D at PBX.IM, describes the signup screen:
"At signup we screen three things at once. The IP: reputation, fraud score, proxy or VPN or Tor flags, the network it is coming from. The email: disposable or leaked addresses. The phone number: VOIP, prepaid, or recent abuse history. All in parallel, a decision in seconds. We query five independent fraud-intelligence sources, not one, so no single feed's bad day becomes a blind spot."
You can see this monitoring in action through real-time call monitoring, where supervisors watch active calls, queues, and analytics from a single dashboard.
That "five sources, not one" point is worth sitting with. A system leaning on a single vendor's score inherits that vendor's mistakes. One that lets several sources vote through rules you own looks more like defense in depth than a checklist.
Detection tells you something is wrong. Prevention is what stops the call. The only prevention that protects your invoice is the kind that happens in real time, on the call itself, not in a report you read the next morning.
On PBX.IM that second layer lives in the dialplan, the logic every outbound call passes through before it connects:
"Every outbound call passes a gate before it bridges. It checks destination country, prefix, account balance, active channel count, call-frequency limits, and per-user and per-country spend caps. A block is a rejection inside the dialplan, under 100 milliseconds, no queue and no waiting. The fastest fraudulent call we will allow is the one we never bridge."
Avi Asraf, VP of R&D, PBX.IM
Those controls belong to the customer, not to a support queue. On every account you can set account-level spend caps, each with a custom action and even a custom audio message when the cap is hit. You can set per-user and per-country caps. You can build a geo-plan that whitelists only the destinations you actually call, keep a blocked-prefix list, and limit concurrent channels per user. Sane defaults ship out of the box. The policy is yours.
Plenty of providers now sell "AI-powered fraud detection." Worth knowing what that actually buys you, because the real question is not whether a provider uses AI. It is whether they can explain a decision when it matters.
PBX.IM made a deliberate choice here: auditable, deterministic rules instead of a black-box model. Some of the upstream intelligence sources it queries run their own machine learning to produce a score, and those scores get consumed. But the decision itself comes from priority-ordered rules the team owns and can audit.
"Every block names the rule that fired, the source, and the exact signal value. So when a Finance customer's compliance team asks why we dropped an outbound call to Lagos, we have the answer before they finish writing the email. That is why we don't bury the decision inside a neural network. You can't subpoena a neural network."
Avi Asraf, VP of R&D, PBX.IM
For a regulated buyer, that auditability is the feature. Evaluating an "AI-driven" provider? Ask three plain questions. Can they tell you why a legitimate call got blocked. Do they rely on more than one intelligence source. Is there a fallback when a feed goes dark. "We use AI" without those answers is a slogan, not a safeguard.
Every fraud system carries a real risk. Block too hard and you strangle the legitimate international minutes that are the whole point of a global phone system. A provider that reliably blocks good calls is a worse problem than one that occasionally lets a borderline signup through.
PBX.IM handles this three ways. Whitelisting is a first-class control, so known-good IPs, networks, email domains, numbers, and countries skip the rules entirely. Signup has three outcomes rather than two: allow, review, or block. A "review" sends a plausible-but-borderline business to identity verification instead of straight rejection. And the system fails open by design.
"If our fraud screen has a bad day, signups go through. A platform that occasionally admits a borderline signup is fixable. A platform that reliably rejects good customers is not."
Avi Asraf, VP of R&D, PBX.IM
Here is the part most fraud-detection content skips, because most providers cannot claim it. The cheapest fraud to stop is the fraud that never gets an account in the first place.
A lot of telecom fraud never comes from a real business at all. Bots and shell signups exist only to drain trial minutes and cheap-destination credit, then vanish. Every time a provider tightens policy to fight that, the cost tends to fall on real customers, in the form of smaller trials and slower onboarding. Verified, real-business onboarding, proper KYC, stops the abuse at the door instead of taxing everyone behind it.
This is where a managed provider and a DID reseller split. A reseller optimizes for one number: signups. Card, instant number, ship it. The fraud cost surfaces later, on the carrier's invoice and on the next customer who inherits a number with a wrecked reputation. PBX.IM optimizes for a different number:
"We screen every signup, we verify identity wherever it is flagged, and we provision numbers with the documentation each country's provider actually requires: incorporation papers, proof of address, letters of authorization. We pay a small conversion cost up front so legitimate customers don't pay a much bigger trust cost later."
Avi Asraf, VP of R&D, PBX.IM
For the genuine business, KYC is a few minutes, once. For the fraudster it is a wall they cannot climb without a real identity. Framed right, verification is not friction. It is the reason your numbers stay clean.
Choosing a business phone system? Here is a checklist you can hold any provider to.
- Real-time call controls. Spend caps, geo and destination rules, and blocking that happens on the call, set by you without raising a ticket.
- Verified onboarding (KYC). Does the provider check that customers are real businesses, or sell numbers to anyone with a card? Ask outright.
- Encryption in transit. TLS for signaling and SRTP for media are the baseline. Confirm they are enforced, not just supported.
- Tenant isolation. In a shared cloud, your data has to be walled off from every other customer by design. On PBX.IM, every query that touches customer data is filtered by that account ID at the data layer, so one compromised account cannot reach another account's data.
- Data residency. For EU, UK, and regulated customers, ask where calls and data physically sit. PBX.IM pins each customer to a region across signaling, media, and stored data, so an EU customer's calls stay in the EU end to end.
- Compliance you can verify. Card handling on PBX.IM is delegated to Stripe (PCI DSS Level 1 certified), so card numbers are never stored on the platform, and EU customers are covered under GDPR. Ask any provider to point to the concrete controls behind a claim, not just the claim.
- Support that owns the incident. When something breaks you want a provider that fixes it, not one that blames your network. Accountable support is part of security, not a side desk.
The threat is shifting under everyone, and it matters most for finance teams. This stopped being a static-blocklist problem. The new shape of it is synthetic voice.
"Deepfake calls that impersonate executives. Voice-cloned scams aimed at finance teams. Static blocklists do not catch robocaller patterns that were generated to beat them. Detection has to start reading behavioral patterns over time, not single signals at single moments. For finance teams the next wave isn't the wire-transfer email. It is the phone call that sounds exactly like your CFO. We are building for the day after that becomes normal."
Avi Asraf, VP of R&D, PBX.IM
The attack surface is also climbing the stack, into the chat agents, AI assistants, and voicebots that are now both the channel and the target. The defense has to travel with it. The threat does not care which channel your team is on. Your protection shouldn't either.
Fraud protection is not a bolt-on. It is part of running a phone system for a whole team. If you are equipping a sales or support floor, talk to us about secure seats for your business. Book a 15-minute walkthrough and watch the monitoring, spend controls, and verified onboarding run on real calls. It pairs naturally with Microsoft Teams calling and transparent per-seat pricing.
Telecom fraud is the theft of phone service or money over a telecom network, through stolen accounts, hijacked routing, or fake identities, so someone else pays for calls they never made. For businesses it usually appears as surprise charges for unauthorized international or premium-rate calls.
By watching for signals that break an account's normal pattern: odd call patterns, sudden velocity spikes, calls to high-risk destinations, and account changes that look like takeover. The strongest systems screen at account creation and on every call, in real time, so a suspicious call gets blocked before it connects.
By frequency, subscription and account-takeover schemes now top the CFCA's reporting, accounting for around half of reported fraud. By cost, International Revenue Share Fraud (IRSF) is the single most expensive category. For business phone systems specifically, toll fraud and PBX hacking are the most direct threats.
Lock down who can reach the phone system, set per-destination and per-country spend caps, whitelist only the countries you actually call, and pick a provider that screens accounts at onboarding and blocks risky calls in real time. That way a hijacked account cannot run up a five-figure bill before anyone notices.
PBX.IM runs auditable, deterministic rules rather than a black-box AI model, while still consuming scores from several fraud-intelligence sources, some of which use their own machine learning. The payoff is explainability: every block traces back to the exact rule and signal that triggered it, which matters the moment a compliance team asks why.