Website chat for service businesses: setup and lead capture
Published 27 September 2026 · Nesdzo team
A chat button can catch a visitor’s question at the moment they are comparing options. The value comes from what happens after the click: a relevant answer, a sensible next question and a lead your team can follow up.
Decide what website chat should accomplish
Pick a small number of real outcomes: collect a consultation request, understand a repair, arrange a viewing enquiry or answer an opening-hours question. Give the assistant the facts it needs for those outcomes. A generic greeting with no approved knowledge cannot reliably help a customer choose the next step.
Write down when a person must take over. Questions about safety, a dispute, a missing price or an appointment that needs confirmation should have an explicit route to staff.
Prepare the assistant before installation
In NEmployee, add products and services with approved prices and optional photos in AI & knowledge. Describe what each photo shows so the assistant can use that description without guessing from the image. Add FAQs and your booking policy there too. Use Conversation guidance for the tone and next-step approach your business prefers. Then use the built-in assistant test to send realistic questions without creating a customer lead.
The free workspace includes eight test messages per month. Check a normal lead, an unclear question, a refusal and a spam-like message. Improve your knowledge where the answer is incomplete.
Install on the exact website domain
When your offer includes website chat, open Quick start and add the HTTPS origins that may show the widget. Save the settings, then copy the generated script tag into your site before the closing body tag. NEmployee checks the origin against your list, so a lookalike domain cannot use the same public site key.
The site key in that script is intentionally public. Keep REST API bearer keys on a server or trusted automation tool; never paste one into website JavaScript. If you rotate the site key, replace the old snippet on your site.
Give your website developer or AI clear instructions
Quick start has a separate copy button for an AI coding assistant. It contains the exact script, approved domain and security boundaries. Use that brief if someone else manages your website; they should add the widget, then send a test enquiry from the allowed domain.
Verify the message appears in the NEmployee inbox and that staff can take over. Test on mobile as well as desktop, including pages where cookie banners or sticky buttons may overlap the chat launcher.
Judge quality by the handover
A useful lead record should say what the visitor asked, which service they meant and what action is still needed. Review missed or confusing questions and add approved answers. Do not judge the widget only by the number of chats opened.
Website chat is one part of the customer journey. Link to the same booking or contact route your team uses so the next step stays consistent with your real capacity and confirmation process.
Install a small widget only after the assistant knows your business, then measure whether its conversations leave staff with a clear next action.