Somebody in your office has a cardiac event. A colleague grabs the nearest phone and dials. What happens next depends on decisions made months earlier by people who were thinking about call quality and licence costs.
This guide covers what E911 is, why cloud telephony complicated emergency calling, and what applies where you actually operate. That last part matters more than the rest, because E911 is a United States framework and the number at its centre is not the one you dial in the Emirates.
The short answer, and a geography warning
E911 stands for Enhanced 911. It is the American arrangement for delivering a caller’s location and callback number to the emergency dispatch centre answering the call, rather than leaving an operator to ask where somebody is.
Two things follow immediately. Businesses calling or operating in the United States face rules that apply directly and carry compliance obligations. Where your people sit in Dubai, Riyadh or Doha, the same problem exists while the framework, the numbers and the duties are all different.
Read the regional section before acting on anything. Half this guide is essential for an American operation and background reading for a Gulf one.
Why cover it at all if the framework is foreign? Because the risk it addresses is universal. Every organisation running calls over the internet employs people who might need help urgently, and the questions those rules force businesses to answer are worth answering anywhere. The obligations differ; the risk does not.
What E911 actually is
The distinction between the basic and the E911 version is worth knowing, because it explains exactly what was added.
Basic emergency calling routes a call to a dispatch centre and nothing more. Somebody answers and asks where you are, which works fine when the caller can speak and knows the address.
E911 adds two pieces of information automatically: where the call originated, and a number to ring back on if it drops. Both matter most in exactly the situations where nobody can supply them.
The receiving facility is a public safety answering point, almost always shortened to PSAP. It answers and dispatches whoever is needed.
What arrives alongside the call has become more precise over time. The American standard is now dispatchable location, which the FCC defines as a location delivered to the PSAP consisting of the confirmed street address of the calling party plus additional information such as suite, apartment or similar detail necessary to adequately identify the caller’s whereabouts.
That phrasing does real work. A street address alone sends responders to the front of a big building; a floor and room number sends them to the person.
Why cloud systems complicated this
Older telephony solved location by assuming it. A line ran to a building, the address was recorded when it was installed, and it never changed because the wire could not move.
Internet-based calling broke that assumption entirely. An agent’s account travels with them, so the same login might be in the office on Monday, at home on Tuesday and in another country the following week.
Mobile networks never had this problem in the same form, since a handset reports its position through the cellular network serving it. A browser session reports nothing of the kind, which is precisely why the question needed solving separately.
The nomadic problem
Nothing about a browser tab or a softphone tells the network where its user is sitting. The address on file may be the head office while the person dialling is three hundred kilometres away.
Solutions exist and all of them involve somebody maintaining information. Registered addresses per user, location detection from network signals, prompts asking staff to confirm where they are, or a combination. None is automatic in the way a copper line was, and each carries an administrative cost that businesses consistently underestimate.
The American rules
Kari’s Law
The law is named for Kari Hunt, killed in a motel room in Marshall, Texas in 2013. The FCC records that her nine-year-old daughter tried four times to reach help from the room’s phone and never got through, because she did not know the motel’s system required dialling “9” for an outside line first. Congress responded in 2018.
Two requirements followed, adopted by the Commission in August 2019. Business phone systems must let users dial emergency services directly, with no prefix or access code. Systems must also send a notification whenever somebody dials, initiated simultaneously where technically feasible, and delivered somewhere a person is likely to see or hear it.
That second requirement is frequently overlooked and genuinely useful. It means reception or security learns immediately that somebody on site needs help, which lets them open doors and direct responders.
Worth pausing on why the prefix rule existed at all. Office systems historically required an access digit because internal extensions and external numbers shared a dialling plan, and nobody thought through what that meant for a child or a visitor in a crisis. The fix costs nothing technically and had to be legislated because it was not happening voluntarily.
Both rules bind the system, not the network. Buyers miss that detail: duties follow the equipment and configuration you operate, not solely to whoever supplies your lines.
RAY BAUM’S Act
Section 506 of that Act produced the dispatchable location requirement described above, applying across technological platforms instead of to one kind of system.
Compliance was phased, with separate deadlines for fixed systems and for devices that move. Anybody operating there should confirm current obligations directly rather than relying on a summary, since the detail varies with equipment age and deployment type.
Enforcement is real rather than theoretical, and penalties reach whoever operates the system as well as manufacturers and installers. That distribution of responsibility is what most businesses learn about late.
Several individual states have layered their own requirements on top. An operation with offices in more than one American state should not assume federal compliance settles the matter everywhere.
How cloud platforms handle location
The approaches in use
Four patterns cover most implementations, and most organisations end up combining them.
- Registered address per user. Each account carries an address somebody entered. Simple, and wrong the moment anybody moves without updating it.
- Network-based detection. The platform infers location from whatever network a device connects through, mapping wireless access points or switch ports to specific floors and rooms.
- User confirmation prompts. People get asked to confirm or update their position when connecting somewhere new.
- Device-level location. Mobile applications can use handset positioning, which is accurate outdoors and considerably less so indoors.
Each has a failure mode. Registered addresses go stale, network mapping needs a maintained record of which access point sits where, prompts get dismissed, and satellite positioning struggles indoors.
Worth being honest about the administrative burden. Location accuracy is a data maintenance problem wearing a technology costume, and the organisations that get it right are the ones who assigned somebody to own it.
Hybrid working made this materially harder. A workforce that moves between home, office and elsewhere means the location on file is wrong for a substantial share of people on any given day, and no amount of platform capability fixes a record nobody updates.
The pragmatic response most organisations land on is layered rather than clever. Maintain addresses for fixed sites properly, prompt anybody connecting from an unfamiliar place, and tell remote workers plainly which device they should reach for when it matters.
What this means outside the United States
Emergency calling on internet-based systems is handled differently in every country, and in many it is handled less completely than on traditional lines.
That is the single most important point in this article. A cloud platform may route ordinary business calls perfectly while offering limited or no emergency capability in a given market, and the gap is rarely advertised.
Three questions matter wherever you are. Can somebody reach the emergency services this way at all? What location, if any, travels with the call? And what happens during a power cut or internet outage, when the whole arrangement depends on connectivity an older line never needed?
Answer those honestly for every country you operate in, and you have done more than most organisations manage. Answer them optimistically and what you have documented is an assumption, not a capability.
Europe has moved furthest on harmonisation, with 112 functioning across member states and location requirements attached to it. Several Asian markets have their own arrangements. None of it transfers automatically to the Gulf, and assuming it does is the error this section exists to prevent.
Multi-country operations face the hardest case. A platform deployed identically across six markets may support emergency calling properly in two, partially in three and not at all in the sixth, and nothing in the interface tells an agent which applies at their desk.
Offshore delivery teams add another layer. Agents in South Asia or the Philippines serving Gulf customers are subject to whatever arrangements exist locally, which the business commissioning the work rarely investigates and remains responsible for understanding.
Emergency calling in the UAE
Different numbers, a different framework, and nothing described in the sections above applies as an obligation here.
The UAE Government portal lists the three to know: 999 for police, 998 for ambulance, and 997 for fire and civil defence. Those work nationally.
How location is handled locally
The approach leans on applications rather than on a network-delivered equivalent of dispatchable location. The same official portal describes Abu Dhabi Police’s AD999 app, which reports fires, requests ambulances and carries an SOS button, and Dubai’s DCAS SOS app for ambulance services, noting that it determines the exact location of the patient.
That is a meaningfully different model. Rather than the telephone network supplying position automatically, a smartphone application does it when somebody uses that route instead of dialling.
For a business, the practical consequence is straightforward and slightly uncomfortable. You cannot assume a call placed through a cloud phone system will deliver a usable location to responders, because the mechanism doing that job in America has no direct local equivalent you can rely on.
Voice service here is also regulated at the service level. TDRA treats voice and video calling over IP as a regulated activity, deliverable by licensed service providers or in collaboration with them, which ties emergency capability to whoever holds the licence behind your service rather than being a platform feature you can switch on.
What to ask your provider
Put these in writing and keep the answers. They are worth more than any marketing page.
- Can users contact emergency services through this platform, in each country where we employ anybody?
- What location information, if any, is delivered with such a call?
- How is that location maintained, and who updates it after a move?
- What happens when the internet or power fails?
- Is there a notification capability so people on site learn somebody has dialled?
- What do you recommend we tell employees about all of this?
A supplier unable to answer the first two plainly is telling you something. Vagueness here is not a sales technique; it usually means the capability is limited and nobody wants to say so.
Get the answers in writing rather than accepting them verbally during a demonstration. Emergency arrangements are exactly the sort of detail that gets described optimistically in a sales conversation and precisely in a contract, and the difference between those two versions is worth establishing before you sign.
Ask the same questions again at renewal. Platforms change, markets get added, and an answer accurate two years ago may no longer describe what you are running.
Practical steps whatever your market
Six things reduce risk regardless of which framework applies to you.
- Keep a landline or mobile for emergencies. The simplest answer to the whole problem, and worth having wherever people work regardless of what your cloud system does.
- Tell people what to dial and from what. Written, posted visibly, and covered during induction. Most people have never thought about it.
- Maintain site addresses. Somebody owns the list of which office is where, and reviews it whenever an office changes.
- Brief remote workers explicitly. Anyone working from home should understand which device to reach for, and that it may not be the work application.
- Test it. Ask your provider how to verify the arrangement without actually dialling emergency services, then do exactly that.
- Check new sites before opening. A location added after the original rollout inherits none of the work done for the others.
- Write it down. A short policy covering all of the above takes an afternoon and demonstrates that the question was considered.
That last point carries weight beyond compliance. Where something goes badly wrong, the question afterwards is what the business had put in place beforehand.
Review it annually alongside everything else. Offices move, people relocate, platforms change, and a policy written three years ago describes an organisation that no longer exists.
One further point worth raising internally rather than with a supplier. One person in the business should own this question, and in most organisations nobody does. It sits between IT, operations, facilities and HR, which means it belongs to everyone and gets attended to by nobody. Naming an owner costs nothing and does more than anything else to prevent an unpleasant surprise later.
None of this needs to become a project. An afternoon spent asking the six questions above, writing down the answers and briefing staff covers most of the exposure that matters.
Frequently asked questions
Does 911 work from a cloud phone system?
American rules place emergency calling obligations on interconnected internet calling services, so generally yes, though capability and location accuracy vary by provider and configuration. Elsewhere the number differs entirely and so does the arrangement behind it. Never assume equivalence between markets. Confirm with your provider, country by country, what is supported and what location travels with a call, and put a non-dependent alternative in place wherever the answer is unclear.
What happens if the internet goes down?
Emergency calling through any internet-based system stops working, which is the most serious limitation of the whole category. An analogue line drew power from the exchange and kept working through local outages; a cloud system depends on both electricity and connectivity at your premises. Keep at least one alternative at every location, whether a mobile handset or a conventional line, and make sure staff know it exists rather than assuming somebody will improvise.
Who is responsible for emergency calling compliance?
Responsibility is shared, which surprises businesses expecting their supplier to carry all of it. Providers supply capability; the organisation operating the system supplies accurate location information, configures direct dialling correctly, and tells staff what to do. The FCC sets that division out explicitly. Elsewhere it is less formalised and no less real, since nobody else knows which desk sits on which floor of your building.
Where to go next
Emergency calling is the part of a telephony decision that nobody asks about during procurement and everybody cares about afterwards. It is worth half an hour before signing rather than an uncomfortable conversation later.
Start by establishing which framework governs you. American requirements are detailed and well documented; Gulf arrangements work differently and the official numbers are 999, 998 and 997. Neither set transfers to the other.
Worth being direct about scope. TabaTalk sells cloud contact center software, holds no network and does not act as a carrier. Emergency call handling depends on the licensed operator carrying your calls, not on any software layer above, which is why these questions belong with whoever provides your connectivity and, where the answer matters, with the relevant authority.
What the platform does handle is everything else about a conversation: routing design, live reporting, and how published lines reach agents wherever they sit, which the remote contact center setup covers in more detail.
If you are planning a deployment across several countries and want the emergency questions settled before anything goes live, speak to sales or book a demo. Bring a list of every location where staff will be working, since everything else turns on it.
Based in Sofia, Bulgaria, a city where history meets innovation, Aleksandar is part of the Product Marketing team at Voiso. After completing his studies in Cologne, Germany, he built a strong background with 5 years in telecommunications and 2 years in and contact center solutions (CCaaS). He thrives on closing the gap between customers and product teams, turning insights into strategies that drive clarity, alignment, and growth. He believes great Product Marketing is about creating understanding, momentum, and belief, both inside and outside the company. Outside of work, Aleksandar channels his energy into sports and the mountains, where each hike offers space to organize his thoughts and the quiet needed to return renewed, much like a trail that leads to a higher and clearer view.
