How Much Does It Cost to Add Live Chat to a Business Website?

Adding live chat to a business website can be inexpensive when it means installing a vendor widget and paying a monthly subscription. It becomes a larger project when the business needs custom conversation routing, staff availability, transcripts, CRM records, file handling, automation, or a private customer experience.

Three common chat scopes

Vendor widget and configuration

A vendor widget may require 5 to 15 hours for installation, branding, basic routing, business hours, notifications, testing, and analytics. The recurring provider fee is separate. Confirm whether the widget affects performance, consent, accessibility, and data ownership.

Chat connected to business workflows

Connecting conversations to a CRM, lead queue, appointment system, or support process may require 20 to 60 hours. The work includes field mapping, routing, transcripts, identity matching, status changes, handoff, retries, and tests.

Custom chat or portal messaging

A custom chat experience may include authenticated customers, staff presence, private threads, attachments, notifications, search, audit history, moderation, and mobile behavior. Planning for 80 to 200 or more hours is reasonable depending on the scope.

At Vertinus's published rate of $49.99 per hour, those implementation ranges are roughly $250 to $10,000 before subscriptions, messaging costs, storage, and taxes.

The staffing cost can exceed the build cost

Chat creates a promise to respond. Decide who monitors it, which hours are covered, how overflow is handled, what happens after hours, and when a conversation becomes a phone call or form request.

An unattended chat bubble can reduce trust. If the business cannot provide live coverage, a well-designed contact form, callback request, or honest asynchronous message may be better.

Define the conversation types

Separate sales, service, support, billing, and general questions when they have different owners or privacy needs. Ask only the fields needed to route and start the conversation. Collect more context after a person joins if that creates less friction.

Plan routing and handoff

Decide how a chat moves from bot or front desk to a specialist, how a customer requests a call, and how the transcript reaches the person who continues the work. Preserve page context, source, consent, and the original message where appropriate.

The lead routing system guide explains fallback queues and response deadlines. Chat should follow the same ownership rules as forms and calls.

Use automation carefully

Automated answers can handle hours, location, basic service information, and routing. They should make it clear when a human is not responding. Avoid generating confident answers about pricing, availability, policies, or personal records when the system cannot verify them.

Consider privacy and accessibility

Review transcript retention, access, recordings, personal data, attachments, vendor processing, and deletion. Give users a keyboard-accessible chat control, labels, readable contrast, and a non-chat way to get help.

Measure conversations, not bubble clicks

Track chats started, chats answered, wait time, handoff rate, form or appointment completion, qualified leads, resolution, opt-outs, and staff workload. A high chat-start rate with no answer is a service problem, not a conversion win.

Choose the smallest useful implementation

Start with a vendor tool or asynchronous request if the business needs to test demand. Add CRM integration and routing after ownership works. Consider custom chat only when the customer or staff workflow cannot be supported by a product without unacceptable compromises.