Live chat pricing usually comes down to three variables: how many people reply to customers, how many conversations you handle, and which features are locked behind higher tiers. A small team may pay $0 for a lightweight contact layer, $20–$132 per agent per month for seat-based tools, or hundreds per month once usage, branding removal, channels, and add-ons are included.
TL;DR
- Per-agent pricing: annual cost = agents × monthly seat price × 12. It is predictable, but costs rise every time another person needs access.
- Per-conversation pricing: cost depends on usage volume. It can be efficient for small teams, but spikes during launches, incidents, or seasonal traffic.
- Flat-rate pricing: one workspace or account price. It is simpler to budget, but you must check limits on seats, conversations, channels, history, and branding.
- Published prices are not the full budget. Check extra seats, history retention, branding removal, channel expansion, integrations, and taxes.
- Knocket’s core contact experience is 100% free forever: Web Widget, Contact Page, Mobile Widget, unified Inbox, Telegram/Email ingestion, no card, and no message caps. It is designed for makers, founders, creators, service providers, and small teams that need a simple way to be reachable.
- Pay when the operational requirement justifies it: complex routing, formal SLAs, audit controls, advanced reporting, or enterprise procurement may be worth a paid suite.
Live chat pricing at a glance: what you actually pay for
When people search for “live chat cost,” they often expect one number. The real answer is a stack:
| Cost layer | What it means | Why it changes your bill |
|---|---|---|
| Seats or agents | People who can reply to customers | Seat-based tools multiply price by headcount |
| Conversations or resolutions | Customer threads handled per month | Usage-based pricing rises with traffic |
| Channels | Website chat, email, Telegram, social messaging, app chat | Some tools charge more for additional channels |
| History | How long you can search old conversations | Lower tiers may limit retention or reporting depth |
| Branding | Vendor badge on the widget | Removing branding can require a higher tier |
| Integrations | CRM, ecommerce, analytics, or workflow tools | Advanced integrations may sit behind paid plans |
| Support operations | SLA, roles, routing, permissions, audit logs | Usually priced for larger teams |
For a solo founder, the meaningful question is often: “Can users reach me without forcing them to create an account?” For a growing support team, the question becomes: “How much does each additional responder cost, and what happens when volume doubles?”
That difference matters. Grand View Research describes customer experience management as a growing software category, but the budgeting problem at small-team level is practical, not abstract: the first paid seat may be manageable; the fifth, tenth, or seasonal overage may not be.
If you only need a website chat button, a shareable contact link, app-side contact entry, and one calm place to reply, start with the smallest system that covers those jobs. For Knocket, the starting path is installing the Web Widget from the Knocket console, publishing a shareable Contact Page, or replying from the unified Knocket Inbox.
The 3 common live chat pricing models: per agent, per conversation, and flat rate
1. Per-agent pricing
Per-agent pricing charges for each teammate who needs access.
Formula:
number of agents × price per agent per month × number of months
Example: if a tool costs $55 per agent per month and you have 6 agents, the annual software cost is:
6 × $55 × 12 = $3,960 per year
This model is easy to forecast when headcount is stable. It gets expensive when founders, engineers, sales, customer success, and part-time contractors all need to jump into the inbox.
Best fit:
- Dedicated support teams
- Predictable staffing
- Companies that need named users, roles, and reporting by agent
Watch out for:
- Paying for occasional responders
- Paying for admins who rarely reply
- Higher tiers required for full history, routing, or branding control
2. Per-conversation pricing
Per-conversation pricing charges based on the number of customer conversations, handled threads, or billable usage events. Vendors define “conversation” differently, so read the pricing page and billing terms carefully.
Formula:
base subscription + included conversations + overage or usage charges
Example:
- Plan includes 100 conversations per month
- You handle 240 conversations
- The extra 140 may require an upgrade or usage charge
This model can work well when only a few people reply but message volume is predictable. It can surprise you during a Product Hunt launch, Black Friday sale, service incident, or viral post.
Best fit:
- Small team, variable support load
- Businesses that want fewer named seats
- Teams comfortable tracking monthly usage
Watch out for:
- What counts as a billable conversation
- Whether spam/test messages count
- Whether outbound campaigns or bot-handled threads are billed differently
- Overage behavior: hard stop, auto-upgrade, or extra charge
3. Flat-rate live chat software
Flat-rate pricing charges one account or workspace fee, often by tier.
Formula:
workspace price per month × 12 + add-ons
A flat rate is easiest to explain to a founder or finance lead: “This inbox costs $X per month.” But “flat” rarely means unlimited in every dimension. Check how many seats, sites, conversations, channels, and history windows are included.
Best fit:
- Makers and small teams that want predictable cost
- Teams with many occasional responders
- Early-stage products testing demand
Watch out for:
- Seat caps inside the flat rate
- Conversation caps
- Branding restrictions
- Limited integrations or history
Real live chat pricing table: official public prices and lookup date
The table below uses official public pricing pages checked on September 28, 2026. Vendors change prices, billing terms, packaging, and regional display. Re-check the linked page before purchasing or publishing a final procurement memo.
| Product | Public entry pricing shown | Pricing model | Billing note | Official source |
|---|---|---|---|---|
| Knocket | $0 | Flat $0 core contact experience | 100% free forever, no card, no message caps for core contact | Knocket homepage |
| LiveChat | Starter from $20/agent/month; Team $41/agent/month; Business $59/agent/month | Per agent | Prices commonly displayed for annual billing; Enterprise custom | LiveChat pricing |
| Zendesk Suite | Team $55/agent/month; Growth $89/agent/month; Professional $115/agent/month | Per agent | Annual billing display; Enterprise/custom tiers available | Zendesk pricing |
| Intercom | Essential $29/seat/month; Advanced $85/seat/month; Expert $132/seat/month | Per seat plus possible usage/add-ons | Public plans; usage-based items may apply depending on setup | Intercom pricing |
| Tidio | Starter $29/month; Growth $59/month; Plus from $749/month | Workspace/package pricing with usage and tier limits | Public monthly package display; check included conversations and seats | Tidio pricing |
This table is not a feature-equivalence claim. LiveChat, Zendesk, Intercom, Tidio, and Knocket are packaged for different support operations. The useful comparison is cost behavior:
- LiveChat, Zendesk, and Intercom: cost scales clearly with seats.
- Tidio: package-style pricing; check included limits carefully.
- Knocket: $0 core contact layer for being reachable across web, mobile, a contact link, Telegram, Email, and one Inbox.
For industry context, you can also compare customer support and experience software trends through external research from sources such as Grand View Research, Gartner, and Statista.
Per-agent pricing example: agents × monthly price × 12 = annual cost
Per-agent pricing looks small until you multiply it by everyone who needs to answer customers.
Assume you have:
- 1 founder
- 2 support agents
- 1 customer success teammate
- 1 engineer who helps with technical questions
- 1 operations teammate who covers weekends
That is 6 potential responders.
| Tool and public tier example | Formula | Annual software cost |
|---|---|---|
| LiveChat Team at $41/agent/month | 6 × $41 × 12 | $2,952/year |
| Zendesk Suite Team at $55/agent/month | 6 × $55 × 12 | $3,960/year |
| Intercom Advanced at $85/seat/month | 6 × $85 × 12 | $6,120/year |
| Intercom Expert at $132/seat/month | 6 × $132 × 12 | $9,504/year |
These figures exclude tax, discounts, add-ons, implementation, and internal time. They also assume the public annual-billing prices above remain unchanged.
The hidden part is occasional access. If the engineer only replies twice a month, the seat may still cost the same as a full-time agent. If the founder wants visibility but rarely responds, that may still count as a paid user in many tools. This is why “support inbox pricing” should be calculated from real workflow, not only the pricing page headline.
Hidden costs to check before choosing live chat software
Extra seats
Ask: who truly needs to reply, and who only needs summaries exported elsewhere? Per-agent tools can be efficient for dedicated teams, but expensive for small companies where many people occasionally help.
Checklist:
- Are admins billed?
- Are light users or viewers billed?
- Can teammates reply from mobile without another product?
- Do contractors need temporary seats?
Knocket’s mobile H5 Inbox gives operators a browser-based way to reply from a phone, while Telegram quote reply can send responses back to the visitor’s original screen when Full mode is configured.
Conversation history
History matters when a user returns three months later and says, “I asked about this before.” Some plans restrict searchable history or advanced reporting by tier.
Ask:
- Is chat history unlimited, time-limited, or tier-limited?
- Can you see the same conversation across web, mobile, and external channels?
- Are exports included?
Knocket brings Web Widget, Mobile Widget, Contact Page, Telegram, and Email into one Inbox with shared conversation history for the same thread.
Removing vendor branding
A low entry price may include visible vendor branding on the chat widget. That may be fine for an early maker. For a consulting business, ecommerce brand, or SaaS landing page, branding removal may matter.
Ask:
- Is vendor branding shown?
- Which tier removes it?
- Does branding differ between web widget, contact page, and mobile entry?
Channel expansion
Many teams start with website chat and later add email, mobile app contact, or messaging channels. The price question is not just “What does the widget cost?” It is “What happens when support moves beyond the website?”
Ask:
- Is email a channel or only a notification method?
- Can Telegram messages enter the same inbox?
- Does replying from Telegram send the answer back to the original visitor entry?
- Are app users supported through a native-feeling WebView entry?
Knocket supports Web Widget, Mobile Widget, Contact Page, Telegram, and Email into a unified Inbox. For a website, the Web Widget can be added with one async script such as <script src="https://trtc.io/knocket-sdk/sdk.js?identifier=YOUR_IDENTIFIER" async></script>, copied from the console. It works with WordPress, Shopify, React, Astro, and plain HTML. Mobile Widget supports iOS, Android, React Native, and Flutter through a WebView-based flow.
For setup, use the actual code and URLs from Knocket installation settings rather than hand-building links.
Implementation and maintenance
Even if software is inexpensive, setup time is not free.
For each vendor, estimate:
- Time to install the widget
- Time to configure availability and offline forms
- Time to connect channels
- Time to train responders
- Time to clean up spam and test conversations
- Time to update privacy and data-handling docs
A no-backend install can save real engineering time. Knocket’s Web Widget uses a script tag, Contact Page is published from the console, and Mobile Widget uses a WebView entry inside the app.
What a $0 live chat plan can do: where Knocket fits
A $0 live chat option is enough when your goal is simple: make it easy for users to contact you and easy for you to answer without building backend messaging infrastructure.
Knocket’s core contact experience is 100% free forever with no card required and no message caps. It is built around one idea: a free contact layer for makers who ship.
What you can do with Knocket at $0:
| Need | Knocket capability |
|---|---|
| Add live chat to a website | Web Widget via one script tag |
| Support common site platforms | WordPress, Shopify, React, Astro, plain HTML, and other custom-code sites |
| Let users contact you without a website | Contact Page at knocket.io/your-handle style shareable link |
| Put a contact link in social bios | Use the Contact Page in X bio, GitHub README, email signature, or QR code |
| Add contact inside an app | Mobile Widget for iOS, Android, React Native, and Flutter |
| Centralize conversations | Unified Inbox for Web Widget, Mobile Widget, Contact Page, Telegram, and Email |
| Reply from Telegram | Configure Telegram; in Full and quote reply mode, quoted replies can return to the visitor screen |
| Capture offline context | Offline form can capture email and bring context into the Inbox |
| Avoid visitor account friction | Visitors do not need to register; only the owner needs an account |
Use Knocket Contact Page management when you need a shareable page, Knocket Inbox when you want to handle conversations, and Knocket installation when you are adding the widget or app entry.
This is not the same as buying a full enterprise support suite. It is a lightweight way to be reachable across the places where early users already knock.
The limits of free live chat tools: when $0 is not enough
Free live chat software is not automatically the right answer for every support operation.
Start evaluating paid tools when you need:
- Complex role-based permissions
- Multiple formal teams or departments
- SLA tracking and escalation policies
- Advanced routing by account, region, or contract
- Audit logs for compliance workflows
- Deep reporting for a dedicated support organization
- Large-scale outbound campaign management
- Enterprise procurement, security reviews, and vendor contracts
- Custom workflows tied to CRM, billing, or ticketing systems
The honest boundary: Knocket is a lightweight customer contact platform. It is not positioned as a CRM, enterprise helpdesk, or complete ticketing system replacement. If your support process depends on queues, strict SLAs, macro libraries, workforce management, and multi-layer approvals, a paid suite may be the correct operational choice.
The decision should not be “free versus paid.” It should be “contact layer versus support operating system.”
When should you start paying for live chat software?
Start paying when the cost of missing operational controls is higher than the subscription.
Here are practical triggers:
| Trigger | Why paid software may be justified |
|---|---|
| You have dedicated support headcount | Per-agent reporting and routing may matter |
| You need guaranteed internal processes | SLA, assignment, and escalation controls become important |
| You support high-value accounts | Audit trails and account context may justify higher cost |
| You operate across regions | Routing, language coverage, and permissions become harder |
| You need formal reporting | Leadership may require support metrics and exports |
| You have regulated workflows | Security, data retention, and compliance reviews may drive vendor choice |
Reverse advice: do not pay early just because a pricing page has more features. If you are still validating demand, a simple contact layer can teach you what users ask, which channels they prefer, and whether support volume is real. Upgrade after you know the workflow you are buying for.
How to calculate your own live chat software budget
Use this worksheet before choosing a tool.
Step 1: Count real responders
List everyone who must reply, not everyone who wants visibility.
| Role | Needs to reply? | Paid seat likely? |
|---|---|---|
| Founder | Sometimes | Maybe |
| Support agent | Yes | Yes |
| Engineer | Occasionally | Maybe |
| Sales | Yes, if handling inbound | Yes |
| Contractor | During coverage windows | Maybe |
Step 2: Estimate monthly conversations
Use website analytics, email volume, launch calendar, and app active users.
Create three cases:
- Normal month
- Launch or campaign month
- Incident or seasonal peak month
If pricing is usage-based, budget for the peak case, not the quiet month.
Step 3: Map required channels
Minimum channel list:
- Website widget
- Contact page or public link
- Telegram or messaging workflow
- App contact entry
If your users reach you from multiple places, the inbox matters more than the chat bubble.
Step 4: Add hidden feature requirements
Mark each as “must have now,” “later,” or “not needed.”
- Branding removal
- Full conversation history
- Mobile operator replies
- File attachments
- Offline email capture
- Multiple websites or apps
- Advanced routing
- Reporting
- Integrations
Step 5: Calculate annual cost
For per-agent tools:
agents × monthly seat price × 12
For conversation-based tools:
base plan × 12 + expected overages
For flat-rate tools:
workspace monthly price × 12 + add-ons
Then add a setup-time estimate. Even a $0 tool has some configuration time; a paid suite may have more training and process design.
Step 6: Compare against the job to be done
If the job is “let users reach us from the website, app, Telegram, Email, or one link,” Knocket may cover it at $0. If the job is “run a formal support department with SLAs and complex routing,” compare paid suites using annual cost and operational fit.
FAQ
What is the average live chat cost?
There is no single average that applies to every team. Public pricing among common tools ranges from $0 for lightweight contact layers to $20–$132 per agent per month for seat-based software, before taxes, add-ons, and enterprise contracts.
What is per-agent pricing?
Per-agent pricing charges for each person who can use the support tool. The basic formula is: agents × monthly price × 12. It is predictable, but every additional responder increases annual cost.
What is per-conversation pricing?
Per-conversation pricing charges based on customer threads, handled conversations, or similar usage units. The risk is variability: launches, incidents, or seasonal campaigns can push you into a higher tier or overage.
Is free live chat software enough for a small business?
Often, yes, if the goal is to be reachable and reply from one place. Knocket covers Web Widget, Contact Page, Mobile Widget, Telegram, Email, and a unified Inbox at $0 for the core contact experience. If you need SLAs, advanced routing, compliance controls, or complex reporting, evaluate paid software.
Do website visitors need an account to use Knocket?
No. Visitors can contact you without registering. The owner needs a Knocket account to configure entries and reply from the Inbox.
Can I add live chat without a backend?
Yes. Knocket’s Web Widget can be installed with one async script copied from the console, and it supports platforms such as WordPress, Shopify, React, and plain HTML. Mobile entry uses a WebView-based flow for iOS, Android, React Native, and Flutter.
Why do paid live chat tools become expensive?
The main reasons are seat multiplication, higher tiers for history or branding removal, added channels, usage-based conversation charges, and enterprise features. Always calculate annual cost, not only the monthly headline.
When should I choose a paid customer support suite instead of Knocket?
Choose a paid suite when you need a full support operating system: formal SLAs, advanced routing, role controls, audit logs, deep analytics, or enterprise procurement. Choose Knocket when you need a lightweight, free contact layer that helps users reach you from web, mobile, Telegram, Email, or a simple link.
If you want to start with a $0 contact layer before committing to seat-based support software, try Knocket at https://knocket.ai/.
