Skip to main content
The existing payment terms for xApps are outlined in the Billing article. Cognigy reserves the right to change the billing of xApps in the future.
Cognigy xApps are infinitely flexible micro-web applications for customer self-service. You can use xApps standalone or as a complement to any channel to enhance AI and human agents’ capabilities and to overcome channel limitations that compromise user experiences. A set of xApp nodes controls the behavior of xApps. You can build the actual xApp pages in two ways, by providing HTML code or by specifying an adaptive card in JSON. Alternatively, for more customization, you can create your own node by implementing and uploading an Extension. Watch this webinar to get a quick overview of what xApps are, how they work, and in which scenarios you can use them. The webinar also includes a tutorial on how to build a simple xApp.

Compatibility

Concepts

Session concept

You can access an xApp session via the URL and initialize it using the xApp: Init Session node. An xApp session displays a sequence of xApp pages that you can configure as needed. You can initialize a maximum of one xApp session per Cognigy session.

Screen concept

The shell page has a set of configurable built-in screens. You can use these default screens to interact with end users, for example, when the xApp content isn’t displayed. These default screens are part of the shell page, which holds the connection to the Cognigy backend.

xApp screen

The xApp screens appear when the xApp page launches, fails to launch, encounters an error, or is halted.
xApp success screen displayed when a page launches successfully
xApp error screen displayed when a page fails to launch

Intermediate screen

Intermediate screens appear while no xApp page is configured. You can replace the default intermediate screen with a custom-built xApp page.
Default intermediate screen shown while no xApp page is configured

Connection screen

Connection screens appear while the real-time connection to the backend is re-established. You can replace the default connection screen with a custom-built xApp page.
Connection screen shown while re-establishing the backend connection

Session ended screen

The session ended screen appears when the xApp session ends, for example, when the channel connection is closed. The screen informs the user that no further input is accepted. You can customize this message using the ‘Session Ended’ Text parameter on the xApp: Init Session node.
Session ended screen shown when the xApp session ends, for example, when the channel connection is closed.

PIN screen

The PIN screen prompts the end user to enter the xApp session PIN. The user needs to provide the correct PIN to access the xApp pages. Requesting a PIN to enter the session is optional.
PIN entry screen prompting the user to access the xApp session

How it works

To learn more about how an xApp works, read the xApp use cases and Build your first xApp articles. You can find ready-made examples of xApps in the Cognigy GitHub repository.

More information

Last modified on November 11, 2026