 |
Modular Messaging Help
|
|
|
MAS - CA - A Word to AUDIX Users
|
Those who are coming from and familiar with an Intuity AUDIX environment should be aware that there are some fundamental differences between the way that AUDIX and the way that Modular Messaging handle call flows.
Automated attendants versus caller applications
In the AUDIX environment, caller interaction is controlled mostly through the use of “automated attendants,” and particularly “nested automated attendants.” Modular Messaging achieves the same kind of functionality with the use of caller applications.
In the Modular Messaging environment, the term “Automated Attendant” is reserved strictly for the system Automated Attendant and has a much narrower use. The Automated Attendant in Modular Messaging is, generally speaking, a top-level menu that acts as a gateway into the system. Though the system Automated Attendant can be used in an even stricter sense to provide only one route into the system, such as a simple call transfer, That is not the way it is designed to be used. In a case like this, a caller application would be much easier and more efficient to use.
Therefore, if you want to use multiple levels of menus and a wider range of caller options in Modular Messaging, you must use caller applications (which, again, are roughly analogous to nested automated attendants).
“Bottom-Up” versus “Top-Down”
System designers in the AUDIX environment are advised to plan their systems carefully, then start at the deepest level of menus (the “bottom”) and work their way up from there.
Modular Messaging makes it much easier and often more practical to design and build from the top levels and work your way down. This aspect of Modular Messaging design also makes it somewhat easier to add on to your caller applications later, should you find the need.
A brief comparison of AUDIX versus Modular Messaging functionality
Although the end result is the same in many cases, AUDIX and Modular Messaging sometimes take different approaches to get there. The following is a brief summary of how AUDIX and Modular Messaging handle various functions or tasks, summarizing both the similarities and the differences:
Note:
This is by no means an exhaustive list of the differences and similarities, but merely a representative sampling.
|
Intuity AUDIX
|
Modular Messaging
|
|
Uses “automated attendants” and “nested automated attendants”.
|
Uses caller applications and application nodes.
|
|
Must create the “main automated attendant” as the starting point.
|
May use the system (built-in) Automated Attendant or bypass it in favor of a caller application as the starting point.
|
|
Automated attendants are always treated as subscriber mailboxes.
Automated attendants require no special treatment after being created, other than a special mailbox property designating them as automated attendants.
|
Caller applications may use ID numbers similar to subscriber mailbox numbers, but are not required to do so, and they are not necessarily treated as subscriber mailboxes.
Also, caller applications must be deployed on the system after being created.
|
|
Automated attendants may have up to 10 options, corresponding with the touchtone keys 0 through 9.
|
Caller applications may have up to 11 menu options, corresponding with all touchtone keys, including the * and # keys (minus the key assigned for cancellation operations).
|
|
You may administer the automated attendant as an extension on the switch or solely in the AUDIX system (as an internal extension only).
|
You may administer caller application ID numbers on the switch or solely in the Modular Messaging system (as an internal extension only).
|
|
Requires * 8 for transfers.
|
Offers built-in transfer capability.
|
|
Allows up to 4 special (“holiday”) schedules to be defined and in use at one time.
|
Allows up to 18 special (“holiday”) schedules to be defined and in use at one time.
|
|
Multi-lingual options may be configured using system-wide and subscriber-specific settings or an automated attendant.
|
Multi-lingual options may be configured using either the system Automated Attendant, subscriber-specific settings, or a caller application.
|
|
Allows call routing based on a time-of-day schedule.
|
Allows call routing based on a time-of-day schedule.
|
|
Prompts are created as “mailbox greetings” (thus offering little quality control over recordings).
|
Prompts created either as recorded (*.WAV) files embedded in caller application or as “mailbox greeting” (announcements).
|
|
Top of page
