Docs Live Chat

Live Chat

Set up agent management, routing rules, canned responses, and real-time chat features for your support team.

Overview

The Live Chat console is the central workspace where your support agents handle real-time conversations with website visitors. Access it from Helpon → Live Chat in your WordPress admin panel.

The agent workspace is divided into three main areas:

  • Conversation List (left panel) — All active, pending, and resolved chats sorted by most recent activity. Unread messages are highlighted with a badge count.
  • Chat Window (center panel) — The active conversation thread with message history, typing indicators, and the message composer at the bottom.
  • Visitor Details (right panel) — Contact information, CRM data, session notes, previous conversations, current page URL, browser info, and custom fields.
ℹ️
Real-Time Messaging

Helpon uses WebSocket connections for instant message delivery. Messages appear in real time without page refreshes. If WebSockets are unavailable, the system falls back to AJAX long-polling automatically.

Agent Management

Agents are WordPress users who have been granted access to the Helpon Live Chat console. You can manage agents from Helpon → Settings → Agents.

Adding Agents

1

Navigate to Agent Settings

Go to Helpon → Settings → Agents and click the Add Agent button in the top-right corner.

2

Select a WordPress User

Choose an existing WordPress user from the dropdown. The user must already have an account on your site. If they don't, create a WordPress user first via Users → Add New.

3

Assign a Role

Choose between Admin, Supervisor, or Agent. Each role has different permissions within the Live Chat console (see role table below).

4

Configure Agent Profile

Set a display name, avatar, department, skills (tags), and the maximum number of concurrent chats this agent can handle. Click Save Agent to finish.

WordPress User *
Sarah Johnson (sarah@clinic.com) ▾
Agent Role *
Agent ▾
Department
General Support ▾
Display Name
Sarah J.
Max Concurrent Chats
5
Skills (comma-separated)
billing, appointments, insurance

Agent Roles

Permission Admin Supervisor Agent
Handle chats Yes Yes Yes
View all conversations Yes Yes Own only
Transfer chats Yes Yes Yes
Manage canned responses Yes Yes Own only
View analytics Yes Yes No
Manage agents Yes No No
Configure routing rules Yes No No
Access settings Yes Limited No

Chat Routing

Chat routing determines how incoming conversations are distributed among available agents. Configure routing from Helpon → Settings → Live Chat → Routing.

Helpon supports four routing methods. Choose the one that best fits your team structure:

Method How It Works Best For
Round-Robin Distributes chats evenly across all online agents in sequential order, regardless of current workload. Small teams with generalist agents who handle similar types of queries.
Skill-Based Matches incoming chats to agents based on skill tags. The visitor's initial message is analyzed by AI to identify the required skill set. Teams with specialized agents (billing, technical, appointments, insurance).
Load-Balanced Assigns new chats to the agent with the fewest active conversations, keeping workload evenly distributed at all times. High-volume teams where balanced workload is more important than specialization.
Department-Based Routes chats to specific departments chosen by the visitor via a pre-chat form or menu. Within the department, load-balancing applies. Organizations with distinct departments (Sales, Support, Billing, Scheduling).
Combining Routing Methods

You can combine Department-Based routing with Skill-Based or Load-Balanced as a secondary strategy. For example, route to the Billing department first, then use load-balancing among billing agents.

Auto-Assignment

Auto-assignment automatically distributes incoming chats to available agents without manual intervention. Configure it from Helpon → Settings → Live Chat → Auto-Assignment.

Auto-Assignment
Enabled
Routing Method
Load-Balanced ▾
Assignment Timeout
30 seconds
Time to wait before re-routing to another agent
Max Queue Size
20
Maximum pending chats before overflow triggers
Priority Queue
Enabled
Overflow Action
Show offline form ▾
Action when all agents are at capacity: show offline form, queue with position, or redirect to AI

How Auto-Assignment Works

  • New chat arrives — The system checks for available agents who are online and below their maximum concurrent chat limit.
  • Agent matched — Based on the selected routing method, the best agent is chosen and receives a notification with a sound alert.
  • Assignment timeout — If the assigned agent doesn't respond within the timeout period, the chat is re-routed to the next available agent.
  • No agents available — If all agents are at capacity or offline, the overflow action is triggered (offline form, queue position display, or AI handoff).

Priority Queue

When enabled, the priority queue reorders incoming chats based on these factors:

  • Returning visitors — Existing CRM contacts are prioritized over anonymous visitors.
  • VIP tags — Contacts tagged as VIP in your CRM are placed at the front of the queue.
  • Wait time — Visitors who have been waiting longest are moved up progressively.
  • Page context — Visitors on checkout or pricing pages receive higher priority.
ℹ️
Disabling Auto-Assignment

When auto-assignment is disabled, incoming chats appear in a shared queue. Agents must manually pick up conversations by clicking Accept on each chat. This is useful for small teams who prefer to choose which conversations to handle.

Canned Responses

Canned responses are pre-written message templates that agents can insert during conversations using shortcodes. Manage them from Helpon → Settings → Live Chat → Canned Responses.

Creating Canned Responses

1

Add a New Response

Click Add Canned Response. Enter a shortcode (e.g., /greet), a title for internal reference, and the response body.

2

Assign a Category

Organize responses into categories like Greetings, Billing, Hours, Closings, or create custom categories. Categories help agents find the right response quickly.

3

Add Variables (Optional)

Use dynamic variables in your response body to personalize messages. Variables are replaced with real data when the response is inserted into a conversation.

4

Save and Test

Click Save. Open a chat conversation and type the shortcode (e.g., /greet) to verify it auto-completes correctly with variable substitution.

Shortcode Examples

Canned Response: /greet
Hello {{visitor_name}}! Welcome to {{business_name}}. How can I assist you today?
Canned Response: /hours
Our business hours are:
Monday - Friday: 9:00 AM - 6:00 PM
Saturday: 10:00 AM - 2:00 PM
Sunday: Closed

You can also book an appointment online anytime at {{booking_url}}.
Canned Response: /thanks
Thank you for contacting {{business_name}}, {{visitor_name}}! If you have any more questions, don't hesitate to reach out. Have a great day!
Canned Response: /transfer
I'm going to connect you with a specialist from our {{department}} team who can better assist you with this. Please hold for just a moment.

Available Variables

Variable Description Example Output
{{visitor_name}} Visitor's name from the pre-chat form or CRM John Smith
{{visitor_email}} Visitor's email address john@example.com
{{business_name}} Your business name from settings My Dental Clinic
{{agent_name}} Current agent's display name Sarah J.
{{booking_url}} Your online booking page URL https://clinic.com/book
{{department}} Current chat's assigned department Billing
{{ticket_id}} Conversation reference number #HC-00482

Import & Export

You can bulk-manage canned responses using CSV files. Go to Helpon → Settings → Live Chat → Canned Responses and use the Import or Export buttons. The CSV format requires four columns: shortcode, title, category, and body.

CSV Import Format
shortcode,title,category,body
/greet,Welcome Greeting,Greetings,"Hello {{visitor_name}}! How can I help you?"
/hours,Business Hours,General,"We're open Mon-Fri 9AM-6PM, Sat 10AM-2PM."
/thanks,Thank You,Closings,"Thanks for reaching out! Have a great day."

Session Notes

Session notes allow agents to add internal annotations to conversations that are only visible to your team, never to visitors. Notes appear in the right-side Visitor Details panel under the Notes tab.

Add Note
Patient asked about insurance coverage for teeth whitening. Referred to billing dept for detailed pricing. Follow up next week.
Tags
insurance, whitening, follow-up
Template
Custom Note ▾
Visibility
All Agents ▾
Options: All Agents, Supervisors Only, Private (only me)

Note Features

  • Tagging system — Add tags to notes for easy filtering and searching. Common tags include follow-up, urgent, billing, complaint, and escalated.
  • Note templates — Create reusable templates for common note types like handoff summaries, complaint logs, or follow-up reminders. Templates are managed in Settings → Live Chat → Note Templates.
  • Visibility rules — Control who can see each note. Options include All Agents, Supervisors Only, or Private (only the note author).
  • Timestamps — Every note is automatically timestamped with the agent's name, making it easy to track when annotations were added and by whom.
  • Pinned notes — Important notes can be pinned to the top of the notes panel so they are always visible when any agent opens the conversation.
Pro Tip

Use pinned notes for critical information like patient allergies, VIP status, or ongoing issues. Pinned notes persist across sessions and are visible to every agent who opens the conversation.

Chat Features

Helpon provides a rich set of real-time communication features for both agents and visitors. Configure these from Helpon → Settings → Live Chat → Features.

Feature Description Default Configurable
Typing Indicators Shows a "typing..." animation when either party is composing a message. Agents can also see a live preview of what the visitor is typing. Enabled Yes
Read Receipts Displays checkmarks to indicate message delivery and read status. Single check = delivered, double check = read. Enabled Yes
File Sharing Allows visitors and agents to share files. Supported types: JPG, PNG, GIF, PDF, DOC, DOCX, XLS, XLSX, CSV, TXT, ZIP. Max size: 10 MB per file. Enabled Yes
Emoji Picker A full emoji picker panel accessible from the message composer for both agents and visitors. Enabled Yes
Message Formatting Supports basic Markdown formatting: **bold**, *italic*, `code`, and clickable URLs. Agents also have a rich-text toolbar. Enabled Yes
Chat Transfer Agents can transfer a conversation to another agent or department. The full chat history and notes follow the transfer. Enabled Yes
Sound Notifications Audible alerts for new messages, new chats, and transfer requests. Agents can customize which sounds are active. Enabled Yes
Desktop Notifications Browser push notifications for incoming chats when the agent's tab is not focused. Requires browser permission. Enabled Yes

File Sharing Details

File sharing can be restricted per role. Admins can configure allowed file types and maximum file sizes from the settings panel.

Setting Default Options
Allowed file types JPG, PNG, GIF, PDF, DOC, DOCX Customizable list of extensions
Max file size 10 MB 1 MB to 25 MB
Visitor uploads Enabled Enable / Disable
Auto-scan for viruses Enabled Enable / Disable (requires server-side ClamAV)
Storage location WordPress Media Library Media Library, Custom folder, Amazon S3

Chat Transfer

To transfer a conversation, click the Transfer icon in the chat toolbar. You can transfer to a specific agent, a department, or back to the AI. The receiving agent sees the full conversation history, session notes, and visitor details.

ℹ️
Transfer Notifications

When a chat is transferred, the visitor sees a message like "You've been connected with [Agent Name]." The receiving agent gets both an audible alert and a desktop notification with the transfer reason (if provided).

Agent Availability

Agent availability determines whether an agent can receive new chat assignments. Agents can set their status from the Live Chat console toolbar at the top of the page.

Agent Status
Online ▾
Options: Online (green), Away (yellow), Offline (gray)
Auto-Away Timeout
10 minutes
Automatically switch to Away after this period of inactivity
Offline Routing
Redirect to AI ▾
What happens when all agents are offline: Redirect to AI, Show offline form, Display queue message
Show Status Indicators to Visitors
Enabled

Status Behavior

  • Online (green dot) — Agent is active and can receive new chat assignments. Appears in routing pool. Visitors see a green indicator on the widget.
  • Away (yellow dot) — Agent is temporarily unavailable. Existing chats remain active, but no new chats are assigned. Useful for breaks or meetings.
  • Offline (gray dot) — Agent is not available. All new chats are routed to other online agents. If no agents are online, the offline routing behavior triggers.

Auto-Away

When enabled, the system automatically switches an agent to Away status after a configurable period of inactivity (no mouse movement, keyboard input, or chat activity). The default timeout is 10 minutes. Once the agent becomes active again, their status automatically returns to Online.

Offline Routing Behavior

When all agents are offline, incoming chats are handled based on the configured offline routing behavior:

  • Redirect to AI — The AI chatbot takes over and handles the conversation. If the AI cannot resolve the issue, it collects the visitor's contact information for a follow-up.
  • Show offline form — Displays a form asking for the visitor's name, email, and message. Submissions are saved as tickets in the conversation queue.
  • Display queue message — Shows a custom message informing the visitor that agents are currently unavailable and provides estimated availability hours.

Escalation Rules

Escalation rules define when and how conversations are transferred from the AI chatbot to a human agent. Configure these from Helpon → Settings → Live Chat → Escalation.

Setting Up Escalation Triggers

1

Enable AI-to-Human Escalation

Go to Helpon → Settings → Live Chat → Escalation and toggle Enable Escalation to on. This activates the automatic handoff system between the AI and live agents.

2

Configure Confidence Threshold

Set the AI confidence threshold (0-100%). When the AI's confidence score drops below this threshold for a response, the conversation is automatically escalated to a human agent. The default is 40%.

3

Define Keyword Triggers

Add specific keywords or phrases that immediately trigger escalation regardless of AI confidence. Common triggers include: "speak to a person", "human agent", "manager", "complaint", "urgent", "emergency", and "cancel".

4

Set Visitor Request Handling

When a visitor explicitly asks to speak with a human, Helpon can either escalate immediately or ask a qualifying question first (e.g., "Can you briefly describe your issue so we can connect you with the right person?").

5

Configure Escalation Priority

Choose the priority level for escalated chats: Normal (enters the standard queue), High (placed near the front of the queue), or Urgent (immediately assigned to the next available agent with an alert).

6

Set Up Notifications

Configure how agents are notified of escalated chats. Options include desktop push notification, sound alert, email notification, and Slack webhook. You can enable multiple notification channels simultaneously.

⚠️
No Agents Online

If an escalation triggers but no agents are online, the AI will inform the visitor that an agent is currently unavailable, collect their contact information, and create a pending conversation in the queue. The chat will be assigned to the first agent who comes online.

Troubleshooting

Common Live Chat issues and their solutions:

Messages not delivering

  • Check your server's WebSocket support. Helpon requires WebSocket connections on port 443 (wss://). Contact your hosting provider if WebSockets are blocked.
  • Verify that your SSL certificate is valid and not expired. Mixed content (HTTP/HTTPS) blocks WebSocket connections.
  • Clear your browser cache and disable browser extensions that may interfere with WebSocket connections (ad blockers, privacy extensions).
  • Check the browser console (F12 → Console) for connection errors. Look for "WebSocket connection failed" messages.
  • If using Cloudflare, ensure WebSockets are enabled in the Cloudflare dashboard under Network → WebSockets.

Agent not receiving notifications

  • Verify the agent's status is set to Online, not Away or Offline.
  • Check that browser notification permissions are granted. Go to your browser settings and ensure notifications are allowed for your WordPress admin domain.
  • Ensure the agent has not reached their maximum concurrent chat limit. Check the limit in Helpon → Settings → Agents.
  • Confirm that sound notifications are not muted in the agent's Live Chat console toolbar.
  • If using auto-assignment, verify the agent's skills match the routing rules for the incoming chat.

File upload failures

  • Check that the file type is in the allowed list. Go to Helpon → Settings → Live Chat → Features → File Sharing to review allowed types.
  • Verify the file size does not exceed the configured maximum (default: 10 MB). Also check your PHP upload_max_filesize and post_max_size settings in php.ini.
  • Ensure your WordPress wp-content/uploads directory is writable (permissions 755 or 775).
  • If using Amazon S3 storage, verify your S3 credentials and bucket permissions are correctly configured.

Connection drops

  • Intermittent disconnections are often caused by server timeout settings. Increase your PHP max_execution_time and your web server's keep-alive timeout.
  • If using a reverse proxy (Nginx, Apache), ensure the proxy timeout values are sufficient. Set proxy_read_timeout to at least 300 seconds for Nginx.
  • Check your hosting provider's connection limits. Shared hosting environments may restrict long-running connections.
  • Helpon includes automatic reconnection logic. If the WebSocket drops, the client will attempt to reconnect every 3 seconds for up to 30 attempts before falling back to AJAX polling.
  • Monitor your server's memory usage. High memory consumption can cause the PHP process to be killed, dropping active connections.
⚠️
Caching Conflicts

Full-page caching plugins can interfere with Live Chat functionality. Add /wp-admin/admin-ajax.php and /wp-json/helpon/v1/* to your cache exclusion list. If using a CDN, exclude WebSocket connections from being cached or proxied.