Back to Articles|Published on October 29, 2026|12 min read

Auto Attendant Article

Phone Toll Fraud: How to Protect a Small Business Line

How toll fraud works (hacked phone systems, voicemail and forwarding abuse, one-ring scams), who pays, and the controls a small business should switch on.

By Auto Attendant Editorial

Phone Toll Fraud: How to Protect a Small Business Line

Summary

  1. 01Toll fraud runs up charges on your account while a fraudster or partner collects revenue from international or premium calls.
  2. 02Small businesses face three routes: hacked phone systems or cloud accounts, voicemail and forwarding used to dial out, and Wangiri callbacks that need no hacking.
  3. 03Canadian network blocking targets verified fraud and known patterns, but it does not protect a phone system whose password has been guessed.
  4. 04Expect the bill to land on your business unless your contract says otherwise. Read your provider's terms, dispute charges quickly and escalate unresolved complaints.
  5. 05Limit calling destinations, secure passwords and PINs, enable two-factor authentication, restrict forwarding permissions and monitor usage. Teach staff to check unfamiliar numbers before calling back.
Inside this article
  1. 01What toll fraud is
  2. 02Three ways it reaches a small business
  3. 03How Canadian carriers block Wangiri and other fraud
  4. 04Who pays when it happens
  5. 05Controls that work
  6. 06Staff script for missed calls and odd voicemails
  7. 07If you think it is happening now
  8. 08Monthly 10-minute checklist
  9. 09FAQ

What toll fraud is

Toll fraud is someone running up call charges on your account so that they, or a partner, get paid. One carrier's policy puts it in a single line: "Toll fraud is the theft of long-distance service" [1].

The money usually comes from international revenue share fraud (IRSF). Some international and premium number ranges earn a share of every minute of traffic that reaches them. A fraudster gets hold of such numbers, then pushes as many long calls as possible to them, from your phone system, your voicemail, your forwarding settings, or your staff calling back a "missed call." The number holder collects the termination revenue; you get the bill. The New Zealand Telecommunications Forum's industry guideline describes the fraudster as receiving "a share of the revenue from termination charges obtained by the number range holder" [2]. Twilio's documentation says the owners of the targeted numbers "receive revenue for every minute" of calls placed to them [3].

The same guideline groups several attacks under "revenue share fraud": PABX (phone system) hacking, IRSF, Wangiri fraud, VoIP hacking and voicemail hacking [2].

How big is it? The Communications Fraud Control Association (CFCA) estimated telecom fraud losses of $38.95 billion in 2023, about 2.5% of telecom revenues, and listed "PBX Fraud" among the top five fraud methods [4]. That number covers all telecom fraud worldwide, mostly losses borne by carriers, so treat it as a sign of scale, not of your personal risk.

This guide is for small businesses in the US and Canada, as of October 2026. It is educational, not legal advice.

$38.95 billionCFCA estimate of worldwide telecom fraud losses in 2023, mostly borne by carriers
2.5%Estimated share of worldwide telecom revenues lost to fraud in 2023, according to CFCA
1,120,372,443Calls blocked by Bell's mechanism from 15 July 2020 to 16 October 2021, recorded in the CRTC decision

Three ways it reaches a small business

1. A hacked phone system or VoIP account

The classic case is an on-premises phone system (PBX) or a hosted VoIP account whose credentials are guessed or stolen. Attackers then place international calls through it, often outside business hours. One US carrier's guidance warns that criminals "often will direct their heaviest assaults on your network when vigilance is at its lowest", meaning nights, weekends and holidays, and lists remote access features such as Direct Inward System Access (DISA) and the remote maintenance port as entry points [5].

For a cloud phone account, the equivalent is a stolen login or API key. Twilio's advice to its own customers is to "Use 2FA to protect against account-takeovers and keep API keys private" [3].

2. Voicemail, auto-attendant and forwarding features used as a dial-out

Features that can send a call outward are the weak points. FirstLight says "Voicemail and Auto Attendants are common vulnerability points" and tells customers to "Ensure outbound access is not enabled on your auto attendant" and to delete inactive voicemail accounts [5]. The NZ guideline's customer checklist includes "Disabling PABX ports and features that are not used (e.g. remote call-forwarding)" and making sure voicemail PINs are secure [2].

Why forwarding matters: when a hosted system forwards a call to another phone, it typically creates a second, outbound call. Twilio's billing note describes "An inbound leg from the caller to your Twilio number" and "An outbound leg from Twilio to the number you are forwarding the call to," each billed per minute [6]. So if someone can change where your line forwards (for example, to an international premium number), every inbound call becomes a paid outbound call. (Editorial note: this is the general billing structure; whether your plan charges for the forwarded leg depends on your provider.)

3. Wangiri (one-ring) callbacks

Wangiri, the one-ring scam, needs no hacking at all. An automated dialer calls huge numbers of phones, lets them ring once, and hangs up, hoping someone calls back [7]. The FCC's guide explains the trap: "If you call back, you risk being connected to a phone number outside the U.S.," and "you may wind up being charged a fee for connecting, along with significant per-minute fees for as long as they can keep you on the phone," shown on the bill as "premium services, international calling, or toll-calling" [8].

The numbers can look domestic. The FCC notes that "232" goes to Sierra Leone and "809" goes to the Dominican Republic, and that scammers may also spoof caller ID [8]. FirstLight makes the same point for business phone systems: "Calls that do not start with 011 can also be international and are often overlooked in security arrangements" [5].

In a business, the risk is the helpful employee who returns every missed call, or the voicemail that says "call us back about your delivery" at an unfamiliar number. The FCC mentions exactly that variation: fake voicemails urging a call back to "schedule a delivery" or about a "sick" relative [8].

How Canadian carriers block Wangiri and other fraud

In Canada, a carrier needs CRTC approval under section 36 of the Telecommunications Act to block calls. Two decisions show how this developed:

  • Telecom Decision CRTC 2020-125 (16 April 2020): Bell Canada and its affiliates asked for urgent approval to block verified Wangiri calls during the early COVID-19 network surge. Bell explained that the calls go mostly to mobile subscribers, appear to come from overseas, and ring "only once or twice" in the hope of a callback; it recorded more than six million Wangiri calls on its networks between 16 and 20 March 2020 alone. The CRTC approved blocking verified Wangiri calls until 1 June 2020 [9].
  • Telecom Decision CRTC 2021-403 (9 December 2021): The CRTC approved Bell's move from a trial to a permanent call-blocking mechanism for verified fraudulent calls. The system uses artificial intelligence to flag traffic anomalies; flagged activity is reviewed, and verified fraud is blocked at the network level. The decision records 1,120,372,443 calls blocked from 15 July 2020 to 16 October 2021, and keeps a redress process for wrongly blocked numbers [10].

Network blocking helps, but it targets known patterns. It does not protect a phone system whose own password has been guessed.

Figure 01
Canadian carrier blocking decisions
  1. 2020Verified Wangiri blocking approved

    On 16 April 2020, the CRTC approved Bell's blocking of verified Wangiri calls until 1 June 2020.

  2. 2021Permanent fraud blocking approved

    On 9 December 2021, the CRTC approved Bell's permanent mechanism. AI flags traffic anomalies; reviewed and verified fraud is blocked at network level.

We don't call back unknown numbers from a single ring. If a voicemail asks us to call an unfamiliar number about a delivery, a prize or a relative, we look up the company's real number instead. If an area code is one we don't recognize, we check it before dialing.

Who pays when it happens

Expect the bill to land on you unless your contract says otherwise. Carrier terms are blunt:

  • Summit Broadband: "the customer is responsible for payment of any charges incurred due to fraud (including toll fraud)," "whether known or unknown to the customer" [1].
  • FirstLight: "the security of your company's PBX and its internal processes are beyond FirstLight's scope," and "There is no limit to the potential loss and liability in the event of international toll fraud" [5]. The same document says the FCC has ruled that the customer is responsible. Read that as the carrier's summary of tariff-era precedent. In Chartways Technologies, Inc. v. AT&T Communications, 8 FCC Rcd 5601 (1993), the FCC upheld a 1991 Common Carrier Bureau ruling that a business owed AT&T, under AT&T's tariff, for unauthorized calls that outsiders made through its PBX's remote access feature: the incoming 800 calls because it had subscribed to a service built to let unknown callers in, and the outgoing long-distance calls because the callers got dial tone from its premises, so the calls originated at its numbers. The FCC also found AT&T had no duty to warn the customer about toll fraud. In 2001 it applied the same tariff provisions to another hacked business and called Chartways "dispositive" [11]. The FCC did open a toll fraud rulemaking in 1993 (CC Docket No. 93-292), but, as that 2001 order notes, it never adopted a rule on a carrier's duty to warn. No FCC rule allocates these losses today; your service contract does.

These are two smaller carriers' policies. Read your own provider's terms for "fraud," "unauthorized use" and "toll fraud" before you need them.

What rights you do have (US):

  • Dispute the charge. Under the FCC's truth-in-billing rule, a carrier's bill must "prominently display" a toll-free number to "inquire or dispute any charges on the bill," and carriers "shall not place or cause to be placed on any telephone bill charges that have not been authorized by the subscriber" [12]. Whether fraudulent calls through your own hacked equipment count as "unauthorized" is exactly what carriers dispute; call anyway, and fast.
  • Escalate. For one-ring charges, the FCC says to "first try to resolve the matter with your telephone company," and if that fails, "file a complaint with the FCC at no cost"; victims of international phone scams can also complain to the FTC [8].

In Canada, start with your provider; if that fails, ask whether the service falls under the Commission for Complaints for Telecom-television Services (CCTS), the independent body that handles complaints about telecom services [13].

Controls that work

Most of these take an afternoon. Work through them with whoever manages your phones.

ControlWhat to doSource
Block international dialing you don't need"If you do not make international calls, ask your phone company to block outgoing international calls on your line."FCC
Allow only the countries you callOn cloud platforms, enable only needed countries and only low-risk ranges; Twilio: "Only turn on calling to countries you need to call."Twilio
Block premium and high-risk rangesClearing a high-risk range blocks calls to it.Twilio
Strong, unique PINs and passwordsChange defaults; no "1234", "1111" or extension numbers; change when staff leave.FirstLight; NZ TCF
Two-factor authentication on portalsProtects against account takeover.Twilio
Turn off what you don't useRemote call forwarding, DISA, remote maintenance access, outbound access from the auto attendant, unused mailboxes.FirstLight; NZ TCF
After-hours restrictionsProhibit toll calling at night, weekends and holidays.FirstLight
Usage alertsSet alerts on calls or minutes per day; Twilio's example of an anomaly is "5 times more usage on a weekday compared to average usage over the last 3 weeks."Twilio
Don't return unknown missed callsCheck whether an area code is international before calling back.FCC

Two more points that are easy to miss:

  • Know who can change forwarding. Anyone who can edit where calls forward can, in effect, dial out on your account. Keep that permission to one or two people. Our guide to business phone call routing permissions covers how to set that up.
  • Protect the account itself. The same weak portal password that enables toll fraud can enable a number hijack. See our research note on port-out fraud and SIM swaps.
Figure 02
Work through the preventive controls
  1. 01Limit calling destinations

    Block international dialing you do not need. Allow only needed countries and low-risk ranges, and block premium and high-risk ranges.

  2. 02Secure account access

    Use strong, unique PINs and passwords, change defaults and credentials when staff leave, and enable two-factor authentication on portals.

  3. 03Restrict dial-out features

    Turn off unused remote forwarding, DISA, remote maintenance access, auto-attendant outbound access and mailboxes. Limit who can change forwarding.

  4. 04Restrict hours and monitor usage

    Prohibit toll calling at night, weekends and holidays. Set alerts on calls or minutes per day.

  5. 05Check unfamiliar callbacks

    Do not return unknown missed calls. Check whether an area code is international before calling back.

Staff script for missed calls and odd voicemails

Put this next to the front-desk phone:

"We don't call back unknown numbers from a single ring. If a voicemail asks us to call an unfamiliar number about a delivery, a prize or a relative, we look up the company's real number instead. If an area code is one we don't recognize, we check it before dialing. Numbers starting 011, and some three-digit codes that look like US area codes (809 is the Dominican Republic), are international."

FirstLight also suggests teaching staff to flag warning signs such as "Excessive hang-ups," "Dead air," and "Frequent calls requesting nonexistent extensions" [5].

If you think it is happening now

  1. Call your carrier's fraud or business support line immediately. Ask them to block international and premium calling on the account. Summit Broadband, for example, asks customers to be ready to explain how the fraud occurred and what equipment changes were made [1].
  2. Change every password and PIN: portal, voicemail, phone system admin, SIP credentials.
  3. Check and reset forwarding on every line and mailbox.
  4. Call your phone system vendor, if you have one.
  5. Write down timings and amounts, and ask for the call detail records.
  6. Report it. FirstLight advises notifying state police, the FBI and your insurer [5]. In Canada, fraud can be reported to local police or the Canadian Anti-Fraud Centre [14].
  7. Dispute the charges in writing using the number on your bill [12].
Figure 03
Respond when toll fraud may be happening
  1. 01Call your carrier immediately

    Contact the fraud or business support line and ask it to block international and premium calling on the account.

  2. 02Secure credentials and forwarding

    Change portal, voicemail, phone system admin and SIP passwords and PINs. Check and reset forwarding on every line and mailbox.

  3. 03Contact your phone system vendor

    Call your phone system vendor, if you have one.

  4. 04Record timings and amounts

    Write down timings and amounts, and ask for the call detail records.

  5. 05Report the fraud

    FirstLight advises notifying state police, the FBI and your insurer. In Canada, report to local police or the Canadian Anti-Fraud Centre.

  6. 06Dispute charges in writing

    Dispute the charges in writing using the number on your bill.

Monthly 10-minute checklist

  • Scan last month's bill or call log for international, premium or after-hours outbound calls
  • Confirm international and premium calling are still blocked (or limited to the countries you need)
  • Check forwarding destinations on every line and mailbox
  • Remove users, mailboxes and extensions for people who have left
  • Confirm 2FA is on for every admin login
  • Check that usage or spend alerts are still going to a monitored inbox
  • Remind front-desk staff about one-ring callbacks (see the spam call guide for blocking options)

FAQ

Is toll fraud covered by insurance? It depends on your policy; some cyber or crime policies mention telecom fraud, others exclude it. No general rule applies, so ask your broker. FirstLight's guidance lists notifying your insurance carrier as one of the first steps [5].

Should I call back a number that rang once? Not if you don't recognize it. The FCC's advice is: "Don't answer or return any calls from numbers you don't recognize" [8].

Who do I report to? In the US, your carrier first, then the FCC (billing) or the FTC (scams), per the FCC guide [8]. In Canada, your carrier, then local police or the CAFC [14].

Does a cloud phone service remove the risk? No. It removes the on-site PBX ports, but the account login, voicemail PINs and forwarding settings are still targets, and forwarded calls can still create outbound charges [6].

Is it only an international problem? Mostly, because the revenue comes from international and premium ranges, but some of those ranges sit behind codes that look like ordinary North American area codes [8].

For what it's worth, Auto Attendant forwards calls only to US and Canadian numbers and places no outbound calls of its own, as a guard against this kind of fraud.

External Sources (14)

Published by

Auto Attendant Editorial

Auto Attendant gives a small business one phone number and a recorded menu that sends each caller to the right person's mobile, for a flat $29 a month per business line, whatever the size of the team.

Pricing and plans · About and editorial standards · Contact

Get started

Editorial note

Researched and written by Auto Attendant Editorial with AI-assisted research tools; sources are cited inline and checked before publication. Report an error: https://autoattendant.io/contact/.