> This page is for version Scripted.
> For other versions, use one of these documentation indexes:
> - Generative (default): https://developers.ada.cx/generative/llms.txt
> - Scripted: https://developers.ada.cx/scripted/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developers.ada.cx/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.ada.cx/_mcp/server.

# Configure and use Ada Glass for Oracle

## Overview\[#UUID-c6404ff7-06c5-d224-25ba-5bae3798f7d3_id_1500011055042_id_h_01F5XMDN8P365CX9STR18SG4X4]

The Oracle Glass integration helps you create seamless handoffs from
your chatbot to Oracle live agents, all from within Ada. To configure
the Oracle Glass integration, you must have an Oracle instance with the
*RightNow* Chat Cloud Service.

> **Note**
>
> The number of handoff platforms your organization can use varies
> depending on your subscription package. For more information, see Ada's
> [Pricing](https://www.ada.cx/pricing) page, or contact your Ada team.

### Requirements\[#UUID-c6404ff7-06c5-d224-25ba-5bae3798f7d3_id_1500011055042_id_h_01F5XMDYQT3XQNR6FCQEKKQDDC]

* [RightNow Chat Cloud Service](https://www.oracle.com/cx/service/rightnow/)

* Your Oracle URL

* Administrator account credentials

## Configure Oracle Glass in Ada\[#UUID-c6404ff7-06c5-d224-25ba-5bae3798f7d3_id_1500011055042_id_h_01F5XME4SKJD7DCS29GV4YVKSN]

Turn on the Oracle glass integration in **Settings** >
**Integrations**.

Input:

* **OracleUrl**: the fully qualified URL of your Oracle instance

* **Username**: an Administrator username associated with your Oracle
  instance

* **Password**: the corresponding password for the Administrator account

![](/_fern-files/_img/717bbd0418c856d9ff263dc3a990bc6ffa5b9d6f9b1fa32e5924ab8759d0a575.webp)

## Use the Oracle Live Handoff Block\[#UUID-c6404ff7-06c5-d224-25ba-5bae3798f7d3_id_1500011055042_id_h_01FDT19WY8SP4MR1XWC0172SJE]

The Oracle block is made up of a series of fields for the various
parameters you can define when creating the Oracle live support ticket.
As such, your Oracle live support handoff Answer should be built to
gather whatever information you need from the chatter for a successful
handoff.

![](/_fern-files/_img/fef80bfa27a55646963076b386fa8da38ef81563d40c914c613a2b06abed518e.webp)

All Oracle handoffs do require three details at minimum: The chatter's
*first name*, *last name*, and *email address*. Using Oracle’s REST API,
the bot can then find the chatter in your Oracle database and create an
incident for them. If the chatter does not exist, the bot creates a new
profile for them. Once everything is in place, the Oracle block uses
this information to create a live support ticket and establish a
connection with one of your agents.

The Oracle live agent handoff Answer is made up of five primary actions:

* Gather information from the chatter

* Search for chatter's Contact ID

* Create chatter Contact ID (if no contact ID exists)

* Create Incident ID

* Connect to live agent

For the Contact and Incident ID actions, a REST HTTP request must be
made to your Oracle B2C Service server. Consult the Oracle documentation
for more information about configuring [HTTP requests to the Oracle REST server](https://docs.oracle.com/en/cloud/saas/b2c-service/21a/cxsvc/).

Here is the basic Answer structure of the Oracle handoff Answer,
followed by the detailed steps for building it:

* **Capture block**: *firstname* (required)

* **Capture block**: *lastname* (required)

* **Capture block**: *email* (required)

* **Capture block**: *chatter_question* (recommended)

* **HTTP Request block**: *GET request to your Oracle server for report
  on the chatter's email address.*

* **Conditional block**: *Triggers Contact ID creation on Oracle server
  if GET request returns nothing.*

  * **HTTP Request block**: *POST request to Oracle server to create a
    new Contact ID for chatter.*

* **HTTP Request block**: *POST request to Oracle server to create an
  Incident ID.*

* **Oracle block**: *Connects the chatter with a live agent.*

## Build your Oracle live agent handoff Answer\[#UUID-c6404ff7-06c5-d224-25ba-5bae3798f7d3_id_1500011055042_id_h_01FDT2QYEQVD3572G62RNQEH06]

1. On the Ada dashboard, go to **Build** > **Answers**.

2. Select the existing **Handoff to Support** Answer, or create a new
   Answer to use for the Oracle handoff.

3. In the Answer workspace, add **Capture** blocks to capture the
   chatter's **first name**, **last name**, **email**, and **chatter
   question**.

   > **Note**
   >
   > Capturing the chatter's name and email address before attempting to
   > connect the chatter with your Oracle support team is required. The
   > variable name is important, so be sure to title the variables
   > exactly as listed below:
   >
   > * firstname
   >
   > * lastname
   >
   > * email

4. Next, add an **HTTP Request** block in the Answers workspace.

5. Configure the HTTP Request block for a GET request to check for the
   existence of the chatter's **contact ID** on your Oracle B2C Service
   server. Add the following pathway to your server's REST API URL in
   the URL field of the *HTTP Request* block:

   ```
   /services/rest/connect/v1.4/contacts?q=emails.address={email variable from step 3}
   ```

   *Consult the [Contacts REST Endpoints](https://docs.oracle.com/en/cloud/saas/b2c-service/21a/cxsvc/api-contacts.html)
   section of the Oracle documentation.*

6. Add a **Conditional** block to your Answer to trigger the creation
   of a new chatter contact ID if one does not exist in your Oracle
   database.

7. In the Conditional block, click the Choose a Variable drop-down menu
   and select the **contactid** variable, then set the **Comparison**
   drop-down menu to **Is Null**.

8. Add an **HTTP Request** block to action if the condition is true.

9. Configure the HTTP Request block for a GET request to check for the
   existence of the chatter's **contact ID** on your Oracle B2C Service
   server. Add the following pathway to your server's REST API URL in
   the URL field of the *HTTP Request* block:

   ```
   /services/rest/connect/v1.4/contacts
   ```

   *Consult the [Contacts REST Endpoints](https://docs.oracle.com/en/cloud/saas/b2c-service/21a/cxsvc/api-contacts.html)
   section of the Oracle documentation.*

10. Add an **HTTP Request** block to the main body of your Answer, then
    configure it to create an Incident ID. Add the following pathway to
    your server's REST API URL in the URL field of the HTTP Request
    block:

    ```
    /services/rest/connect/v1.4/incidents
    ```

    *Consult the [Incidents REST Endpoints](https://docs.oracle.com/en/cloud/saas/b2c-service/21a/cxsvc/api-incidents.html)
    section of the Oracle documentation.*

11. Now add the **Oracle** block to your Answer, and configure it as
    required for your handoff:

    | Field                                      | Description                                                                                                   |
    | ------------------------------------------ | ------------------------------------------------------------------------------------------------------------- |
    | **Standby Message**                        | Enter a message explaining to the chatter that they are being connected to an agent.                          |
    | **Question/Chat Subject** \[*recommended*] | Add the **chatter_question** variable from step 3.                                                            |
    | **ContactId** \[*required*]                | Add the **contactid** variable to associate the handoff with the chatter.                                     |
    | **IncidentId** \[*required*]               | Add the **incidentid** variable.                                                                              |
    | **ProductId**                              | Enter the **product ID** for the product associated with the handoff.                                         |
    | **OrganizationId**                         | Enter the chatter's **organization ID**                                                                       |
    | **CategoryId**                             | Enter the **category ID** associated with the chatter's question.                                             |
    | **Off-Hours Answer**                       | Select an **off-hours Answer** to surface if your live support is currently offline.                          |
    | **Error Answer**                           | Select an **error Answer** to surface should an error occur while connecting to your Oracle support instance. |

You're done! Your Oracle handoff Answer is configured and ready to use.
Feel free to add custom messaging to create a more conversational
experience.

## Chatter Experience\[#UUID-c6404ff7-06c5-d224-25ba-5bae3798f7d3_id_1500011055042_id_h_01F5XMH6M0GTY8PA5EY66VN35N]

When the chatter encounters the Oracle Live Agent block during a handoff
Answer flow, they'll be added to the appropriate queue.

When the chat is assigned to an available agent, the agent's name and
Oracle avatar image (or default avatar if a personal one has not been
set) will be provided to the chatter to identify who they are chatting
with.

When the agent is typing, a three dot typing indicator appears in the
Ada window. ![](/_fern-files/developers.ada.cx/343f32bfe3d1be1288c69c3e51d46e18fd0af625c1d3147e942f3c8ef9414a06/ada.docs.buildwithfern.com/2025-05-28T19:49:52.708Z/versions/assets/image/uuid-563d5139-4d95-0574-fc90-a9ddfd4f509c.gif)

The chatter will continue the conversation with the live agent in the
same chat window that they were corresponding with the bot in, resulting
in a seamless experience for the chatter.

If the chatter is asked to share any sensitive information, such as a
Social Security or credit card number, the agent can trigger Oracle's
Off the Record functionality. This reveals a secret message dialog box
the chatter can use to securely share any sensitive data with the agent
without that information being recorded by Ada. See [Oracle Off the Record](#UUID-c6404ff7-06c5-d224-25ba-5bae3798f7d3_id_1500011055042_id_h_01FH65APSS90XANHXFWWBRJ5N2)
for more information.

## Oracle Live Agent Experience\[#UUID-c6404ff7-06c5-d224-25ba-5bae3798f7d3_id_1500011055042_id_h_01F5XMHDEE6XPWFQGXVMH8Z712]

To receive live chats, Oracle agents must "request a chat." In the top
right hand corner of the Oracle dashboard, agents will see a toolbar —
click the button highlighted in red in the screenshot to "request a
chat."

![](/_fern-files/_img/eca65031bdf21dbd1d563932e1f097ac38f5037419a801d82615a6bed028d715.webp)![](/_fern-files/_img/07ac9da94a2a6ac1de14db0bcb8c672141fcc7261ee4ad838b3de88789171724.webp)

The chat window becomes present for the agent with the full transcript,
at this point the agent can reply back to the conversation. The contact
record is also created if not already present in Oracle. If the contact
record is present, it is presented to the agent.

![](/_fern-files/_img/b91124e9e481d14a7c224ee626d13b690b8d9608b966550763d1156500cb56b3.webp)

### Oracle Off the Record\[#UUID-c6404ff7-06c5-d224-25ba-5bae3798f7d3_id_1500011055042_id_h_01FH65APSS90XANHXFWWBRJ5N2]

Ada supports Oracle's Off the Record feature. If a chatter needs to
share sensitive information with the Oracle agent, such as a credit card
or Social Security number, the agent can trigger an Off the Record
secret message box in the Ada chat window. Information sent using this
secret message box is available only to the agent and not recorded in
Ada's database.

#### How to use Off the Record

The Oracle agent triggers the Off the Record interaction in Ada. Here's
how the interaction works:

1. On the Oracle Chats dashboard, in the Public Response field, enter
   `/secret`. This adds the secret message icon to the left of the
   chatter's message field in the Ada chat window.

2. The chatter clicks the **secret message icon** to open the secret
   message input box.

3. In the secret message box, the chatter enters the sensitive
   information they wish to share.

4. The chatter clicks **Send** to share the information with the agent.

5. The secret message box disappears from the chatter's view, and a
   confirmation message appears, indicating the secret message was
   sent.

6. The agent receives the sensitive information in their chat window.
   The secret message is prefixed with the label SECRET.

7. Once the chat ends, the sensitive information is redacted from the
   Oracle transcript.

For more information about Off the Record, check out the following
Oracle knowledge base articles:

* [Chatting with a Customer](https://docs.oracle.com/cloud/november2016/servicecs_gs/FAABU/_BUIGuide-10.htm)

* [Off the Record button in Chat](https://docs.oracle.com/cloud/november2016/servicecs_gs/FAABU/_BUIGuide-10.htm)

---

Have any questions? Contact your Ada team, or email us at [](<mailto:help@ada.support%20%E2%80%9CHelp Docs inquiry%E2%80%9D>).