Add 933 dialing support to allow for testing of our 911 Notifications
Problem: Today, there is no way to test RingCentral 911 notifications for a company's emergency response teams. To validate they are working and that the message content is accurate, we ask that they dial 911. This makes customers feel uncomfortable and puts an unnecessary burden on 911 operators.Added context: Today, we offer customers a way to validate the e911 address and registration status associated with each endpoint. To do so, they dial 933 from a desk phone or RingCentral Phone for desktop (softphone). Our system will playback the direct telephone number of the phone they are dialing from (not the phone set in the Outbound Caller ID), the address they are registered to, and whether they are registered to 911 or not. It is an effective way to support validating the e911 address today.Request: Allow 911 notification to be sent out when dialing 933. This will allow admins, and emergency response teams to adequately test the RingCentral 911 notifications.
Matt
shared this idea
-
Fatima Flores
commented
Dialing 933 from the mobile app is not an expected use case. When a user dials 911 from the mobile app, we give that call to the device's native dialer, to route the call over the device's cellular carrier. The E911 center then is provided location data by the cellular provider. RingCentral is out of the call flow at that point, and nothing 911 is routed over our network.However, we do not anticipate users dialing 933 from our mobile app to test 911 routing, so we do not have any special routing or messaging built into the app for this. Therefore, we route the 933 call over our network incorrectly, and cannot provide location data from the mobile app to the 933 endpoint.