Business phone numbers and phone menus for the United States and Canada. FRES(510) 288-6288[email protected]Sign in

Home › Guides › Emergency calling

Guide

Emergency calling, honestly.

Most business phone pages treat 911 as a footnote. It is the one part of a phone purchase where being wrong has consequences that no refund fixes, so this page sets out what the rules actually say, with the rule itself linked, and states plainly what this service does not do.

Last checked 28 October 2026 · 13 cited sources · 11 min read

Emergency calling done right

The plain statement first

Emergency calling

autoattendant.io routes incoming calls to ordinary mobile phones. It does not place outbound calls and does not provide 911, E911 or any emergency calling service.

To reach emergency services, dial 911 — or 999, 112 or your local number — directly from a phone that supports emergency calling on its own network. Because everyone on your team keeps using their own mobile on their own carrier, an emergency call from one of those handsets is carried by that mobile carrier exactly as it would be if you had never heard of us.

If your organisation operates a multi-line telephone system, your obligations under Kari's Law and the FCC's dispatchable-location rules apply to that system and are unaffected by this service. The same holds in Canada for 9-1-1: the Canadian rules are below.

That is the whole operational answer. The rest of this page explains the law it refers to, because if you are buying a business phone product you will meet these rules eventually and the summaries circulating online are frequently wrong about the dates.

The short legal answer is the same in both countries: the 911 rules govern calls a user places, and nobody can place a call through this service. Kari's Law covers calls a user initiates from a station with dialling facilities, the FCC's interconnected-VoIP 911 requirements apply "only to 911 calls placed by users", and the CRTC's 9-1-1 directions are about routing "a 9-1-1 call originating from a local VoIP service". Each section below quotes the rule.

Kari's Law: dial 911, not 9-911

Kari's Law is named for Kari Hunt, who was killed in a motel room in 2013 while her nine-year-old daughter tried repeatedly to call 911 and could not, because the motel's phone system required dialling 9 for an outside line first.

It became federal law on 16 February 20181 and is codified at 47 U.S.C. § 623. It does two things.

Direct dialling. A user must be able to reach 911 "without dialing any additional digit, code, prefix, or post-fix, including any trunk-access code such as the digit '9'".1 The FCC's implementing rule repeats it: a user must be able to "directly initiate a call to 911 from any station equipped with dialing facilities".2

On-site notification. The system must "provide a notification to a central location at the facility where the system is installed or to another person or organization regardless of location"1 — so that somebody on site knows a 911 call has been made and can meet the responders. The FCC adds quality requirements: the notification "must be initiated contemporaneously with the 911 call", "must not delay the call to 911", and "must be sent to a location where someone is likely to see or hear it."2

The date that matters: 16 February 2020. The rules attach to any MLTS "manufactured, imported, offered for first sale or lease, first sold or leased, or installed after February 16, 2020".3 There is no retrofit obligation for a system installed before that date — a point almost universally garbled in summaries.

Note who is bound: not just operators. The rule separately binds "A person engaged in the business of manufacturing, importing, selling, or leasing multi-line telephone systems" and "A person engaged in the business of installing, managing, or operating multi-line telephone systems".2 If you configure a phone system for your own business, that second category can include you.

RAY BAUM'S Act: where, not just whether

Kari's Law makes sure the call connects. RAY BAUM'S Act § 506, enacted 23 March 2018,4 addresses the next problem: responders arriving at a building and not knowing which floor or room to go to.

It directed the FCC to ensure "that the dispatchable location is conveyed with a 9–1–1 call, regardless of the technological platform used",4 and defines dispatchable location as "the street address of the calling party, and additional information such as room number, floor number, or similar information necessary to adequately identify the location".4

The binding deadlines live in the FCC's rules rather than the statute, and there are four of them. Getting these confused is the single most common error in vendor content on this topic:

CategoryDeadlineRule
MLTS, on-premises fixed telephone6 January 202147 CFR 9.16(b)(3)2
MLTS, on-premises non-fixed device6 January 202247 CFR 9.16(b)(3)2
MLTS, off-premises device6 January 202247 CFR 9.16(b)(3)2
Interconnected VoIP, fixed6 January 202147 CFR 9.11(b)6
Interconnected VoIP, non-fixed6 January 202247 CFR 9.11(b)6

Scroll the table sideways to see every column.

Fixed on-premises phones must provide automated dispatchable location.2 For non-fixed and off-premises devices the rule is softer: automated location "when technically feasible", otherwise location "based on end user manual update, or alternative location information".2

Check the current text before relying on this

47 CFR § 9.11 was amended again on 14 January 2026 (91 FR 1403).6 Any summary of the VoIP rules written before 2026, including much of what is published by vendors, may be describing superseded text. The quotations above are from the current edition as at the date on this page; the rule itself is linked.

What counts as an MLTS

This is the definition everything turns on, and it is broader than most people assume. From 47 CFR § 9.3:5

"A system comprised of common control units, telephone sets, control hardware and software and adjunct systems, including network and premises based systems, such as Centrex and VoIP, as well as PBX, Hybrid, and Key Telephone Systems … and includes systems owned or leased by governmental agencies and non-profit entities, as well as for profit businesses."

Two things are worth drawing out. It explicitly covers network-based and VoIP systems, not only a box on your premises. And it covers non-profits and government, not only companies.

The identical definition appears in statute at 47 U.S.C. § 1471 and is incorporated into Kari's Law by reference.7

The same section defines a "person engaged in the business of installing an MLTS" as one "that configures the MLTS or performs other tasks involved in getting the system ready to operate", including "establishing the dialing pattern for emergency calls".5 If you set up a phone system's dial plan, you may be in scope.

Kari's Law itself says what it regulates: a system configured so that "a user may directly initiate a call to 9–1–1 from any station equipped with dialing facilities".1 This service has no stations and no dialling facilities. Nobody can initiate any call through it, so there is no dial plan for 911 to sit in, and nothing for these rules to configure.

If you run a traditional office phone system with handsets on desks, the opposite is true: assume these rules are your problem and get advice.

The "interconnected VoIP" definition, and why it does not reach this service

A separate set of 911 duties attaches to "interconnected VoIP service", defined at 47 CFR § 9.3 as a service that:5

  1. "Enables real-time, two-way voice communications";
  2. "Requires a broadband connection from the user's location";
  3. "Requires internet protocol-compatible customer premises equipment (CPE)"; and
  4. "Permits users generally to receive calls that originate on the public switched telephone network and to terminate calls to the public switched telephone network."

A second paragraph extends the definition, for 911 purposes only, to services meeting (i)–(iii) that "permit users generally to terminate calls to the public switched telephone network"5 — that is, outbound-capable services.

Those duties are substantial where they apply: obtaining a Registered Location before service starts, giving users a way to update it "at will and in a timely manner", advising every subscriber "prominently and in plain language" where E911 may be unavailable or limited, and keeping "a record of affirmative acknowledgement by every subscriber".6

Why this service is outside it

Both paragraphs of the definition turn on one capability: users must be able to "terminate calls to the public switched telephone network". And the duties themselves are about calls users place: § 9.11's E911 requirements "apply only to 911 calls placed by users", and "all 911 calls" means "any voice communication initiated by an interconnected VoIP user dialing 911".6 Nobody can place a call through this service. It receives calls on your business number and rings your team's mobiles; there is no handset, app or dial pad from which a user could call anyone, let alone 911.

That is also checkable: we route inbound calls to mobile phones, we do not carry outbound calls, and an emergency call made from one of those mobiles travels over that handset's own mobile network under its carrier's arrangements.

What to ask any business phone vendor

One timing note worth carrying across: the FCC warns that wireless 911 location and callback services may be affected while a number is being transferred between providers, which we cover on porting your existing number and in the long-form article on how long porting takes.

Whoever you buy from, including us, these are the questions worth asking in writing:

  • Can a user dial 911 directly from anything this service provides, with no prefix? If the service has no outbound dialling at all, say so explicitly.
  • What location, if any, is transmitted with an emergency call, and how do I keep it current?
  • If my people answer calls on mobiles, whose network carries their 911 calls?
  • Does this product make me an MLTS operator? For anything users can dial out from, the answer depends on your setup, and a vendor that answers confidently without knowing it is guessing. A service nobody can call out from has no stations to configure.
  • Where is your written 911 limitations notice? Any serious provider has one.

Canada: 9-1-1 and VoIP

In Canada the emergency number is 9-1-1 and the regulator is the CRTC. The CRTC's 9-1-1 duties for internet-based phone services attach to local VoIP service providers, which it defines by three tests: they "(i) provide their customers with telephone numbers that conform to the North American Numbering Plan, (ii) provide access to and from the public switched telephone network, and (iii) enable customers to make and/or receive calls that originate and terminate within an exchange or a local calling area." It adds that "a company's use of VoIP technology does not make the company a local VoIP service provider automatically."8 That page is a summary. The decision behind it, Telecom Decision CRTC 2005-21, words the definition more broadly: services that give subscribers "access to and/or from" the public network "along with the ability to make and/or receive calls" within a local calling area.9

Where they apply, the duties are three: provide Basic or Enhanced 9-1-1 service; tell customers about 9-1-1 limitations "upon sign-up and installation, in marketing materials, and in the terms of service", with the information "posted on the Web through an easily accessible link" (this second duty applies only to nomadic and fixed/non-native services); and register with the CRTC.8 The notice duty comes from Telecom Decision CRTC 2005-21, which also requires the customer's express consent to the limitations before service starts.9 Fixed services on a number native to the customer's area are exempt from the notice and consent requirements.10

The CRTC's consumer page adds two practical points: "All VoIP service providers are obligated to provide access to 9-1-1 services", and "during a power (unless battery back-up is provided) or an Internet outage, VoIP services, including 9-1-1, will be unavailable." Basic rather than Enhanced 9-1-1 is provided in Newfoundland and Labrador, Yukon and the Northwest Territories, and where 9-1-1 is not available, such as in Nunavut, emergency services are reached on an ordinary telephone number.11

Next-generation 9-1-1. The CRTC has directed all telecommunications providers to update their networks for NG9-1-1 voice by 31 March 2027,12 and directed the incumbent carriers to decommission the parts of the old E9-1-1 network that will not form part of NG9-1-1 by the same date; after it, providers not using NG9-1-1 will not be able to send 9-1-1 calls.13 A date for NG9-1-1 real-time text for the general public is still to be set.12 None of this changes anything for a team member dialling 9-1-1 from their own mobile: that call is their carrier's.

9-1-1 limitations of this service

This service cannot be used to call 9-1-1. It receives calls on your business number and rings your team's mobiles; it places no outgoing calls of any kind. Call 9-1-1 from a mobile or landline that supports it. If you dial 9-1-1 from any internet-based phone, be prepared to give your address and location.

Why the CRTC's 9-1-1 duties do not reach this service. Not because of the definition: since Decision 2005-21 says "to and/or from" and "make and/or receive", a service that only receives calls is not excluded by those words alone. The reason is what the duties are about. Basic 9-1-1 "consists of routing 9-1-1 dialed calls" to the emergency answering centre (para 21); the decision directs carriers to route "9-1-1 calls, along with ANI and ALI data, to the correct PSAP" (para 52) and to ensure that "a 9-1-1 call originating from a local VoIP service" goes to the centre serving "the geographic location from which the call is placed" (para 68).9 Every one of these duties concerns a 9-1-1 call a subscriber places. No subscriber can place any outgoing call through this service, so no 9-1-1 call can originate on it. This is our reading of the decision; the CRTC has not ruled on a receive-only service. Emergency calls from your team are made on their own mobiles, under their own carriers' 9-1-1 obligations.

Elsewhere

The UK (999 and 112, regulated by Ofcom) and every other country have their own frameworks. We have not set them out here because the service is offered in the United States and Canada only.

Further reading

Longer research pieces on this topic, each with its own source list and a downloadable PDF.

Sources

Every regulatory and pricing claim on this page links to the primary source it came from. Figures were checked on the date shown at the top of the page; rules and prices change, so verify before relying on one.

  1. 47 U.S.C. § 623, Kari's Law. Pub. L. 115–127, enacted 16 February 2018. Cornell Legal Information Institute. Retrieved 20 Sep 2026
    https://www.law.cornell.edu/uscode/text/47/623
  2. 47 CFR § 9.16, Multi-line telephone systems. Source credits: 84 FR 66760, Dec. 5, 2019, as amended at 85 FR 78022, Dec. 3, 2020. Current edition, retrieved 20 Sep 2026
    https://www.ecfr.gov/current/title-47/section-9.16
  3. 47 CFR § 9.15, Applicability (Subpart F). Current edition, retrieved 20 Sep 2026
    https://www.ecfr.gov/current/title-47/section-9.15
  4. RAY BAUM'S Act § 506, statutory note to 47 U.S.C. § 615. Pub. L. 115–141, enacted 23 March 2018. Retrieved 20 Sep 2026
    https://www.law.cornell.edu/uscode/text/47/615
  5. 47 CFR § 9.3, Definitions (MLTS, interconnected VoIP, dispatchable location, Registered Location, on-premises). Current edition (27 Oct 2026), retrieved 28 Oct 2026
    https://www.ecfr.gov/current/title-47/section-9.3
  6. 47 CFR § 9.11, 911 service requirements for interconnected VoIP, including (b)(1) scope and (b)(2)(ii)(A) definition of all 911 calls. Source credits include 91 FR 1403, Jan. 14, 2026. Current edition (27 Oct 2026), retrieved 28 Oct 2026
    https://www.ecfr.gov/current/title-47/section-9.11
  7. 47 U.S.C. § 1471, definitions including multi-line telephone system, incorporated by reference into § 623. Retrieved 20 Sep 2026
    https://www.law.cornell.edu/uscode/text/47/1471
  8. CRTC, 9-1-1 Obligations of Local VoIP Service Providers in Canada. Date modified 20 January 2026. Read via an Internet Archive copy (the CRTC site blocks automated access), 26 Oct 2026
    https://crtc.gc.ca/eng/phone/911/voip.htm
  9. Telecom Decision CRTC 2005-21, Emergency service obligations for local VoIP service providers (4 April 2005), paras 2 (definition), 21, 52 and 68 (9-1-1 routing), 93-98 (notice and consent). Read via an Internet Archive copy of 17 May 2026 (the CRTC site blocks automated access), 28 Oct 2026
    https://crtc.gc.ca/eng/archive/2005/dt2005-21.htm
  10. Telecom Decision CRTC 2011-619 (26 September 2011): notification and express consent requirements do not apply to fixed/native VoIP. Read via an Internet Archive copy (the CRTC site blocks automated access), 26 Oct 2026
    https://crtc.gc.ca/eng/archive/2011/2011-619.htm
  11. CRTC, 9-1-1 Services for Traditional Wireline, VoIP and Wireless Phone Services. Date modified 28 October 2024. Read via an Internet Archive copy (the CRTC site blocks automated access), 26 Oct 2026
    https://crtc.gc.ca/eng/phone/911/can.htm
  12. CRTC, Next-generation 9-1-1. Date modified 28 February 2025. Read via an Internet Archive copy (the CRTC site blocks automated access), 26 Oct 2026
    https://crtc.gc.ca/eng/phone/911/gen.htm
  13. Telecom Decision CRTC 2025-67 (E9-1-1 network decommissioning by 31 March 2027). Read via an Internet Archive copy (the CRTC site blocks automated access), 26 Oct 2026
    https://crtc.gc.ca/eng/archive/2025/2025-67.htm