> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Enhanced Chat Monitoring for Salesforce

> Find where customers wait, give up or never get an answer in Salesforce Enhanced Chat, from the chat button to the hand-off to a rep.

Components
[`RUM Extension`](https://docs.germainux.com/deploy/germain-ux-rum-extension)
[`RUM JS`](https://docs.germainux.com/deploy/germain-ux-rum-js)

Service
`Analytics`

Availability
2026.3 or later

> [card] [How It Works](#how-it-works)
>
> Events from the chat widget

> [card] [Before You Start](#before-you-start)
>
> RUM JS on the chat pages

> [card] [Set It Up](#set-it-up)
>
> Plugin and conversation analysis

> [card] [KPIs](#kpis)
>
> Chat Event and Chat Transaction

## Overview

GermainUX follows every Salesforce Enhanced Chat conversation from the customer's side: how long the chat button took to appear, how fast the bot or the rep answered, and how long customers waited for a hand-off. It flags each message that got no answer, and each customer who left while waiting. Every conversation sits in the customer's session, so you can replay what they saw before and during the chat.

Enhanced Chat is the Salesforce chat for websites and Experience Cloud sites, also called Messaging for In-App and Web. Monitoring covers chats answered by an Agentforce service agent, by human reps, or by both.

### Questions It Answers

* How long does the chat widget take to load on our pages?
* How fast does our bot answer, and how often does it not answer at all?
* How long do customers wait after the bot hands them to a rep?
* Which conversations did customers abandon with an unanswered message?
* Which hand-offs failed, and why?
* What did the customer do on the site before they opened the chat?

## How It Works

The Enhanced Chat plugin for RUM JS listens to the events the Enhanced Chat widget raises in the customer's browser. GermainUX records each event as a **Chat Event** and measures the waits between events as **Chat Transaction** records.

Every record carries **Chat** = `Enhanced Chat`. Records that belong to a conversation also carry the conversation ID and the Salesforce messaging session ID, so you can look the conversation up in Salesforce.

### Chat Events

| Event | When |
| - | - |
| **Chat Button Clicked** | The customer clicks the chat button |
| **Pre-Chat Loaded** | The pre-chat form appears |
| **Conversation Started**, **Conversation Opened** | A conversation starts, or an existing one opens again |
| **Session** + status, such as **Session Ended** | The messaging session changes status. The displayed name says who ended it. |
| **Conversation Routed**, **Transfer Routed** | Salesforce routes the conversation, or transfers it. A failed routing is marked as failed, with the failure reason as its displayed name and the estimated wait time. |
| **Rep Joined**, **Rep Left**, **Bot Joined**, **Bot Left** | A participant joins or leaves, with their display name |
| **Message** | A message is sent. **To Agent** from the customer, **To Visitor** from the bot (labelled `AI`) or a rep (labelled `Human`, with the rep's name). The text is in **Details**. |
| **No Response** | A customer message gets no answer from the bot or rep within 60 seconds, or the rep leaves without answering (**Rep Left**) |
| **Abandoned Turn** | The customer closes the window, leaves the page or ends the conversation with an unanswered message |
| **Window Minimized**, **Window Maximized**, **Window Closed** | The customer changes the chat window |
| **Link Clicked** | The customer clicks a link in a message |
| **Business Hours Started**, **Business Hours Ended** | Business hours of the chat start or end |
| **Identity Token Expired** | The customer's identity token expires. Marked as failed. |
| **Transcript Requested**, **Transcript Failed** | The customer asks for a transcript, or it fails |
| **Conversation Ended** | The conversation closes, with the number of turns and of customer, bot and rep messages in **Details** |

**No Response** and failed routings also count in the **User-Facing Error** KPI.

### Chat Transactions

| Transaction | Measures |
| - | - |
| **Widget Ready** | Time from the start of the page load until the chat widget is ready |
| **Widget Button Load** | Time from the start of the page load until the chat button appears |
| **Pre-Chat** | Time the customer spends on the pre-chat form |
| **Conversation Start Time** | Time from the chat button click until the conversation starts |
| **First Bot Message** | Time from the start of the conversation until the bot's first message |
| **Bot Response Time** | Time from a customer message until the bot's answer, with the bot's name and the answer in **Details** |
| **Rep Response Time** | Time from a customer message until the rep's answer, with the rep's name |
| **First Rep Reply** | Time from the rep joining until their first message |
| **Handoff Wait** | Time from a transfer until a rep joins, with the rep's name |

A turn starts with the first customer message after an answer. Bot entries without text, which Salesforce sends before the answer, don't end the turn.

![Chat Transaction analysis filtered to Enhanced Chat, with a spike in Handoff Wait and Leading Factors by name: Handoff Wait, Rep Response Time, Conversation Start Time and Pre-Chat](https://mintcdn.com/germain-ux/-y4lkVLc1-6hkkiz/images/main/salesforce-enhanced-chat-monitoring/enhanced-chat-transactions.png?fit=max\&auto=format\&n=-y4lkVLc1-6hkkiz\&q=85\&s=2c1233bd421ee13e5e0a020d18649fbb)

Enhanced Chat Wait Times by Transaction - GermainUX

## Before You Start

* Enhanced Chat (Messaging for In-App and Web) is deployed on your website or Experience Cloud site.
* GermainUX RUM JS monitors the pages that show the chat. See [Deploy GermainUX RUM JS](https://docs.germainux.com/deploy/germain-ux-rum-js.md).
* You know which UX Monitoring Profile monitors those pages.

## Set It Up

### Add the Enhanced Chat Plugin

GermainUX captures Enhanced Chat with a plugin for RUM JS. Add the plugin to the init script of the UX Monitoring Profile that monitors your chat pages. The GermainUX team provides the plugin script and can add it for you.

### Turn On Conversation Analysis (Optional)

GermainUX can collect the messages of each conversation into one Chat Conversation record and analyze it with AI. This is off by default. To turn it on:

**1. Confirm AI features are on**

In the left menu, go to **Settings > System > AI > Settings** and check that **AI Features** is enabled.

**2. Enable the chat processor for Enhanced Chat**

In the left menu, go to **Settings > System > AI > Settings**. In the **Chat Analysis** section, open **Processors**, enable the processor named **Enhanced Chat**, and save.

GermainUX closes a conversation when no new message arrives for 30 minutes, then records the Chat Conversation. For what the analysis covers, see [Chat Analysis](https://docs.germainux.com/analytics/conversation-analysis.md).

## Validate

**1. Start a test conversation**

On a monitored page, click the chat button, fill in the pre-chat form if there is one, and send a message.

**2. Check the events**

Open the **Chat Event** KPI filtered on **Chat** = `Enhanced Chat`. You should see **Chat Button Clicked**, **Conversation Started** and **Message** events in the test session.

**3. Check the transactions**

Open the **Chat Transaction** KPI with the same filter. You should see **Widget Ready**, **Conversation Start Time** and a **Bot Response Time** or **Rep Response Time** for the answer.

## Troubleshooting

> [accordion] No Enhanced Chat events at all
>
> Check that:
>
> * RUM JS is running on the page. Other browser data for the session reaches GermainUX.
> * The page is monitored by the UX Monitoring Profile whose init script contains the Enhanced Chat plugin.
> * The page uses Enhanced Chat. The older Salesforce Embedded Chat (Live Agent) widget raises different events.

> [accordion] Many No Response events
>
> GermainUX records **No Response** when neither the bot nor a rep answers a customer message within 60 seconds. Check the bot's flows and the rep queue for that time, then replay a few of the sessions to see what the customer saw.

> [accordion] No Handoff Wait or First Rep Reply
>
> **Handoff Wait** needs a successful transfer followed by a rep joining. **First Rep Reply** needs a rep to join and send a message. Conversations answered only by the bot have neither.

## KPIs

| KPI | What it holds for Enhanced Chat |
| - | - |
| **Chat Event** | Widget, conversation, routing, participant, message and window events |
| **Chat Transaction** | Widget load times, bot and rep response times, first replies and hand-off waits |
| **User-Facing Error** | Unanswered messages and failed routings |

## Related Documentation

> [card] [Chat and CTI Monitoring](https://docs.germainux.com/integrations/browser-monitoring/chat-cti-monitoring.md)
>
> Other supported chat integrations

> [card] [Agentforce Monitoring](https://docs.germainux.com/integrations/salesforce-monitoring/salesforce-agentforce-monitoring.md)
>
> Agentforce for employees in Lightning

> [card] [Chat Analysis](https://docs.germainux.com/analytics/conversation-analysis.md)
>
> AI Conversation Summaries and Frictions

## Get Help

The GermainUX team can add the Enhanced Chat plugin to your UX Monitoring Profile and help you set up SLAs and alerts on response times.

> [card] [Contact GermainUX Support](https://docs.germainux.com/getting-started/support.md)
>
> The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

> [card] Can't Find What You Need?
>
> Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.