Integrations & API

Plug MyLiveChat into the rest of your support stack.

Slack, Discord, and Microsoft Teams alerts. Shopify and WordPress installs. Email-to-ticket and migration workflows. A REST API and signed webhooks for the rest. Your stack, talking to ours.

Try It Free API Docs
Shared workflow

From chat to ticket

Website chat can become follow-up work instead of a dead-end transcript. Missed chats, offline forms, and longer cases all fit the same operator workflow.

Migration

Bring your old queue

Import tickets, knowledge-base articles, and canned-reply macros so a move from Zendesk, Freshdesk, or LiveAgent is operationally realistic.

Automation hooks

Connect the moments that matter

Push chat, ticket, offline-form, and AI handoff events into the tools your operators and back office already use.

One-click installs

Pre-built for the platforms you already use.

Shopify

Add the launcher to every storefront page from the Shopify App Store.

WordPress

Plugin from the WP directory — no theme code edits required.

Wix & Squarespace

Paste the embed snippet into the platform’s custom-HTML block.

Custom HTML

One <script> tag — works on every framework.

Team alerts

Send chat events to Slack, Discord, or Teams.

Paste an incoming webhook URL, choose the events you care about, and route MyLiveChat into the team channel your operators already watch.

Slack Discord Microsoft Teams
  • New chat started
  • Missed chat (no agent online)
  • AI handoff requested
  • Offline-form submission
  • Daily summary digest
Slack notification example
Example team-channel alert when a chat starts or AI requests handoff.
Ticketing workflow

Support work that continues after the live conversation.

Top competitors increasingly bundle live chat with a real queue. MyLiveChat now does the same with email-to-ticket flows, saved views, macros, snooze, SLA-facing triage, and CSAT follow-up hooks that keep unresolved work visible after the browser tab closes.

Email to ticket

Convert inbound support email into tracked ticket threads instead of leaving the queue in a separate inbox.

Saved views

Build reusable queue slices for triage, detractor follow-up, or high-priority work.

Macros + snooze

Respond faster with reusable replies and pause work intentionally when you are waiting on the customer.

CSAT hooks

Trigger surveys and low-score follow-up automations when a ticket is resolved.

Channel roadmap
Open shared inbox page

Build the shared inbox in the right order.

Crisp, Intercom, and Zendesk all sell broader channel coverage than a website widget alone. MyLiveChat is taking the practical path: keep the website and email workflow strong first, then expand into the highest-value adjacent channels without forcing customers into a bloated suite.

Available now
Web + email support core

Live website chat, offline capture, email-to-ticket flow, queue views, macros, and CSAT hooks already run in the same support operation.

Foundation already built
Channel-aware ticket model

The shared queue already understands channel metadata for web, email, WhatsApp, Messenger, Instagram, and SMS so future rollout is additive instead of a separate inbox rewrite.

Next logical launch
WhatsApp Business

WhatsApp closes the biggest SMB expectation gap versus Crisp and Zendesk while staying close to the core support use case.

Why sequence matters
Support-first, not everything-at-once

The goal is not to mimic every enterprise suite. It is to make sure each added channel lands inside the same queue, routing rules, and transcript history operators already use.

What this means for buyers

If you need a polished website support stack today, MyLiveChat is ready now. If your shortlist requires WhatsApp, Messenger, Instagram, or SMS in the same queue on day one, those are roadmap-sensitive conversations rather than GA claims today.

Competitive reality

Why WhatsApp is the next obvious channel.

Reviewed May 7, 2026

The market moved decisively toward shared inbox packaging. Crisp now promotes WhatsApp, Instagram, SMS, Line, and Viber inside its omnichannel inbox. Intercom prices WhatsApp, SMS, and phone as usage-based channels on top of its seat plans and Fin AI outcomes. Zendesk and tawk.to both now document live WhatsApp inbox flows. LiveChat pushes SMS and Apple Messages for Business on higher plans. That makes WhatsApp the smallest launch that closes the biggest expectation gap for SMB buyers.

Crisp
Omnichannel is now the front page.

Public pricing highlights WhatsApp Business, Instagram DMs, SMS, Line, and Viber on the shared inbox story instead of treating them as side integrations.

Intercom
AI-first, but still channel-broad.

Its pricing FAQ now calls out WhatsApp, SMS, and phone as usage-priced channels layered onto the support suite and Fin outcome billing.

Zendesk + tawk.to
WhatsApp is no longer enterprise-only.

Zendesk documents Agent Workspace WhatsApp setup, and tawk.to now documents a WhatsApp inbox for free-first buyers evaluating low-cost support stacks.

LiveChat
Pure-chat rivals widened too.

LiveChat now markets SMS, WhatsApp via marketplace, and Apple Messages for Business on top of its traditional website-chat core.

Recommended sequence

Launch WhatsApp inside the existing queue, reuse the current channel-aware ticket model, and keep transcript continuity, routing rules, and AI handoff behavior identical to web chat. That closes the most visible market gap without forcing a broad social-inbox rewrite.

REST API

A first-class API for everything else.

Bearer-token auth. JSON in, JSON out. No SOAP, no XML, no surprises. Use it to build custom integrations, sync data into your CRM, or power your own internal tooling.

Chats
GET /v1/chats

List + filter conversations. Paginated.

Visitors
POST /v1/visitors

Identify visitors from your own auth.

Articles
PUT /v1/articles

Sync KB content from your CMS.

Agents
GET /v1/agents

Roster, online status, departments.

Transcripts
GET /v1/transcripts/:id

Full conversation export — JSON or HTML.

Webhooks
POST /v1/webhooks

Subscribe to events; we POST to you.

curl -X POST https://api.mylivechat.com/v1/visitors \
  -H "Authorization: Bearer $MLC_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "email": "[email protected]", "name": "Lee", "plan": "pro" }'
Automation controls

The operational layer behind AI and integrations.

Competitors increasingly win on workflow packaging and trust. MyLiveChat already has several of the operator-side controls that matter in practice, even when the marketing story has been quieter than Intercom or Zendesk.

Signed webhooks

Push chat, ticket, knowledge-base, and AI handoff events into your own systems with verifiable outbound deliveries.

Audit-friendly AI

Per-answer review history, handoff reasons, and transcript context make it easier to inspect what the bot did before a human steps in.

Spend controls

Per-site AI billing paths and usage controls help teams choose predictable managed billing or keep model spend on their own OpenAI account.

Feature flags

Roll out voice, webhook, portal, and workflow surfaces gradually instead of exposing unfinished operations to every workspace at once.

Remaining gaps

The integration story is solid, but not yet fully omnichannel.

  • Native messaging channels: the queue is prepared for WhatsApp, Messenger, Instagram, and SMS, but those channels are still the clearest buyer-visible gap versus Crisp, Zendesk, and Intercom.
  • Workflow automation depth: signed webhooks are a strong base, but buyers increasingly expect no-code rules and AI actions that can classify, route, and update external systems automatically.
  • Marketplace breadth: one-click app coverage still reads narrower than larger suite vendors, even when the API can technically cover the same use case.
Build order

The plan that preserves one operating model.

1. Productize shared email workflow: keep proving that chat, tickets, and email already live in one queue.
2. Add WhatsApp on the existing ticket model: use the same routing, transcript, and handoff behavior instead of a sidecar inbox.
3. Layer AI and rules on top: let automation tag, route, collect fields, and trigger webhooks so every new channel lands in the same support system.
Webhooks

Push events to your own server.

Subscribe to chat.started, chat.ended, offline.form, ai.handoff. We POST signed JSON to your URL with retry-on-fail so ticketing, CRM, and internal workflow automations stay in sync.

Visitor SDK

Identify your logged-in users.

Drop-in JS: MyLiveChat.identify({...}). The chat now knows who’s on the line — subscription tier, name, last order, anything you pass.

Migration

Move support data without rebuilding the whole operation.

If you are replacing an incumbent support platform, migration matters as much as feature parity. MyLiveChat includes import workflows so you can preserve the operational basics your team already depends on.

Tickets

Import open, pending, and resolved tickets with requester, status, priority, and description preserved.

Knowledge base

Bring over help-center articles so self-serve and AI do not launch empty.

Macros

Keep canned replies and standard response patterns your agents already rely on.

Zendesk Freshdesk LiveAgent
Build something custom

All paid plans include API access.

Read API Docs Start Free
Free forever for 1 agent

Give every visitor an instant way to reach you.

Launch live chat, connect your knowledge base, and add AI answers when you are ready. No credit card, no trial clock.

Get Started Free View Demo