25.1 Live Thread Status

The Conversation thread contains a Live status control that indicates whether the operator view is automatically refreshing current Conversation information.

The control can be toggled between Live and Paused.

25.2 Auto-Refresh Behavior

When Live mode is enabled and the browser tab is visible, AIUNIFY Chat periodically reloads the Conversation state, messages, and applied tags.

The deployed interface refreshes more frequently during active human-takeover activity than during an ordinary historical thread.

  • Live takeover/handoff activity uses approximately a 2-second polling interval.
  • Normal Conversation viewing uses approximately an 8-second polling interval.

25.3 Pausing Auto-Refresh

Select the Live status control to change it to Paused when you temporarily do not want automatic thread refreshes.

Select it again to resume Live auto-refresh.

Remember that a Paused view can become stale while other operators or the visitor continue interacting.

25.4 Browser Visibility

Automatic refresh is intentionally skipped when the browser document is not visible. When you return to the active AIUNIFY Chat tab, the polling cycle can resume.

25.5 Visitor Typing Indicator

When you own the active human Conversation, AIUNIFY Chat can display Visitor is typing….

This indicates that the visitor is currently composing a message and can help the operator avoid interrupting unnecessarily.

25.6 Operator Typing Activity

While you type a visitor Reply, the operator console periodically signals typing activity to the Conversation. The interface throttles these signals rather than submitting one request for every keystroke.

This supports the visitor-side typing experience without changing the actual message history.

25.7 Claim Ownership Can Change

Live refresh is particularly important during handoff work because another authorized action can change the current claim state.

If the Conversation becomes owned by another operator, the interface can switch to a read-only state for you.

25.8 Details and Context

The live thread also provides a Details/context area containing visitor identity, page context, captured Lead information, tags, satisfaction information, and timing signals.

Use this information together with the live message stream rather than responding based only on the newest message.

25.9 Operational Best Practices

  • Keep Live mode enabled during active human handling.
  • Use Paused only when intentionally stopping refresh.
  • Pay attention to Visitor is typing before sending overlapping messages.
  • Recheck claim ownership after returning to a previously inactive browser tab.
Write Your Comment