Integrations
Send chat alerts to your team, install the widget on the platforms you use, and connect follow-up work with your CRM, inbox, or support process when you need it.
Shared workflow
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
Import tickets, knowledge-base articles, and canned-reply macros so a move from Zendesk, Freshdesk, or LiveAgent is operationally realistic.
Connected alerts
Send chat, offline-message, and AI handoff moments to the tools your support team already checks.
One-click installs
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
Use the platform’s embed block and follow the guided setup steps.
Custom sites
Guided setup works on custom websites and common frameworks.
Team alerts
Choose the alerts 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
Example team-channel alert when a chat starts or AI requests handoff.
Ticketing workflow
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.
Start with the website and email workflows your team needs most, then add the highest-value connected channels without forcing agents 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.
Ready to extend
Shared follow-up model
Keep routing, transcripts, and ownership consistent as more customer touchpoints are connected.
Plan ahead
Messaging channels
If your team needs social or messaging channels on day one, review the best setup path with support before rollout.
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 your team
If you need a polished website support stack today, MyLiveChat is ready now. If you need more messaging channels in the same queue on day one, talk with support so the rollout matches your expectations.
Most teams do not need every channel on day one. Start with the touchpoints that produce real customer questions, then keep those conversations connected to the same agents, transcripts, and follow-up workflow.
Website
Best first channel.
Website chat is where visitors already compare plans, ask support questions, and decide whether to contact you.
Email
Useful follow-up path.
Email follow-up keeps missed chats, offline messages, and longer cases from disappearing.
Messaging
Plan by demand.
Add messaging channels when your customers regularly ask for them and your agents are ready to support them.
AI
Keep handoff consistent.
Use AI to answer routine questions while keeping human handoff and transcripts in the same workflow.
Recommended sequence
Launch website chat first, connect follow-up and team alerts next, then add custom or messaging workflows when customer demand is clear.
Custom integrations
Use integration details to sync customer data, connect CRM workflows, or support internal reporting when the standard setup is not enough.
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.
Alerts
Team notifications
Send key events to your tools.
curl -X POST https://api.mylivechat.com/v1/visitors \
-H "Authorization: Bearer $MLC_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "email": "lee@example.com", "name": "Lee", "plan": "pro" }'
For teams with custom requirements, MyLiveChat can connect support activity with ticketing, CRM, reporting, and internal workflow tools.
Follow-up updates
Keep ticket status, ownership, priority, notes, and reminders connected to the chat workflow.
Queue shaping
Use tags, shared replies, saved views, policies, and time logs to keep automated follow-up aligned with agent work.
Delivery + trust
Delivery logs and test tools help teams verify alerts before relying on them in daily operations.
Room to grow
Start with the integrations your team needs today, then add more automation and channels as your support process grows.
Workflow controls
Integrations are most useful when they make follow-up easier. MyLiveChat keeps alerts, transcripts, tags, reviews, and AI handoff context tied to the same visitor conversation.
Reliable event alerts
Send important chat, follow-up, and AI handoff moments to the systems your team relies on.
Audit-friendly AI
Answer history, handoff reasons, and transcript context make AI-assisted conversations easier to review.
Spend controls
AI usage controls help teams keep support coverage predictable as conversation volume grows.
Controlled rollout
Turn on new support workflows gradually so teams can adopt changes without disruption.
Clear expectations
- Website-first today: MyLiveChat is strongest when website chat, offline messages, transcripts, and follow-up are the center of your support workflow.
- Automation when needed: connect alerts and follow-up work first, then add deeper rules as your team is ready.
- Practical integrations: use pre-built installs where available and integration details for custom workflows.
Recommended rollout
1. Install chat where customers ask questions: start with your website and key product or pricing pages.
2. Connect team notifications: send urgent chats and handoff moments to the channels your team already monitors.
3. Add deeper workflows: connect CRM, ticketing, or custom follow-up when your team needs more automation.
Custom alerts
When chats start, end, move offline, or hand off from AI, MyLiveChat can notify your ticketing, CRM, or internal workflow tools so follow-up stays in sync.
Visitor context
Pass useful customer details into the chat experience so agents can see who is asking, what plan they are on, and what they may need next.
Migration
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