Alerts Approval Checklist

Alerts Approval Checklist

1. Provide a CAD version where RapidSOS Alerts API is available.

2. Subscribe to all event notification types. Confirm that CAD can handle all event notification types.

3. Acknowledge the alert upon notification.

4. Send query to RAD-E to retrieve additional data about the alert.

5. Accept or decline the alert.

  • Verify parallel behavior in the RapidSOS portal.
  • Ensure that CAD is aware of cancellations from Central Station and closes CAD incident.

6. When accepting the alert it should create and auto-fill the CAD incident based on data from the alert

  • Check that addresses are parsed correctly into CAD fields.
  • Check that incident types are parsed correctly into CAD.

7. Send and receive chat messages.

  • Your application must de-duplicate alert.chat notifications from the WebSocket Events API when your application is the sender of the message.
  • Incoming chat messages should populate in CAD notes.
  • Verify that outbound chat messages correctly display in RapidSOS Portal.

8. Disposition updates in CAD must also be reflected against the Alerts API. Can CAD correctly update these dispositions?

9. When the WebSocket subscription receives alert.multi_trip_signal and alert.milestone events they should populate in the CAD narrative

10. Test location scenarios

  • In the case where the provided_location is GEODETIC, the CAD system is expected to perform a reverse geocoding operation, converting the latitude and longitude coordinates to the local GIS format used by the CAD. If the CAD's GIS does not have a corresponding match, then the CIVIC address provided by RapidSOS should be utilized
  • If the provided_location is CIVIC, the CAD system should parse the address provided by RapidSOS. In the rare circumstance where the CIVIC address does not align with the CAD's GIS, the CAD can resort to using the GEODETIC address and conduct a reverse geocoding lookup.
  • If the provided_location is BOTH, use CIVIC and geocode independently. This way, both will reflect the locally authoritative address.
  • Additionally, CAD users have the option to utilize the chat functionality to seek clarification from a monitoring agent if there are any discrepancies with the address.
  • Confirm that there is a system in place to handle the Location Validation flow initiated by location.prevalidation.

11. Over time, additional API schemas will be included, and it is important for partners to consider this to prevent any negative impact or disruption to their integrations caused by additive changes. Some examples of non-disruptive changes that may be introduced are:

  • New event types may be added
  • Enum values may be added (emergency_type, status, disposition, etc)
  • New optional fields may be added

12. When Call for Service is created, the call source in CAD should be listed as“RapidSOS”.