This help page is for Desktop Studio. This information is also available for CXone Studio.

Pops a page in the agent application to assist an agent in their interaction. The popped page can display an image, text styled with basic HTML capabilities, or fields for the agent to enter information. You can use multiple Page actions in your script and include a Next button, allowing the agent to manually move along a sequence of pages.

Agent scripting often cuts down on training, improves contact handling, and facilitates more control in the way agents handle contacts. The system can be configured to display screens and popups so that agents can be directed to specific steps while they are handling the contact. The agent is transitioned through a series of pages depending on how the contact responds to certain questions. Page actions call the appropriate pages.

Common uses of Page are displaying sets of instructions, steps of a script for the agent to speak, and so forth. Double-click the action to launch the configuration editor.

Use in conjunction with Onpageopen action and Pageclose action. To preview a page, use the OnPreview action.


  • Any variables created or changed by the Page action will lose their values when any event, such as Onrelease, Onsignal, or other similar event, runs in the script. If data needs to be preserved for use after the call ends, an API call or DB insert should be used via iframe before the Page action ends.
  • Be sure to use a Pageclose action to conclude a sequence of Page actions. Not closing out a Page may result in "stuck" contacts as an agent may be able to click Next within the popped page even after the interaction is finished.

Supported Script Types

The icon for a Generic script type - a rectangle with < and > symbols inside it.

The icon for the Email script type - a large @ symbol in a diamond.

The icon for the Chat script type - a chat bubble with an ellipsis inside (...), in a diamond shape.

The icon for the Phone script type - an old-style phone handset with curved lines indicating sound coming out of it.

The icon for the Voicemail script type - a symbol that looks like a cassette tape - two circles sitting on a horizontal line.

The icon for the Work Item script type-a piece of paper with one corner folded down and a bullet list on it.

The icon for the SMS script type - a smart phone with a chat bubble coming out of it.


Email Chat Phone Voicemail Work Item SMS

Comparison of Similar Actions

The following actions have similar functions, but with some key differences: 

Runapp: Pops a custom form and submits information through the Ondata branch.

Page: Pops a page in the agent application. Allows you to create a sequence of items that may follow different branches.

Input Properties

These properties define data that the action uses when executing.




Enter a short phrase that uniquely identifies this action in the script. The caption appears on the script canvas under the action icon. The default is the action name.


The title of the HTML page that pops in the agent application.


Reserved. Used to store the Page configuration. Not user editable.


Select True or False. When True, inserts the Next button on the HTML page.


Select True or False. When True, inserts the Back button on the HTML page.


Insert a link to an external stylesheet. For example, <link REL="stylesheet" type="text/css" href="style.css">.


Reserved. Used by the Page Property editor. Not user-editable.


Reserved. Used by the Page Property editor. Not user-editable.

Result Branch Conditions

Result branch conditions allow you to create branches in your script to handle different outcomes when an action executes.




Path taken unless the script meets a condition that requires it to take one of the other branches. It is also taken if the action's other branches are not defined.
OnNext Path taken when the user clicks the "Next" button.
Custom Cases Paths created and taken when connecting to secondary actions using Variable Branch Conditions. Click the ellipsis to open the ConnectView Collection Editor to customize these branches.

Configure PAGE Actions

  1. Add a Page action to your desired location in your script.
  2. Double-click the action.
  3. Add your desired components. Components are the elements displayed on the page that pops up, such as a text field or table. This editor displays an estimated preview of what the agent will see. The CXone agent applications support multiple browsers, which may have small differences in how they display these components. Perform adequate testing with a test interaction to ensure that you are content with the functionality and visual display.
  4. Configure the component's properties.
  5. If you added a Text Input Area or Text Input Field, add any validators.
  6. If you want to remove a component, highlight it in the properties list and click . You can also move the component with the up and down arrows.
  7. Click Ok.