Website chat and chatbot lead capture · Sales
Catch the visitor who reads three pages, types nothing and leaves.
Most people who visit your site will never fill in a form. They read the price page, look at two photos of past work and close the tab. Typing one line into a chat box is easier than filling six fields, so a few of them will do that instead.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

In one paragraph
Website chat and chatbot lead capture is a chat window that asks a visitor two or three questions about the job, then hands the thread to a person. GullySales writes the questions, sets the rule for who picks a chat up, and files every conversation in your CRM with the page it started on.
Chat is a capture point, not a salesman. It finds out what the visitor came for, then puts the whole thread in front of whoever is on duty, with the page they were reading attached. Nothing sits in a widget dashboard that nobody opens.
A bot also answers at midnight, which matters for some trades and not for others. If a customer is locked out of the house at 11 pm, they want a number to ring at the top of the page.
Who it is for
This is written for you if these sound familiar.
- A few hundred visitors a month, and a contact form that brings in two enquiries
- Buyers who will type one line on WhatsApp but abandon a six-field form
- Someone at a desk in working hours who can pick up a chat within a few minutes
- Work priced after a site visit, where the first job is finding out what the visit involves
- Visitors who arrive at 10 pm comparing you with two other suppliers
Not for
It is not the right fit if.
- An emergency trade where the customer wants a voice. A locksmith or an ambulance service puts the phone number in front of them, not a chat window
- Nobody can pick up the handover for a day, so the chat collects names that go cold
- Ten visitors a day. Fix that first, because a chat window on an empty site has nothing to catch
The problem
Does this sound like your business?
What owners tell us on the first call, in their words.
“People come to the site and nothing comes of it”
Analytics shows four hundred visitors. The form shows three enquiries. The rest had a question and nobody was there to answer it.
“The chat we switched on just collects names”
A widget greets everyone and asks for a name and number. Nobody reads the transcripts, and the numbers get called two days later.
“The bot answers everything except what they asked”
A visitor asks whether you service a Bosch pump and gets a menu of four buttons. He leaves and calls the next result.
“Chats live in the widget and nowhere else”
Last month's conversations sit in a dashboard nobody logs into. When the same buyer rings, your team starts from zero.
What we do
Everything that is included.
Each deliverable, and what it gets you. Nothing here is an extra.
Chat on the pages where people hesitate
The widget opens on the price page and the service pages, and stays quiet on the blog.
The qualifying questions
Two or three questions written for what you sell: what needs doing, where, and how soon. Enough to tell a buyer from a student doing a project.
Answers to what people actually ask
Written replies for the ten questions your team types out again and again: hours, the areas you cover, whether you quote a rough price on chat.
The handover rule, day and night
Who the chat goes to, and how fast. At 11 pm the window promises a callback time your team can keep, instead of an instant reply nobody is awake to give.
A CRM record for every chat
Each conversation saved against a lead with the page it started on, so the person who rings back already has the history.
Chat traced to orders
Each conversation tagged with its page and campaign, so the report can say which chats became orders, not how many chats there were.
How the result is measured
- Chats started, by page
- Chats that produced a contact number
- Time from a chat starting to a person joining it
- Enquiries from chat that became orders
- Questions the bot could not answer
Recorded as a baseline before work starts, so every later report has an honest comparison.
How it works
How the work runs
The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.
- 1
Read what the site already does
We record how many visitors arrive, which pages they read before enquiring, and what the form produces today. That is the baseline.
- 2
Write the questions and the answers
Drafted from your own enquiry history, then checked with whoever answers the phone. They know what buyers really ask.
- 3
Agree the handover and the hours
Who picks up a chat, within how long, and what the window says when the office is shut.
- 4
Install, connect and test
The widget goes on the chosen pages and connects to your CRM. We test it on a phone, on mobile data, before it goes live.
- 5
Read the transcripts
At the cadence agreed in writing after we have read your brief and spoken to you, we go through what people asked, fix the answers that missed, and report enquiries and orders from chat against the baseline.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales process design, at stage 1, prospecting and lead generation. The audit comes before it, and sales management keeps it running.
Step 1
Sales audit
Find where deals are being lost and what to fix first.
Start here if you cannot say where orders are lost.
Step 2 · you are here
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3
Sales management
A target, a review routine and someone who owns the number.
Start here if the team has targets and no routine.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
Will a chat window annoy our visitors?
Do we need a bot or a person on chat?
What if nobody on our team can answer a chat?
Will this work for an emergency service?
How is this priced?
How long is the contract?
How soon will we see results?
Who will actually do the work?
What do you need from us?
What if we are not happy with the work?
By industry
Website chat and chatbot lead capture, written for your industry.
Related services
Often bought with this, or instead of it.
Learn the method
The teaching pages behind this work. Read them to judge the work, or to do the parts you want to do yourself.
Read before you buy
- A chatbot on your website: what to ask visitors and when to hand over to a personThe three questions a website chatbot should ask, the phone number it must collect, and the hand-over rule that stops a visitor talking to a bot that cannot help.
- Chatbot or a person on WhatsApp: who should answer the first messageA rule for deciding which WhatsApp messages a bot should answer and which need a person at once, with a handover point written down before you switch anything on.
- How an online seller should handle customer questions before purchaseTreat each pre-sale question on size, compatibility, delivery or authenticity as an enquiry: log it, answer it from a checked answer bank while the buyer is still shopping, then fix the page.
Your next practical step
Tell us what you are trying to grow, and we will read it before we call.
Eight short steps, mostly taps. Skip anything you would rather answer on the call.