# RAD - Attendant Overflow

NOTE: As of MIVB 9.1, it is highly recommended that customers use the Group Announcements feature instead of the legacy Attendant Overflow feature.

Attendant Overflow provides a recorded message for calls which have not been answered by the attendant within a programmable time. Without this feature callers could be forced to listen to ringback for several minutes during peak traffic times.

The system queues incoming calls against the attendant and gives the caller ringback. Calls that are not answered within the Call Forward No Answer Timer are connected to a recorded message (first RAD). The first RAD stops:

- if the Answer Plus Message Length Timer is greater than Answer Plus System Reroute Timer, then the recorded message stops when the Answer Plus System Reroute Timer expires.
- if the Answer Plus Message Length Timer is less than Answer Plus System Reroute Timer, then the recorded message stops when the Answer Plus Message Length Timer expires.

After the first RAD stops, the caller is connected to:

- a music source and remains queued against the attendant

- the recorded message (second RAD) of the attendants second alternate destination, if programmed. Once the second RAD is played for it's Answer Plus Message Length Timer, the caller will receive a reorder tone.

NOTES

- The attendant position can be a Mitel display telephone.

- The RAD port in a clustered system must be local to the attendant console. If not, calls drop after a RAD message plays.

- For a console, program either the RAD - Attendant Overflow feature or the Dial Out of Queue feature. Do not program both the features.

Related Topics

- RAD Description

- RAD Groups

- Types of RADs

- RAD Failure Detection

- RAD Maintenance

- RAD Front End Messaging

- RAD Testing