Skip to main content

Chat Workspace

Interface Layout Breakdown

1. Search, Filter, & Add Bar

Positioned at the upper left quadrant of the interface, this control row houses three critical manipulation modules:

  • Search: Allows query strings to execute text scans across customer conversation indices.
  • Filtering Row: Refines visibility metrics by parsing target conversation parameters such as active Department targets, associated content Tags, or transactional customer Ratings.
  • Add Conversation: An interactive dialog component allowing agents to manually initiate conversation streams pointing directly to targeted deployment nodes.

2. Omnichannel Network Filter Sidebar

A secondary side filtering strip enables real-time viewport updates by filtering chat feeds based on originating platforms. Operators can toggle multi-selection filters to view combinations of channels simultaneously.

3. Lifecycle Status Filters

The core conversation list view is segmented into five distinct functional state queues:

  • All: Displays all historical and ongoing customer interactions without lifecycle exclusions.
  • Unassigned: Isolates incoming conversations awaiting automated routing rules or manual agent pickups.
  • Open: Houses ongoing, active communications requiring immediate response loops.
  • On Hold: Holds paused interactions awaiting background client information or developer trace completions.
  • Resolved: Chronologically logs closed or finalized conversations.

4. Conversation Feed Directory

Renders conversational list items with inline execution updates:

  • Customer Identity: Explicit identifier profiles (e.g., Client#1) bound alongside an adaptive avatar badged with the icon of the source platform channel.
  • Last Message Preview: Outputs a partial snippet showing the latest message snippet string payload.
  • Time Metrics: Calculates real-time time metrics denoting durations elapsed since the last incoming message payload transmission.
  • Satisfaction Ratings: Renders visual indicator star metrics directly within item cards for closed items that received customer reviews.

5. Chat Communication Main Window

Renders the continuous conversational log containing:

  • End-user raw client content submissions.
  • Agent reply frames.
  • Definitive timestamps marking transactional server receipt times.
  • Clear sender identification text parameters.

6. Contact Information & Workspace Control Overlay

An expansive utility panel sliding out from the right workspace perimeter when selecting the top-right information panel icon. It includes:

  • Lifecycle State: Displays current status parameters (e.g., In progress) paired with state adjustment inputs.
  • Channel Profile: Denotes the operational platform origin context (e.g., Widget).
  • Information Tabs:
    1. Profile: Exposes core client telemetry details comprising full name parameters, verification emails, and cellular numbers.
    2. Notes: A shared canvas for appending internal system notes regarding the customer case.
    3. Ticket Creator: Seamlessly instantiates a support tracking object directly mapping input fields for Subject, Message Context, Priority Levels, Target Assignee, and relational Content Tags, backed by an execution Create submission button.
  • Customer Satisfaction Rating: Renders active survey score data fields strictly when viewing closed items containing submitted ratings data.
  • Core Controls: Dynamic runtime inputs enabling operators to shift operational control profiles (e.g., switching from Human interaction modes over to Autopilot AI) or toggling inline language translation layers.
  • Knowledge Base Explorer: An embedded search module pulling internal FAQ lookups directly into the view without breaking workflow navigation.

7. Message Compiling Input Box

  • Text Input Frame: Housing structural inline text elements with Type a message placeholders.
  • Utility Triggers: Integrated controls providing support for rich media attachment vectors including emoji selectors, recorded voice parameters, and binary document file attachment handlers.
  • Send Button: Appends message strings onto outgoing transmission queues.

Shared Canned Responses Subsystem

1. Creating Canned Responses

  • Canned responses are built directly by authorized support personnel or administrators.
  • Authors write recurring solution text strings inside dedicated composition inputs.
  • Categorization arrays (hashtags) are appended onto individual assets to allow for automated prefix matching queries.
  • View visibility settings can be designated as either Private or Public across entire team directories.

2. Deploying Responses Inside Chats

  • Operators run lookup queries or match hashtag strings to select an item from the canned responses directory.
  • The system inserts the text block template payload directly into the active conversation message context area.
  • Operators maintain granular control to edit or adjust the inserted text layout freely prior to finalizing transmission.

AI Contextual Message Optimization

Clicking the drop-down action arrow embedded on incoming client chat frames exposes localized context optimization tools powered by AI layers:

  • Translate: Processes incoming texts through translation engines into target workspace language targets.
  • Rephrase: Generates alternate tones or refined vocabulary versions of draft copy text elements.
  • Summarize: Distills lengthy corporate text descriptions into crisp, informative message definitions.
  • Suggest Reply: Evaluates conversational context threads to propose optimal, immediate agent reply configurations.

Complete User Flow Instructions

  1. Claiming Focus: Click any item in the chat feed directory to pull its timeline into focus in the main communication window.
  2. Replying: Draft text within the message input box and click Send.
  3. Optimizing Client Content: Click the contextual action arrow on any incoming message card to translate, rephrase, or summarize raw text blocks.
  4. Altering Lifecycles: Open the information side panel to adjust conversation lifecycle states as work progresses.
  5. Logging Incidents: Submit detailed support tickets directly via the right-side informational tracker tab when customer issues require deep engineering interventions.
  6. Internal Collaboration: Use the localized note canvas inside the information drawer to pass relevant metrics to incoming shifts.
  7. Deploying Attachments: Click the attachment attachment trigger icon, choose a local target path from your file explorer modal, and execute the Upload event command.
Subscribe to our newsletter Stay up to date! Get all the latest & greatest posts delivered straight to your inbox.