The plain statement first
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.
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.
We deliberately make no compliance claim and no exemption claim anywhere on this site. Whether a given service falls inside a regulatory category is fact-specific and is a question for counsel, not for a marketing page.
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:
| Category | Deadline | Rule |
|---|---|---|
| MLTS, on-premises fixed telephone | 6 January 2021 | 47 CFR 9.16(b)(3)2 |
| MLTS, on-premises non-fixed device | 6 January 2022 | 47 CFR 9.16(b)(3)2 |
| MLTS, off-premises device | 6 January 2022 | 47 CFR 9.16(b)(3)2 |
| Interconnected VoIP, fixed | 6 January 2021 | 47 CFR 9.11(b)6 |
| Interconnected VoIP, non-fixed | 6 January 2022 | 47 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
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.
If you run a traditional office phone system with handsets on desks, assume these rules are your problem and get advice. The purpose of this page is not to tell you they are not.
The "interconnected VoIP" definition, and why we do not claim anything about it
A separate set of 911 duties attaches to "interconnected VoIP service", defined at 47 CFR § 9.3 as a service that:5
- "Enables real-time, two-way voice communications";
- "Requires a broadband connection from the user's location";
- "Requires internet protocol-compatible customer premises equipment (CPE)"; and
- "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
We are not going to publish a claim that we fall outside this definition. Regulatory classification depends on the specific facts of a service and on FCC interpretation, not on a reading of the text by the company that wants a particular answer. Any vendor asserting a clean exemption on a marketing page is telling you something they cannot know.
What we will tell you is operational and 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? A vendor that answers this confidently either way without knowing your setup is guessing.
- Where is your written 911 limitations notice? Any serious provider has one.
Outside the United States
Everything above is United States law and none of it transfers. The UK (999 and 112, regulated by Ofcom) and Canada (9-1-1, regulated by the CRTC) have their own frameworks with different obligations, different location requirements and different treatment of VoIP. We have not set them out here because we were not able to verify their current text to the standard the rest of this page is held to, and publishing a confident summary we had not read would defeat the purpose of the page.
If you operate outside the US, treat this page as background on how one regulator approached the problem, and check your own.
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.
- 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 - 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 - 47 CFR § 9.15, Applicability (Subpart F). Current edition, retrieved 20 Sep 2026
https://www.ecfr.gov/current/title-47/section-9.15 - 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 - 47 CFR § 9.3, Definitions (MLTS, interconnected VoIP, dispatchable location, Registered Location, on-premises). Current edition, retrieved 20 Sep 2026
https://www.ecfr.gov/current/title-47/section-9.3 - 47 CFR § 9.11, 911 service requirements for interconnected VoIP. Source credits include 91 FR 1403, Jan. 14, 2026. Current edition, retrieved 20 Sep 2026
https://www.ecfr.gov/current/title-47/section-9.11 - 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