Release 51 - March 2021 Follow

1.      Vismo can now propagate escalation list data to third-party ARCs.

Vismo can now propagate escalation list data via an API push to third party ARCs.

2.      Vismo has an API integration into Securitas Cirrus/MAAS/NextVersion

Vismo can now be configured to transmit escalation list data to Securitas.

3.      Primary Geocoder has been changed from Google to OpenCage.

Vismo will now query OpenCage when performing geo-coding, and if this fails will fall back to Google’s Geocode API.

4.      The type of button push is now recorded against panic alerts.

Vismo already records the source of a panic event (man down, assignment timeout, button push) but will now also record the type of the button push (e.g. Bluetooth device, On-screen tile, Volume keys etc.) This is surfaced in the portal.

5.      Added the concept of “consumable resources” customers can purchase and consume.

In order to further formalise the charging of SMS messages and voice calls, Vismo now supports the concept of a consumable resource a customer has purchased. Currently, only two types of resources are supported – SMS message and voice call.

Notes on this feature;

• Vismo can be configured to alert account administrators via e-mail when the number of a resource goes below a certain level, actioning the customer to contact Vismo to purchase more.
• If a campaign is created (e.g. a mass notification) and the user does not have enough of a resource (SMS, Voice call) to fulfill it, Vismo will still send the notification if the customer has at least 1 of the required resources, and will put them into negative credit.
  • g. Customer has 10 SMS, sends to geo-fence of 100 users -> Vismo sends 100 SMS -> Customer ends up with -90 SMS which will need to be settled prior to sending any more.
• When an account admin logs into the portal, they will get a pop-up notification if they are running low on a resource.