ICE (Integrated Customer Engagement) — Product Overview

Source: https://help.enterice.com/ice/documentation/ (publicly accessible, noindex/nofollow knowledge base) Vendor: Etech Global Services Compiled: June 2026, by crawling the live documentation site

Note on methodology: This site has ~500 individual pages (250 in the User Manual, ~250 across the three API doc sections). Each page repeats a large navigation block, making a literal page-by-page fetch of all 500 pages infeasible in one sitting. Instead, every page title, URL, and hierarchy position below was captured directly from the site's navigation (100% coverage — nothing here is guessed). For body content, I fetched a representative sample across every module/pattern type and verified content is marked as such; the rest is organized from titles using the site's own (highly consistent) naming conventions. If you need the exact body content of any specific page, tell me which one and I'll pull it in full.


1. What ICE Is

ICE is a multi-channel customer engagement platform (live chat, email/ticketing, social/messaging channels, and a chatbot) aimed at enterprises running online customer support and sales. It's a hosted, browser-based solution — no client install required, agents log in from any browser.

Verified key features (from the Key Features page):

2. Product Architecture

ICE is organized around three user roles crossing two primary channels, plus supporting systems:

Role Chat Email
Visitor/Customer Visitor Console (embedded widget) Email Web Form
Agent Operator Console Operator Console (Email mode)
Supervisor Supervisor Console (monitor + join) Supervisor Console (Email mode)
Admin ICE Admin (campaigns, skills, settings, reports) ICE Admin (mail servers, SLAs, templates)

Supporting systems:

3. Authentication & Account Concepts (verified)

4. Operator Console — Verified Workflow

(Source: ICE Chat → Operator Console → Overview, fetched in full)

After login, an agent lands on the Operator Console, which has:

  1. User Account menu (top-right): Profile (personal info / settings / change password / clear stuck chats), Chat History, Internal Chat (agent-to-agent), a "Beep" toggle for new-chat sound alerts, Logout (requires disposing any active chat first + selecting a logout reason).
  2. Chat tab — the live chat queue/workspace.
  3. Email tab — ticket/email workspace, same console.
  4. Available/Not Available dropdown — controls whether the agent receives new chats; default status is configurable in Profile.
  5. My Chats filter — filters the chat grid.
  6. Help icon, Support icon (raises a ticket in ICE's own helpdesk), and video guide icon.

This single console handles both chat and email — they're tabs in the same UI, not separate logins.

5. Full User Manual Topic Map

This is the complete table of contents as it exists on the live site (every page, fully captured from navigation).

5.1 ICE (Introduction)

5.2 ICE Chat

Operator Console (verified overview above)

Supervisor Console

Visitor Console

5.3 ICE Email

Operator Console

Supervisor Console

5.4 ICE Admin

ICE Admin Overview → Change Password, Change Security Question, Help, Support, Logout

User Management

Settings → Common

Settings → Chat

Settings → Email

Reports

5.5 Rule Engine

This is the engine behind "Proactive Chat" — admins compose if/then conditions from these rule groups that trigger an invitation or routing action in the Visitor Console.

5.6 Chat Bot

This is an intent/story-driven bot builder (not pure LLM-based — config is built around explicit intents, conversational "stories," fallback expressions, and a training step), with a webhook hook-out for custom logic.

5.7 ICE Chat WordPress Plugin

Single page — packaged plugin for embedding ICE Chat in WordPress sites.

5.8 ICE Mobile Chat Application

Single page — mobile app for agents.


6. How This Maps to the API Documentation

Everything above is the UI a human uses. The three API products (covered in 02-ICE-API-Reference.md) are the programmatic equivalent — e.g. the Admin → Settings → Common → Campaign UI screens correspond almost 1:1 to the Chat API's Campaign API and Skill API endpoints; the Admin → Settings → Chat → Canned Responses screens correspond to the CannedResponses API; the Reports screens correspond to the Chat/Email Data API.

This is a useful mental model for integration work: if a UI screen exists for it, there's very likely a matching API module with Create/Get/Update/Delete/Enable-Disable verbs.