Interactions for Automated Attendant

Last Updated : Sep 29, 2023 |

This section provides information about how the Automated Attendant feature interacts with other features on the system. Use this information to ensure that you receive the maximum benefits of Automated Attendant in any feature configuration.

Authorization Codes

The system does not prompt for an authorization code, and the route-to command fails if:

  • Authorization codes are enabled

  • A route-to command in a prompting vector accesses either Automatic Alternate Routing (AAR) or Automatic Route Selection (ARS)

  • The Facility Restriction Level (FRL) of the vector directory number (VDN) cannot use the chosen routing preference

CallVisor Adjunct-Switch Application Interface (ASAI)

The Call Vectoring feature can collect ASAI-provided digits through the collect vector command as dial-ahead digits. The system passes CINFO to CallVisor ASAI.

Hold

If a call is put on hold during the processing of a collect command, the command restarts at the announcement prompt when the call is taken off hold. All dialed-ahead digits are lost. Similarly, if a call to a vector is put on hold, vector processing is suspended when a collect command is encountered. When the call becomes active, the collect command resumes.

Inbound Call Management (ICM)

You can use Automated Attendant to collect information that an adjunct might later use to handle a call.

Transfer

If a call to a VDN is transferred during a collect command, the collect command restarts when the transfer is complete. All dialed-ahead digits are lost. Similarly, if a call to a vector is transferred, vector processing is suspended when a collect command is encountered. When the transfer is complete, the collect command resumes. Attendant-extended calls suspend vector processing in the same way as transferred calls.