In response to a variety of triggering events, DAKS alerts and informs individuals or user groups by automatically dialing their phones and transmitting selected prerecorded and/or "live" announcements and/or alphanumeric display messages. The Alert Notifications application enables you to: - quickly alert and inform large groups of users via phone, pager, e-mail or text message
- get acknowledgment that they have received the message
- apply alerting strategies that are appropriate to the situation
Defining Alert Notifications
DAKS has great flexibility to define each alert with unique parameters and behavior. - Contact Strategy determines how DAKS attempts to notify your users.
- Alert Notifications can be designated as high priority, which assures that maximum network resources are devoted to that broadcast while preempting lower priority broadcasts.
- All subscribers can be simultaneously dialed (depending on channel availability) or dialed sequentially based on the number of subscribers that need to be reached.
- Priority can impact dialing strategy. Priority Level Dialing attempts to reach all high priority subscribers before using resources to reach lower priority subscribers.
- Conditional or non-conditional e-mail notification delivery, independent or in addition to voice announcement delivery.
- Subscriber Confirmation options allow you to determine the level of security required before determining that the subscriber received the message. The subscriber may be required to confirm with a positive or negative response (such as “yes, I will report back to the hospital”) or a simple confirmation that the message was received. Again, there are options such as single key stroke, entering PIN to hear the message or even requiring the user to call back into designated number, enter PIN and then listen to message.
- Notification Success Criteria define what terms must be met before an alert notification is considered a success. This may include trying to reach all members of the broadcast group or reaching a designated number. If the goal is met or not met, there can be follow up broadcasts that are automatically launched.
Initiating Alert Notifications
DAKS provides flexible triggering mechanisms for initiating alert notifications. An alert can be triggered: - From a telephone
- From a DAKS Operator workstation
- By schedule
- By DAKS Desktop Client or Smartphone service
- By external agency
- Switch closures/electrical contacts
- External systems interfaces
- Via integrated applications, such as personal security alarm timer, DAKS Mail-to-Phone application, dispatch consoles and trading turrets or emergency notification management systems
Enhanced Features for Unify Platforms
When deployed as part of a Unify network, DAKS (also referred to as OScAR) operates as a CorNet-NQ or SIP-Q node allowing it to take advantage of a variety of advanced connection set up and interaction features. Specific features leveraged by the server in CorNet-NQ or SIP-Q deployments include: - Variable ringing signals - normal, urgent, alarm
- Station busy strategies:
- Intrusion or emergency-intrusion with neutral announcement
- Camp-on / call waiting
- Forced release
 Trunks busy strategies:- Intrusion with neutral announcement
- Forced release
- Redirection override strategies:
- Ignore call forwarding
- Ignore pickup groups
- Ignore do-not-disturb
- Override executive/secretary configurations
- Automatic speakerphone activation
- Two-line scrolling text display on system phones
- Route optimization
|
