Free Live Chat Widget for Contractors: Turn Website Visitors Into CRM Leads

A free live chat widget gives website visitors a fast way to ask questions without calling, opening another app, or completing a long contact form.

With the DunaHub Live Chat Widget, contractors and local service businesses can add a customizable chat bubble to an existing website using one code snippet.

When a visitor sends a message, the conversation appears in the DunaHub Unified Inbox alongside WhatsApp, SMS, and email.

Your team can reply from the same inbox. While the visitor keeps the widget open, the response appears on the website in real time.

If the visitor leaves before the conversation is finished, DunaHub can still create a CRM lead and save the transcript so the business can continue the follow-up later.

The widget is included free on every DunaHub plan, with no limit on the number of conversations.

What is a live chat widget?

A live chat widget is a small message bubble displayed on a website.

Visitors click the bubble to open a conversation with the business.

A contractor may use website chat to answer questions such as:

• Do you serve my ZIP code?
• Do you offer free estimates?
• Can I send photos?
• What services do you provide?
• Are you available this week?
• Do you work on commercial properties?
• How does your pricing work?
• Can I schedule an inspection?
• Do you offer emergency service?

Instead of searching through several pages or waiting for an email response, the visitor can ask the question while still viewing the website.

A useful live chat system should do more than display messages. It should connect the conversation to the company’s sales and customer-management process.

Why should contractors add live chat to their websites?

Contractor websites receive visitors with different levels of interest.

Some are only researching. Others are ready to schedule a service but still have one question.

A visitor may hesitate because the website does not explain:

• whether their city is covered;
• whether the project is too small;
• whether an estimate is required;
• whether the company handles their property type;
• whether someone is available soon.

Without a quick contact option, that person may leave and visit another contractor’s website.

Live chat creates another conversion path.

The visitor does not need to:

• place a phone call;
• wait on hold;
• open an email app;
• search for a social media profile;
• complete a detailed form before asking a simple question.

They can start the conversation from the page they are already viewing.

What does the DunaHub Live Chat Widget do?

The DunaHub webchat adds a customizable conversation bubble to a website.

When a visitor uses it:

1. The visitor opens the chat;
2. They enter a message;
3. The conversation appears in the Unified Inbox;
4. A team member replies from DunaHub;
5. The response appears in the visitor’s widget in real time;
6. The transcript remains connected to the lead.

The widget can also collect contact information, send an automatic first response, and ask qualifying questions when no team member is online.

This connects the website conversation to the DunaHub CRM Pipeline.

Instead of leaving the conversation inside a separate chat platform, the business can manage the contact as a sales opportunity.

Is the live chat widget free?

Yes.

The DunaHub Live Chat Widget is included on every plan:

Plan	Live chat widget	Conversation limit
Free	Included	Unlimited
Starter	Included	Unlimited
Pro	Included	Unlimited

There is no separate charge for each chat conversation.

The widget includes a small Powered by DunaHub footer link by default. This attribution supports keeping the feature free across all plans.

The chat does not display banner advertisements or internal upsell popups to website visitors.

Review the current DunaHub plans and pricing for the limits that apply to other CRM features, such as total leads, jobs, proposals, invoices, users, and automations.

How does website chat enter the Unified Inbox?

Every webchat conversation is routed into the DunaHub inbox.

The team can see:

• the visitor’s name, when collected;
• the webchat channel indicator;
• the complete message transcript;
• the related lead information;
• the conversation history.

This allows website chat to appear beside other supported channels.

Channel	Customer starts the conversation through
Webchat	Website widget
WhatsApp	Connected WhatsApp number
SMS	Business text number
Email	Connected IMAP/SMTP inbox

The goal is to reduce the need to monitor several disconnected applications.

An employee can open one workspace and see which customers are waiting for a response.

What happens when you reply?

A team member opens the webchat thread inside DunaHub and writes a response.

If the visitor still has the chat open on the website, the reply appears in real time.

For example:

Visitor:

Do you provide gutter cleaning in Airdrie?

Business:

Yes, we serve Airdrie. Could you send your address and let us know whether the property is one or two stories?

The customer can continue the conversation without leaving the page.

The transcript is recorded, giving the company context if another employee needs to take over later.

What happens if the visitor closes the website?

The conversation is not automatically lost.

DunaHub can create a lead and preserve the transcript even when the visitor closes the widget before the conversation is complete.

If the business collected an email address through the intro form, the team can continue the conversation by email.

For example:

1. A visitor asks for an estimate;
2. The business does not respond before the visitor leaves;
3. The visitor’s name and email were collected;
4. The transcript is saved;
5. A lead appears in the CRM;
6. The office follows up by email.

This is one reason to consider enabling the intro form.

Without contact details, the team may understand what the anonymous visitor wanted but have no reliable way to reconnect after the person leaves.

How does the intro form work?

The optional intro form asks for the visitor’s name and email before the first message.

Those fields are added to the lead created from the conversation.

A typical flow is:

1. Visitor opens the chat;
2. Widget requests a name and email;
3. Visitor submits the information;
4. Chat opens;
5. Visitor sends the question;
6. Lead and transcript are stored together.

The intro form helps the team identify the customer and continue the conversation later.

It may be useful when:

• staff are not always available;
• the business receives after-hours traffic;
• website visitors often leave before receiving a reply;
• the sales process usually continues by email;
• the company needs a reliable contact record.

However, every required field creates additional effort for the visitor.

A business that prioritizes immediate conversation volume may choose a more open chat experience. A company that prioritizes identifiable leads may enable the form.

The right choice depends on the response process.

What is the automatic reply?

The auto-reply is a message sent when the visitor contacts the business for the first time.

It confirms that the message was received.

Example:

Thanks for contacting ClearView Cleaning. A team member will reply as soon as possible. Please tell us which service you need and your ZIP code.

Another example:

Thanks for messaging GreenLine Landscaping. We usually respond during business hours. What type of property and service are you contacting us about?

A useful auto-reply should:

• acknowledge the message;
• identify the business;
• set a reasonable expectation;
• ask for one useful piece of information;
• avoid making promises the team cannot keep.

Do not configure:

We will reply in two minutes.

unless the business can consistently meet that expectation.

A safer version is:

We usually reply within a few minutes during business hours.

What is the closing message?

The closing message is displayed when the chat conversation ends.

It can confirm what happens next.

Examples:

Thanks for contacting us. Our team will review your project details and follow up shortly.

Thanks for chatting with Bright Plumbing. We will send the available appointment options to your email.

Your estimate request has been received. We will contact you during business hours if we need additional information.

A closing message should not suggest that the job is scheduled unless an appointment was actually confirmed.

It should reflect the real next step.

What is the offline bot?

The offline bot collects information when no one is available to respond live.

Instead of showing only an unavailable message, the bot asks a configurable list of questions.

Examples include:

• What service are you interested in?
• What is the service address?
• Which city or ZIP code are you located in?
• Is the property residential or commercial?
• When do you need the service?
• Please briefly describe the issue.

The answers are used to create a lead.

The office can review the request when the team returns.

This makes the widget useful outside business hours.

The bot does not need to pretend that a person is online. It should make the situation clear.

Example:

Our team is currently offline, but we can collect a few details and follow up during business hours.

Transparent wording prevents the customer from expecting an immediate human response.

Live chat or chatbot: what is the difference?

Live chat and chatbots are related but different.

Live chat

A real employee reads and responds to the visitor.

It works best for:

• specific questions;
• project discussions;
• estimate qualification;
• availability questions;
• customer support.

Chatbot

An automated flow asks questions or provides predefined responses.

It works best for:

• collecting contact details;
• identifying the requested service;
• confirming the location;
• explaining office hours;
• gathering information while staff are offline.

The DunaHub widget combines both approaches.

The team can reply live when available, while the offline bot gathers information when no one is online.

How to enable DunaHub webchat

The feature is activated inside the dashboard.

1. Open Settings;
2. Select Webchat;
3. Turn on Enable webchat;
4. Configure the appearance and behavior;
5. Click Save.

After saving, the widget is available for installation.

The business then copies the unique script snippet and adds it to the website.

How to install the live chat widget

Inside Settings → Webchat, DunaHub provides a script linked to the organization.

The code follows this general structure:

<script
  src="https://www.dunahub.com/api/webchat/widget?org=YOUR_ORG_UUID"
  async>
</script>

The organization identifier in the real snippet connects the website chat to the correct DunaHub account.

Copy the snippet shown in your own dashboard rather than manually creating one.

Paste it once before the closing </body> tag of the website.

Because the script loads asynchronously, it is designed not to block the rest of the page while loading.

Where should the code be installed?

The exact location depends on the website platform.

The widget should normally be installed site-wide so visitors can open it from any relevant page.

Common locations include:

• global footer;
• custom code settings;
• site-wide script manager;
• application layout;
• tag or snippet management area.

Avoid adding the same snippet several times.

Duplicate installation may create unpredictable behavior or load multiple copies of the widget.

How to install the widget on WordPress

The recommended simple route uses the free Header Footer Code Manager plugin, commonly shortened to HFCM.

Step 1: Install the plugin

In the WordPress administration area:

1. Open Plugins;
2. Select Add New;
3. Search for Header Footer Code Manager;
4. Install and activate the plugin.

Step 2: Create the snippet

Open:

HFCM → Add New Snippet

Configure:

• Site Display: Site Wide;
• Location: Footer;
• Device Display: Show on all devices.

Step 3: Paste the code

Copy the DunaHub snippet from Settings → Webchat and paste it into the HFCM code field.

Step 4: Activate it

Save and activate the snippet.

The chat bubble should appear across the website.

Step 5: Test it

Open the website in a private browser window and send a test message.

Confirm that:

• the bubble appears;
• the chat opens;
• the automatic reply works;
• the conversation reaches DunaHub;
• a reply appears on the website;
• the lead is created as expected.

Can the widget be installed without a WordPress plugin?

Yes.

A developer can paste the script into the active theme or global website layout before the closing body tag.

However, editing theme files directly can create maintenance problems if a future theme update overwrites the change.

A code-management plugin or child theme is usually easier to maintain.

The correct method depends on how the WordPress website was built.

How to install webchat on Wix

Wix websites provide custom-code settings.

The general process is:

1. Open the website dashboard;
2. Find Custom Code or the site’s code settings;
3. Add a new code snippet;
4. Paste the DunaHub script;
5. Place it near the end of the body or in the footer;
6. Apply it to all pages;
7. Publish the website;
8. Test the widget.

Menu names can change as website platforms update their interfaces, but the goal is to add the script globally.

How to install webchat on Squarespace

Squarespace websites with code-injection access can add the snippet through the site settings.

The general process is:

1. Open the website settings;
2. Find Code Injection;
3. Paste the script in the footer area;
4. Save;
5. Open the public website;
6. Test a conversation.

Confirm that the selected Squarespace plan supports the required custom-code feature.

How to install webchat on Shopify

For Shopify, the snippet can be added through the theme’s custom code or footer configuration.

A developer may place the script in the main theme layout before </body>.

After saving:

• review the storefront;
• check product and service pages;
• test mobile display;
• confirm the widget does not cover important checkout controls.

A service business using Shopify primarily for products should decide whether chat should appear during checkout or only on informational pages.

How to install webchat on a static website

For a hand-built HTML website, open the global page template and paste the snippet before:

</body>

If each page has separate HTML, the code must appear on every page where the chat should be available.

A global template or shared include is preferable because it keeps the installation consistent.

How to install webchat in React or Next.js

React and Next.js applications should load the script through the application’s existing script strategy.

For a Next.js project, the script can be added with the framework’s <Script /> component and an afterInteractive strategy.

A simplified example is:

import Script from "next/script";

export default function RootLayout({ children }) {
  return (
    <html lang="en">
      <body>
        {children}

        <Script
          src="https://www.dunahub.com/api/webchat/widget?org=YOUR_ORG_UUID"
          strategy="afterInteractive"
        />
      </body>
    </html>
  );
}

Use the real organization-specific source provided in the DunaHub dashboard.

Place the component in a shared layout when the widget should appear across the entire application.

How can the widget be customized?

Customization is managed under:

Settings → Webchat

The available options include:

• subtitle;
• auto-reply;
• closing message;
• brand color;
• intro form;
• offline bot.

These settings allow the business to match the chat experience to its brand and customer process without rebuilding the widget.

How should the subtitle be written?

The subtitle appears below the business name in the chat header.

It should communicate availability or set an expectation.

Examples:

• We usually reply within minutes;
• Ask us about your project;
• Get help with scheduling;
• Request service information;
• Online during business hours;
• Tell us what service you need.

Keep it short.

The subtitle is not the place for a long company description or promotional paragraph.

How should the brand color be selected?

The selected color is applied to elements such as:

• chat bubble;
• header;
• primary button;
• accents.

Choose a color that:

• matches the company’s visual identity;
• is easy to see against the website background;
• provides enough contrast for readable text;
• does not blend into other fixed buttons.

After selecting a color, test the widget on:

• desktop;
• mobile;
• light website sections;
• dark website sections.

A brand color may look good in a logo but be difficult to use as a button background.

Can live chat create CRM leads automatically?

Yes.

The widget can create a lead from the conversation.

Contact details collected through the intro form are attached to the lead.

Information gathered by the offline bot can also be used when creating the record.

The lead then becomes part of the visual CRM pipeline.

A typical process is:

1. Visitor opens chat;
2. Name and email are collected;
3. Visitor asks about a service;
4. Conversation enters the inbox;
5. Lead is created;
6. Team qualifies the request;
7. Lead moves through the pipeline;
8. Proposal or booking is created.

This prevents website conversations from remaining isolated from the sales process.

How should chat leads move through the pipeline?

A practical pipeline may use stages such as:

Stage	Chat-related action
New Lead	Visitor sends the first message
Contacted	Team replies
Information Needed	Photos, address, or details are requested
Estimate Scheduled	Inspection or consultation is booked
Proposal Sent	Pricing is delivered
Follow-Up	Customer has not decided
Ready to Book	Customer agrees to proceed
Booked	Job is scheduled
Lost	Customer does not continue

The exact stages should reflect how the company sells.

Do not create a separate pipeline stage for every possible chat question.

The chat is the source of the lead. The stages should represent the commercial progress.

How does live chat work with public forms?

Live chat and public lead forms serve different customer preferences.

Live chat	Public form
Conversational	Structured
Useful for immediate questions	Useful for detailed requests
Can be answered in real time	Can be reviewed later
Information develops naturally	Fields are defined in advance
Good for uncertain visitors	Good for estimate requests
Can create a lead	Creates a lead automatically

A contractor website can use both.

For example:

• Chat with us for questions;
• Request an estimate for detailed project submissions.

The visitor chooses the path that feels easier.

How does live chat work with online booking?

Some visitors do not need a conversation. They are ready to select an appointment.

The DunaHub Online Booking page lets customers choose a service and available time.

Live chat can help visitors decide which service to book.

Example:

Visitor:

Should I book a repair visit or a full inspection?

Business:

Please select the diagnostic visit. Our technician will inspect the system and explain the next step.

The team can then share the booking link inside the chat.

This creates a useful sequence:

Question → Recommendation → Booking → CRM lead → Scheduled job

How does live chat work with proposals?

A visitor may begin by asking a general question and later become a qualified opportunity.

The team can:

1. Collect the service information;
2. Request the address or photos;
3. Create a CRM lead;
4. Prepare a DunaHub Visual Proposal;
5. Send the proposal;
6. Follow up;
7. Convert approved work into a job.

The original chat remains part of the customer context.

That helps the estimator understand what was discussed before preparing the scope.

Can webchat conversions be tracked?

Yes.

The widget fires events compatible with:

• Google Tag Manager;
• Google Analytics 4;
• Meta Pixel.

This allows the business to measure chat interactions in a similar way to:

• form submissions;
• phone-button clicks;
• booking actions.

The relevant tracking IDs are configured under:

Settings → Organization

After the IDs are set, the widget events can flow through the connected tracking setup.

The exact reporting and conversion configuration still depends on how the business has organized GTM, GA4, Meta, and advertising accounts.

A marketing specialist should test the events before relying on them for campaign optimization.

Why track live chat conversions?

Without tracking, the company may know that website traffic increased but not whether visitors opened the chat.

Chat analytics can help answer:

• Which pages generate conversations?
• Which advertising campaigns produce chats?
• How many visitors start a conversation?
• Which services receive the most questions?
• Do chat leads become proposals?
• Do chat leads become booked jobs?
• Which sources produce qualified conversations?

A chat opening is not automatically a sale.

The useful measurement path is:

Chat started → Lead created → Qualified → Proposal → Booked job → Revenue

This requires both analytics and accurate CRM updates.

What pages should display live chat?

For most local service businesses, the widget can appear site-wide.

Important pages include:

• homepage;
• service pages;
• pricing pages;
• contact page;
• landing pages;
• booking pages;
• frequently asked questions;
• location pages.

However, the company should test whether the bubble covers important page elements.

On mobile, pay attention to:

• sticky call buttons;
• cookie banners;
• booking buttons;
• navigation controls;
• checkout buttons;
• accessibility tools.

The chat should remain visible without preventing customers from using the website.

Should the widget appear immediately?

A persistent bubble can remain available without forcing the window to open.

This gives the visitor control.

Avoid aggressive behavior that interrupts the person before they understand the page.

The chat should support the website experience rather than block it.

A clear bubble and useful subtitle are often enough to signal that help is available.

How should contractors answer live chat?

A good response should be:

• clear;
• relevant;
• short enough to read;
• connected to the customer’s question;
• designed to move the conversation forward.

Instead of:

How can I help?

when the customer already explained the problem, respond to the specific request.

Example:

Yes, we provide pressure washing for residential driveways in Tampa. Could you send the property address and an approximate driveway size?

This confirms the service and asks for the next useful detail.

What information should be collected?

The right questions depend on the business.

Common information includes:

• name;
• email;
• phone number;
• service address;
• city or ZIP code;
• service type;
• property type;
• urgency;
• project description;
• preferred appointment period.

Do not turn the chat into a long interrogation.

Collect enough information to identify the next step.

For a gutter contractor, that may be:

1. Address;
2. Property height;
3. Requested service;
4. Photos, if possible.

For a cleaning company:

1. Property type;
2. Number of rooms;
3. Service frequency;
4. Location.

Live chat scripts for contractors

Initial reply

Hi! Thanks for contacting {company.name}. What service do you need, and where is the property located?

Estimate request

We can help with that. Could you send the service address and a short description of the project?

Service-area question

Yes, we serve that area. Please share your ZIP code so we can confirm availability and travel details.

Request for photos

Photos will help us understand the scope. Please send clear images of the area, including one wider view and one close-up.

Booking direction

This service can be booked online. Here is our scheduling page: [booking link]

Custom-project direction

This project needs an estimate before scheduling. Please share your address and project details, and our team will review them.

After-hours auto-reply

Thanks for contacting us. Our team is currently offline. Please leave your name, email, service address, and the type of work you need. We will follow up during business hours.

Closing message

Thanks for the details. Our estimator will review the request and contact you by email with the next step.

How fast should a business respond?

Live chat creates an expectation of a relatively fast conversation.

A business should only describe itself as available when someone can reasonably monitor the inbox.

A practical process can include:

1. Assigning inbox responsibility;
2. Using an auto-reply immediately;
3. Setting honest availability language;
4. Enabling the offline bot;
5. Reviewing unanswered chats;
6. Continuing by email when contact details exist.

Do not allow every employee to assume someone else is monitoring the chat.

Define who is responsible during each period.

How can a small team manage live chat?

A small team does not need a full-time chat department.

It can use a simple operating rule:

During office hours

One person monitors new conversations and claims or answers them.

During field work

The auto-reply explains that the team may need time to respond.

After hours

The offline bot collects the service and contact details.

Next business day

An employee reviews unanswered chats and follows up.

The objective is consistent handling, not pretending that someone is online 24 hours a day.

Can several employees answer website chats?

The conversations enter the shared DunaHub inbox, allowing the company to manage them alongside other customer channels.

Multiple team members can have access according to the organization’s user limits and internal process.

The business should still define rules to prevent:

• duplicate replies;
• conflicting information;
• two employees handling the same customer;
• unanswered conversations.

A shared inbox works best when responsibility is clear.

What should the offline bot ask?

Keep the question list short.

A useful contractor flow could ask:

1. What service do you need?
2. What city or ZIP code is the property in?
3. Is the property residential or commercial?
4. Please describe the issue.
5. What is the best email for follow-up?

Only ask questions that influence qualification or the next action.

Do not request sensitive financial or identity information through a general website chat.

What privacy considerations apply?

A website chat collects customer communication and may collect names, emails, service addresses, or project information.

The business should:

• explain how contact information will be used;
• maintain an accurate privacy policy;
• avoid collecting unnecessary sensitive data;
• restrict CRM access to authorized users;
• remove access for former employees;
• follow the privacy and communication rules that apply to its market.

Do not treat an estimate conversation as unlimited consent for unrelated promotional messages.

The customer’s information should primarily be used to respond to the request unless broader permission was obtained.

What security precautions should be followed?

The widget snippet contains the organization identifier needed to route conversations.

Use the snippet provided in the dashboard and avoid altering it without a reason.

Also:

• install it only on authorized websites;
• keep DunaHub user accounts secure;
• use individual team logins;
• remove former users;
• review unusual chat activity;
• avoid sharing internal notes with visitors;
• confirm customer identity before discussing sensitive account information.

A website chat is appropriate for general service and sales communication. It should not be used to expose confidential information without appropriate verification.

Common live chat mistakes

Installing the snippet more than once

Use one site-wide installation.

Not testing the widget

Send test messages from both desktop and mobile.

Promising an unrealistic reply time

Set expectations the team can meet.

Leaving chats without an owner

Define who monitors the inbox.

Asking too many questions

Collect only what is necessary.

Hiding that the team is offline

Use transparent offline messaging.

Not collecting contact information

Enable the intro form or offline questions when later follow-up is important.

Using generic answers

Respond to the visitor’s actual question.

Treating every chat as qualified

Confirm location, service, timing, and need.

Failing to move the lead through the CRM

The chat should become part of the sales process.

Ignoring analytics

Track whether conversations produce real opportunities.

Allowing the bubble to cover mobile buttons

Test the placement on smaller screens.

Sharing links that do not work

Test proposal, booking, and service links before using them in chat.

Installation and launch checklist

Before publishing the widget, confirm:

• Webchat is enabled;
• The correct organization snippet was copied;
• The code is installed only once;
• The widget appears on desktop;
• The widget appears on mobile;
• The brand color is readable;
• The subtitle is accurate;
• The auto-reply is configured;
• The closing message explains the next step;
• The intro form is enabled when needed;
• Offline questions are short and useful;
• A test conversation reaches the inbox;
• A reply appears in real time;
• A lead is created;
• The transcript is saved;
• GA4, GTM, or Meta events are tested when used;
• The team knows who will monitor new conversations;
• The privacy policy reflects the communication process.

Example: gutter contractor

A homeowner visits a gutter installation page and opens the chat.

Customer:

Do I need 5-inch or 6-inch gutters?

The contractor replies:

The best size depends on the roof area and water volume. Please send your address and a few exterior photos, and we can review the property.

The visitor provides an email and address.

DunaHub creates the lead and saves the conversation.

The contractor later prepares a proposal and moves the opportunity through the pipeline.

Example: pressure washing company

A customer visits a driveway-cleaning page after business hours.

The offline bot asks:

• Which surface needs cleaning?
• What is the property ZIP code?
• Approximately how large is the area?
• What email should we use for follow-up?

The answers become a CRM lead.

The company responds the next morning with the information needed to prepare pricing.

Example: HVAC service company

A website visitor asks:

My AC is running but not cooling. Do I need a repair appointment?

The team replies that a diagnostic visit is the appropriate service and shares the online booking link.

The customer books an available appointment.

The conversation, lead, and job remain connected in DunaHub.

Example: landscaping company

A property manager visits the commercial landscaping page and asks whether recurring maintenance is available.

The office collects:

• property address;
• lot type;
• desired frequency;
• contact email.

The lead moves to Estimate Scheduled, and the company arranges a site visit.

Example: cleaning company

A residential customer asks about recurring cleaning prices.

The team explains that pricing depends on property size and asks for:

• number of bedrooms;
• number of bathrooms;
• city;
• preferred frequency.

The customer receives a proposal after the chat.

The original conversation remains available for reference.

Live chat versus phone calls

Live chat does not replace phone calls.

The channels serve different preferences.

Live chat	Phone call
Quiet and discreet	Direct verbal conversation
Visitor can remain on the website	Customer leaves the page experience
Transcript is saved	Details may need manual notes
Useful for short questions	Useful for complex discussion
Can be used after hours with a bot	Usually depends on availability
Can collect written details	May resolve urgent needs faster

A business can offer both.

The website visitor chooses the most comfortable path.

Live chat versus SMS

SMS begins through a phone number, while webchat begins on the website.

A visitor may prefer webchat before sharing a phone number.

Later, the business may move the conversation to SMS when:

• the customer provides permission and a valid number;
• appointment updates are needed;
• the visitor has left the website;
• the service process continues over several days.

DunaHub keeps supported channels inside the same inbox so the relationship does not need to be reconstructed each time.

Live chat versus WhatsApp

WhatsApp requires the visitor to open the app or web service and contact the connected business number.

Live chat keeps the conversation on the contractor’s website.

A business serving markets where WhatsApp is common can offer both.

Webchat may be better for visitors who:

• do not use WhatsApp;
• are browsing on a work computer;
• do not want to open another app;
• only have a quick question.

WhatsApp may be better for:

• sending ongoing updates;
• sharing photos;
• returning to the conversation later;
• customers already communicating through that channel.

How does live chat support paid advertising?

An advertising visitor may have a specific question that prevents them from submitting a form.

Live chat allows the business to address that concern while the person remains on the landing page.

Examples include:

• Do you serve my location?
• Is the estimate free?
• Can you do the work this week?
• Do you offer this service for commercial buildings?
• What information do you need?

Because the widget supports analytics events, chat starts can also become part of campaign measurement.

The business should still evaluate whether chats become qualified leads and jobs.

A large number of conversations without sales may indicate:

• unclear ad targeting;
• an incomplete landing page;
• pricing confusion;
• service-area problems;
• weak qualification;
• slow responses.

How can chat data improve the website?

Repeated visitor questions reveal where the website may be unclear.

If many people ask:

Do you serve my city?

the website may need a clearer service-area section.

If visitors repeatedly ask about pricing, the company may need to explain its estimate process.

If customers ask which service to book, the service descriptions may need improvement.

Reviewing transcripts can help identify:

• missing information;
• confusing pages;
• customer objections;
• new content topics;
• frequently requested services.

The chat is not only a communication channel. It is also a source of customer-language insights.

How should live chat performance be reviewed?

A monthly review can examine:

• total conversations;
• identified versus anonymous visitors;
• after-hours conversations;
• average response process;
• qualified leads;
• proposals created;
• jobs booked;
• common questions;
• lost opportunities;
• traffic source;
• service-page performance.

Do not measure success only by the number of chats.

The most useful question is:

How many relevant conversations became real sales opportunities?

Summary: why use the DunaHub Live Chat Widget?

The DunaHub Live Chat Widget adds real-time website messaging to a contractor’s customer-management system.

It includes:

• one-snippet installation;
• WordPress and other platform support;
• customizable subtitle;
• automatic first response;
• closing message;
• brand colors;
• optional name and email form;
• offline qualification bot;
• Unified Inbox delivery;
• real-time replies;
• saved transcripts;
• automatic lead creation;
• GTM, GA4, and Meta Pixel event compatibility;
• unlimited conversations on every plan.

The connected workflow is:

Website visitor → Live chat → Unified Inbox → CRM lead → Follow-up → Proposal → Job

Instead of allowing website questions to disappear after the visitor leaves, the company can preserve the conversation and move the opportunity into its sales process.

Frequently Asked Questions

What is a live chat widget?

It is a message bubble embedded on a website that allows visitors to talk with the business.

Is the DunaHub Live Chat Widget free?

Yes. It is included on Free, Starter, and Pro.

Is there a conversation limit?

No. The documentation states that conversations are unlimited on every plan.

Can I install it on WordPress?

Yes. The recommended simple method uses the Header Footer Code Manager plugin.

Can it be installed on Wix, Shopify, or Squarespace?

Yes. Add the script through the platform’s custom-code or footer settings.

Can it be installed on React or Next.js?

Yes. The script can be loaded through the application’s existing script strategy, including Next.js <Script /> with afterInteractive.

Where should the snippet be placed?

Place it once before the closing </body> tag or through the website’s global footer or custom-code settings.

Will the script block the website from loading?

The widget script loads asynchronously and is designed not to block the rest of the page while loading.

Where do messages appear?

Conversations appear in the DunaHub Unified Inbox.

Can the team reply in real time?

Yes. The visitor sees the reply while the widget remains open.

What happens if the visitor closes the widget?

DunaHub saves the transcript and can create a lead. When contact information is available, the business can follow up later.

Can the widget collect a name and email?

Yes. Enable the optional intro form.

Does it work when nobody is online?

Yes. The offline bot can ask questions and create a lead from the answers.

Can I change the widget color?

Yes. The brand color can be configured under Settings → Webchat.

Can I customize the automatic message?

Yes. Configure the auto-reply and closing message in the Webchat settings.

Does the widget connect to the CRM?

Yes. Conversations can create leads and remain connected to the customer record.

Can chat actions be tracked in Google Analytics?

Yes. The widget fires events compatible with Google Tag Manager, GA4, and Meta Pixel.

Does the widget show DunaHub branding?

Yes. A small “Powered by DunaHub” footer is displayed by default.

Are advertisements displayed inside the chat?

No. The documentation states that the widget does not show banner ads or upsell popups.

Add free live chat to your contractor website

Want to answer website questions, capture after-hours visitors, and send every conversation into your CRM?

Create your free DunaHub account, enable Webchat, copy your installation snippet, and start receiving unlimited website conversations in your Unified Inbox.