Customer chat
Customer conversation
Each tenant has one private, text-only conversation with the support team.
- One conversation per customer tenant
- Plain-text messages
- History available through GraphQL
Customer support chat
A simple support chat for your customers one conversation, shared by your team
Give every customer tenant one private conversation with your support team. Use the web app or integrate through GraphQL, WebSockets, and MCP.
1
Conversation per customer
Text
Simple, focused messages
API
GraphQL and WebSockets
A straightforward shared support conversation, built around customer privacy.
Customers and support employees share a private, tenant-scoped conversation.
Why Assist24
A clear line between customer and support
One customer conversation, a shared employee inbox, and straightforward APIs for your product.
Platform capabilities
Everything needed for a basic support chat
A tenant-scoped conversation, a shared employee inbox, and a small set of integration surfaces.
Shared inbox
Shared employee inbox
Authorized support employees can read conversations and reply without assignments.
- Root-operator access
- Any authorized employee can reply
- Tenant boundaries enforced
Integrations
APIs and integrations
Use GraphQL, WebSockets, and tenant-scoped MCP tools to integrate the same chat workflows.
- GraphQL history and send operations
- Live WebSocket notifications
- Tenant-scoped MCP tools
How it works
From customer question to team reply
A tenant-owned conversation keeps customer history in one place and lets any support employee respond.
01
A private customer conversation
Each customer signs in to one conversation tied to their tenant. Messages are visible only to that customer and authorized support employees.
02
One shared support inbox
Root operators see the shared inbox and any authorized employee can reply. There are no assignments or separate queues.
03
Use the interfaces you need
Build around the GraphQL API, receive live updates over WebSockets, or use tenant-scoped MCP tools.
Subscription credits
Straightforward chat credits
Choose a monthly credit plan. Credits do not roll over, and there is no automatic overage.
Founding customer offer
50% off Lite and Standard for the first three paid months
Use FOUNDING50. Limited to the first 100 customers.
FOUNDING50
Request accessChat rates
Customer message5 credits
Per message sent by a customer
Employee reply10 credits
Per reply sent by a support employee
Trial$0 / 30 days
500 base credits plus any invitation bonus, no card required
Customer message = 5 credits, employee reply = 10 credits. Credit usage is charged to the customer tenant.
Lite
1,000 credits/month
Essential monthly credits for getting started with support chat.
$2/month
Up to 100 employee replies or 200 customer messages
- 1 OAuth app
- No rollover or automatic overage
Most popular
Standard
10,000 credits/month
More room for a growing customer support team.
$5/month
Up to 1,000 employee replies or 2,000 customer messages
- 3 OAuth apps
- No rollover or automatic overage
Business
100,000 credits/month
High monthly capacity for busy support teams.
$49/month
Up to 10,000 employee replies or 20,000 customer messages
- 10 OAuth apps
- No rollover or automatic overage
Designed for clear support workflows
Simple chat, ready to integrate
1
Tenant conversation
Private customer history
1
Shared inbox
Available to support employees
API
Integration surfaces
GraphQL, WebSockets, and MCP
Customer support
Give customers a direct, private way to contact your team from the existing web application.
Support operations
Let employees collaborate through a shared inbox without assignments or handoffs.
Product integrations
Use tenant-scoped GraphQL operations, WebSocket updates, and MCP tools.
Automation
Use MCP chat tools with customer-scoped access and the same tenant boundaries as the application.
Frequently asked questions
Frequently asked questions
Chat behavior, integrations, access, and billing.
How does customer chat work?
Each customer tenant has one private conversation with the support team. Customers see their own history; authorized employees can use the shared inbox.
Do support conversations have assignments?
No. Root-operator employees share one inbox, and any authorized employee may reply. There are no assignments or employee-specific queues.
How can I integrate the chat?
Use GraphQL for history and send operations, WebSockets for live notifications, or tenant-scoped MCP tools. Start with the docs and API playground.
Can one customer read another customer’s conversation?
No. Customer access is restricted to the authenticated tenant. Only authorized root-operator employees can access the shared support inbox.
How are chat messages billed?
Customer messages cost 5 credits and employee replies cost 10 credits by default. Both charges are applied to the customer tenant. Monthly credits do not roll over, and there is no automatic overage. See pricing.