A form takes the message and leaves the visitor waiting. Chat answers while they are still on the page, records what matters and hands you the request.
7 days, 20 answered calls, no card
On several fence and deck company sites, a “free estimate” button is the only door shown — no phone number on the home page. Among electricians, a free quote form turns up on nearly every site reviewed. One masonry firm even spells out its buying path: form first, then a call from an advisor, then an on-site assessment.
A form is a one-way drop box. It takes a message; it does not answer the question that decides what happens next — do you cover my area, how long does it take, can it be fixed without opening a wall. Chat is a conversation instead. Your receptionist answers from your instructions, records the address and the nature of the work, offers a slot in your calendar when your rules allow it, starts quote follow-up if you chose it, and files the request in your app with what she understood.
They ask whether you cover their area, what an inspection includes, when you could come by. Your receptionist answers from your instructions, qualifies and passes it to you. Those replies draw on the monthly customer reply allowance, shared with whatever other channels you added.
You ask for a summary, tell her to call someone back, fix a coverage rule. That exchange is yours: it has its own meter and does not draw on what your customers use.
One line to place on your site, and the instructions you already gave for the phone.
Website chat and text messages belong to one module: switching both on is a single addition, not two.
A visitor’s first question is almost invariably coverage. The receptionist answers from the town list you gave her; if it falls outside, she says so right away instead of leaving someone waiting for a callback that will not come.
The visitor describes the job. She asks for the address, the access, the deadline, then offers a visit window under your rules. With a form alone, that request would have sat in an inbox until evening.
The visitor closes the tab partway through. If they left a number and agreed to be reached, the rest goes out by text, and the thread stays attached to one customer file.
Conversing does not quietly grant the right to price, book or collect: those acts belong to the modules that carry them, and you choose them separately.
What a visitor knows before writing, and what happens when a conversation runs past its frame.
This channel is added through a module that also carries other ways of answering. Its page says which. The help explains how messages arrive and what is recorded from them.
Each channel is added separately and none is on by default. Chat and text share one module; Instagram and Messenger share another; WhatsApp and the email inbox each have their own.
No. It is one line to place in the pages, like a measurement tag. If you do not touch the code yourself, whoever looks after your site does it in a few minutes. Nothing else changes: your pages, your forms and your phone number stay where they are.
Not necessarily, and the two go together well. A form stays useful for a detailed request, with files and a drawing. Chat answers the question that decides what happens next — coverage, timing, the order of magnitude of the job — while the visitor is still on the page, instead of sending them off to wait for a callback.
The window states from the first line that an automated receptionist is replying in your business name. The details requested are the ones the request needs, and the reason is stated. A visitor who writes gains no owner rights: nobody reads a customer file by typing in the window.
The thread stays attached to their conversation. If they left a number and agreed to be reached, the rest can go out by text, and the exchange resumes where it stopped. If they come back to the site, they find what was said rather than starting over.
It offers a slot in your calendar when your rules allow it and the calendar is connected. Conversing does not quietly grant the right to price, book or collect: those acts belong to the modules that carry them, and you choose them separately.
It consumes one reply on the monthly customer reply allowance, shared across the conversation channels you added. It crosses no carrier, so it carries no transport charge the way a text does. Calls keep their own meter.
No, one. They belong to the same conversation module, which covers one chat window and one messaging number for the same site. Instagram and Messenger form another set; WhatsApp and the email inbox each have their own.
Website chat
