Arkansas AR
The PDF emphasizes E911 framework definitions more than detailed enterprise MLTS operating rules; verify current local and state 911 board guidance.
What matters before you deploy or audit E911 in Arkansas
- Arkansas sites should start with the federal MLTS baseline: direct 911 dialing, no delayed emergency call, notification where technically feasible, and dispatchable location.
- The most important enterprise question is whether responders can find the caller inside the actual facility, not whether the billing address is correct.
- For larger offices, campuses, healthcare facilities, schools, hotels, warehouses, and shared buildings, review floor, suite, room, wing, entrance, zone, and callback behavior.
How detailed should the dispatchable location be?
No state-specific square-foot threshold was identified in the currently reviewed sources. Treat 7,000 sq ft as a practical audit trigger and apply federal dispatchable-location rules with local PSAP/provider validation.
Exact law callouts
Short excerpts are included for orientation. Follow the links for the complete statutory or regulatory text.
Direct 911 dialing
47 C.F.R. § 9.16(b)(1)“without dialing any additional digit, code, prefix, or post-fix”
Covered MLTS environments should support plain 911 dialing from every station with dialing capability. Old PBX habits such as 9-911 are a compliance red flag.
On-site or responsible-party notification
47 C.F.R. § 9.16(b)(2)“must not delay the call to 911”
Security desk, reception, facilities, or crisis teams can be notified, but notification cannot hold or reroute the emergency call before it reaches public safety.
Dispatchable location for MLTS
47 C.F.R. § 9.16(b)(3)“conveying the dispatchable location of the caller to the PSAP”
The enterprise has to maintain usable location records, not merely a billing address or main switchboard number.
911 context
Arkansas law defines the building blocks of E911 service: ALI, ANI, selective routing, PSAPs, service suppliers, wireless, VoIP, and nontraditional phone service. That matters because enterprise call paths often cross several of those categories.
911 authority and routing model
Operational responsibility is shared among public agencies, service suppliers, and PSAPs. Businesses should not treat compliance as only a PBX setting; the selected carrier or VoIP platform must be able to send the right call, callback, and location data into the local emergency network.
Location delivery approach
Location quality depends on the service type. Fixed enterprise phones generally need validated civic location. Wireless and nomadic VoIP users may depend on provider workflows, handset signals, or registered user locations.
Dispatchable location area / square-footage rule
No state-specific square-foot maximum was identified in the reviewed state-law source. Treat the federal dispatchable-location rule as the floor and use square footage as responder-search risk: review spaces over 7,000 sq ft, multi-floor sites, campuses, hotels, schools, healthcare areas, warehouses, and any large single room or public area. The location sent with a 911 call should be specific enough for responders to find the caller, using room, suite, floor, building, wing, entrance, dock, alarm zone, or similar detail where a street address alone is not enough.
State-specific differences
The special Arkansas issue is definitional coverage: the older summary captures a broad range of service types, including nontraditional and VoIP services, but it does not replace the newer federal MLTS direct-dial, notification, and dispatchable-location requirements.
Regulatory references
Privacy and records considerations
911 location records, callback numbers, test-call results, and site inventories should be treated as sensitive safety data. Limit access, keep change history, and align retention with state public-records rules, customer contracts, and incident-response needs.