Because MessageNet Connections can be used for both everyday and emergency communications, protocols for message prioritization need to be set up. Too often, users, not wanting their messages to be interrupted by others’, set theirs with higher priority levels, potentially blocking any other messages (even emergency messages) from being displayed or spoken. I recommend that an organization should establish priority standards for each type of message ahead of time so users know what priority to give their messages inflatable water slides.
The default priority for normal messages is 200. Other every day priority levels can be set around this base. While emergency messages should have higher priority levels, emergencies are not necessarily equal. This is where it’s vital to set priority standards before emergencies happen, so a message about a fire threatening the entire building isn’t blocked by a message about a water leak in the basement that may only damage equipment. Having different classifications for emergency messages can help make choosing a priority level easier. Also, within Connections’ User Database Manager, it is possible to restrict certain users from sending messages with higher than a certain priority, so only emergency personnel can send messages with emergency-level priority, making it easier to control how the priority levels of messages are set up.
I highly recommend these steps be taken to ensure that emergency communications are reliably delivered and are not lost in the crowd of common daily communications.