Actions and Conditions
Actions and Conditions work together to control how calls flow through an IVR.
Actions define what the system should do next, while Conditions evaluate caller input or call state to determine which path a call should follow. Together, they combine into logical, step-by-step IVR workflows — a Condition evaluates the call state, and the corresponding Action determines the next step. This logic allows administrators to build dynamic, intelligent call paths that adapt in real time.
Actions
Actions define the behavior that occurs once a Condition is met. They control what happens to the call, such as playing an announcement, routing the call to a queue or destination, or ending the interaction. Actions are executed sequentially and form the building blocks of the IVR call experience.
Terminating ActionA terminating action is an action in the IVR that will result in the caller leaving the current IVR.
Drop Call
A terminating action that immediately disconnects the call.
| Field | Description |
|---|---|
| Action Name | Name of the action displayed in reporting and call flows. |
| Play Announcement | Optional announcement played before the call is dropped. |
Typically used after playing a final message, handling invalid input, or ending an IVR flow intentionally.
Forced Announcement
Plays an audio message that the caller cannot skip.
| Field | Description |
|---|---|
| Action Name | Name of the action displayed in reporting and call flows. |
| Play Announcement | The announcement played to the caller. |
Commonly used for compliance messages, legal disclosures, emergency notices, or mandatory information before proceeding.
Transfer
A terminating action that transfers the call to a specified destination such as another IVR call flow, skill, agent, or dialable number.
| Field | Description |
|---|---|
| Action Name | Name of the action displayed in reporting and call flows. |
| Destination Type | The transfer target: Transfer to IVR, Transfer to Skill, Transfer to Agent, or Transfer to Dialable Number. |
This action is usually the final step before agent interaction.
Collect Digits
Prompts the caller to enter digits using their keypad (DTMF). The digit entry is finalized by the # key.
| Field | Description |
|---|---|
| Query Name | Name of the action displayed in reporting and call flows. |
| Session Parameter ID | Name of the key for the collected value; available as a parameter for other conditions and actions. |
| Play Announcement | Announcement played when the call flow reaches this action. |
| Max Digits Allowed | The maximum number of digits accepted; defaults to Unlimited. |
| Digit Entry Confirmation Language | The language used for the announcements played during digit entry. |
| Timeout Duration | The maximum time given for the caller to input digits. If this time elapses, the digits entered up to that point are used. |
| Display Digits in Historical Logging | When enabled, the digits entered are displayed in reporting details alongside the session parameter ID. |
| Display to Agent | When enabled, the digits entered are visible to the agent for the call alongside the session parameter ID. |
| Censor all but last four digits | When enabled, only the last four digits entered are displayed in reporting details and to the agent. |
Used for collecting a string of digits such as menu selections, account numbers, PINs, or routing decisions based on caller input.
Examples could include:
- Account Number
- Extension
- Date of Birth
- Callback Number
Collect Confirmation
Prompts the caller to enter digits using their keypad (DTMF).
| Field | Description |
|---|---|
| Action Name | Name of the action displayed in reporting and call flows. |
| Session Parameter ID | Name of the key for the collected value; available as a parameter for other conditions and actions. |
| Consent Announcement | The announcement presented to the caller requesting confirmation. |
| Display Digits in Historical Logging | When enabled, the confirmation digit entered is displayed in reporting details alongside the session parameter ID. |
| Display to Agent | When enabled, the confirmation digit entered is visible to the agent for the call alongside the session parameter ID. |
Used for collecting binary responses from the caller such as consent to send SMS messages, gather permissions, and/or acknowledgement to compliances.
Examples could include:
- "Do you agree?"
- "Do you want to continue?"
- "Do you approve this action?"
- "May we text you?"
Confirm Caller Number
Prompts the caller to confirm their phone number using their keypad (DTMF).
| Field | Description |
|---|---|
| Action Name | Name of the action displayed in reporting and call flows. |
| Session Parameter ID | Name of the key for the collected value; available as a parameter for other conditions and actions. |
| Max Digits Allowed | The maximum number of digits accepted; defaults to Unlimited. |
| Timeout Duration | The maximum time given for the caller to input digits. If this time elapses, the digits entered up to that point are used. |
| Display Digits in Historical Logging | When enabled, the confirmation digit entered is displayed in reporting details alongside the session parameter ID. |
| Display to Agent | When enabled, the confirmation digit entered is visible to the agent for the call alongside the session parameter ID. |
Announcement Settings:
| Field | Description |
|---|---|
| Number Verification Intro | The first announcement played to the caller, reading back the digits entered for verification. |
| Number Confirmation Prompt | The second announcement, asking the caller to confirm the digits are correct — 1 to confirm, 2 to reject. |
| Request Number Prompt | Played if the caller rejects the Number Confirmation Prompt, prompting them to re-enter the digits. |
| Confirmation Success Announcement | Played once the caller confirms the digits are correct. |
| Digit Playback Language Pack | The language used for the announcements played during confirmation. |
| Invalid Entry Announcement | Played if the caller enters an invalid entry. |
Used for confirming a call back number, a phone number to text and/or receive calls.
Set Parameter
An action that changes the behavior of the call flow and/or displays data to agents or in reporting.
| Field | Description |
|---|---|
| Action Name | Name of the action displayed in reporting and call flows. |
| Session Parameter ID | Name of the key for the value; available as a parameter for other conditions and actions. |
Select one value source:
| Field | Description |
|---|---|
| Set as Static Value | Assigns a fixed string of text as the value whenever this action is triggered. |
| Set with Standard Parameter | Assigns the value from a dropdown of existing standard parameters. |
| Set with Session Parameter | Assigns the value from an existing Session Parameter ID. |
Used to carry state forward through the rest of the call flow. Examples include:
- Marking that a call recording disclosure has already been announced, so it is not repeated later in the flow
- Flagging that the caller is a specific type of member
- Recording that the caller passed identity verification, so downstream skills or groups do not repeat the check
Data Dip
An action used to request data from a database in a call flow.
| Field | Description |
|---|---|
| Query Name | Name of the action displayed in reporting and call flows. |
| Data Dip Profile | The Data Dip Profile executed as this action. |
Used for changing the call behavior based on data requested from a database about the calling party, displaying data from a database to agents during a live call, and/or displaying data from a database in reporting.
Digit Menu
A terminating action to transfer the caller out of the IVR and into a Digit Menu.
| Field | Description |
|---|---|
| Digit Menu Profile | The Digit Menu Profile the caller is transferred into. |
Used for completing an IVR for the caller to navigate into a "phone-tree."
Send SMS
An action that sends an SMS message to the caller or a verified number and can receive a reply.
Consent Required for SMS MessagesA documented consent must be obtained from the caller for SMS messaging. Consent should include clear information about SMS purposes, the applicable privacy policy, and instructions for HELP and STOP (opt-out). SMS-enabled numbers must be registered with The Campaign Registry and comply with the applicable 10DLC requirements.
| Field | Description |
|---|---|
| Action Name | Name of the action displayed in reporting and call flows. |
| Outbound SMS DID | Dropdown to select the outbound SMS number used to send the message. |
| Consent Parameter | The Session Parameter ID used to check for SMS consent. |
| Target Number Source | Caller ID Number uses the caller's caller ID number as the SMS destination. Verified Number uses a Session Parameter ID obtained from caller input by another action, set via Target Number Session Parameter. |
SMS Settings:
| Field | Description |
|---|---|
| SMS Message | The text sent to the target SMS number. |
| Successfully Sent Announcement | Played when the SMS was consented to and sent successfully. |
| Not Sent Announcement | Played when the SMS was not consented to and therefore not sent. |
| Failed to Send Announcement | Played when the SMS message failed to send. |
Conditions
Conditions act as decision points within an IVR flow. They evaluate specific criteria - such as caller keypress input (DTMF), time of day, or menu selection - and determine which path the call should follow. Conditions enable IVRs to respond differently based on how or when a caller interacts with the system before being determined by an action.
Parameter
A condition used to check for a value that is conditionally met given a filter operator.
| Field | Description |
|---|---|
| Condition Name | Name of the condition displayed in reporting and call flows. |
| Parameter Type | Select one: Standard Parameter, SIP Header, or Session Parameter. |
Each parameter type has unique inputs that use named parameters (by type) to check a value given a conditional filter operator.
Example:
- If the Parameter Condition is a
Standard Parameter, the lookup key is set toDNISand the lookup value is1234, where the filter operator is set toCONTAINS, this parameter is conditionally met and will advance the call in the IVR to the next condition/action.
Standard Parameter
Using basic call information.
| Field | Description |
|---|---|
| Parameter | One of Caller ID, DNIS, External Number, or Tag. |
| Operator | The comparison operator applied to the value. |
| Value | The value being compared against. |
SIP Header
Using common call header information.
| Field | Description |
|---|---|
| Header | One of FROM, FROM (Caller ID Only), CONTACT, TO, P-ASSERTED-IDENTITY, USER-AGENT, or REFERRED-BY. |
| Operator | The comparison operator applied to the value. |
| Value | The value being compared against. |
Session Parameter
Using an expected named session parameter.
| Field | Description |
|---|---|
| Session Parameter | The name of an existing Session Parameter. |
| Operator | The comparison operator applied to the value. |
| Value | The value being compared against. |
Holiday
A condition used to check for holidays in the IVR.
| Field | Description |
|---|---|
| Condition Name | Name of the condition displayed in reporting and call flows. |
| Holiday Profile | The Holiday Profile evaluated by this condition. |
Time of Day
A condition used to check for a schedule in the IVR.
| Field | Description |
|---|---|
| Condition Name | Name of the condition displayed in reporting and call flows. |
| Time of Day Profile | The Time of Day Profile evaluated by this condition. |
| Condition is Met | Outside of Profile Hours (False) or Inside of Profile Hours (True). |
Updated 12 days ago
