Take a hypothetical kitchen fitter who describes their work everywhere as "bespoke cabinetry solutions". Their visitors, meanwhile, keep typing "can you just replace the doors" and "do you do worktops only". Not one visitor has ever used the word bespoke. The website is written in the owner's language, and the customers are speaking a different one.
This is the most useful thing a chat log gives you, and most businesses never look at it for this. Transcripts are treated as a support record. They are also the cheapest voice of customer copywriting research you will ever get, because nobody filled in a survey. People just typed what they wanted to know.
If you want to improve website copy from customer questions, the raw material is already sitting in your inbox.
What transcripts reveal that analytics cannot
Page analytics tell you that people left. They do not tell you what they were thinking when they did. A chat conversation often does, because the visitor stops and asks about the thing that was bothering them.
Look for four kinds of signal:
- Vocabulary gaps. The customer says "boiler service" and your page says "heating system maintenance". Search engines and humans both prefer the customer's words.
- Buried answers. The page does mention your cancellation terms, but in paragraph nine. If people keep asking, the answer is effectively missing.
- Missing answers. Questions about parking, deposits, turnaround time or whether you work with renters, where the page is simply silent.
- Doubts rather than questions. "Is it worth it for a small flat?" is not a request for facts. It is hesitation, and the page is not addressing it.
An assistant that records knowledge gaps makes the last two much easier to spot, because the unanswered questions get listed for you instead of hiding in hundreds of transcripts.
A process for mining the transcripts
You do not need special software for this. A spreadsheet and an hour will do.
- Export or scroll through the last 50 to 100 conversations that started on one page, ideally your most visited service page.
- Copy each visitor's first question into a spreadsheet column, exactly as typed.
- Add a second column with a short label for the topic: price, timing, area, suitability, process, trust.
- Count the labels. Anything appearing more than a handful of times is a copy problem, not a chat problem.
- For each frequent topic, highlight the words customers used. Circle any word that appears repeatedly and does not appear on your page.
- Check where on the page, if anywhere, the topic is answered. Note the section and how far down it is.
- Pull out any questions the assistant could not answer. These go straight to the top of your rewrite list.
The last step matters. If you use SpideyChat, those show up as unanswered questions in analytics, which saves you reading every transcript to find them.
Rewriting the page, with a before and after
Here is an invented example for a residential cleaning company, based on the kinds of questions a transcript review tends to surface.
| What customers asked | What the page said | What the rewrite says |
|---|---|---|
| "Do I need to be home?" | Nothing | "Most clients are out. You can leave a key in a lockbox or with a neighbour, and we confirm when we arrive and leave." |
| "How much for a 2 bed flat?" | "Competitive pricing tailored to your needs" | "A regular clean for a two-bedroom flat usually takes around three hours. See the price table below." |
| "Do you bring your own stuff?" | "Fully equipped professional team" | "We bring all products and equipment. Tell us if you prefer we use yours." |
| "What if I'm not happy?" | Mentioned in the terms page | "If something is missed, tell us within 24 hours and we come back to fix it at no charge." |
Notice what changed. The rewrite uses the customer's words (home, flat, stuff, not happy). It replaces vague reassurance with a specific answer. And it moves those answers onto the page itself, near the top, instead of making people hunt.
The prices and policies in the table are placeholders. Only publish what you actually offer.
What not to do with the findings
Transcripts can mislead you if you read them carelessly.
A single loud conversation is not a pattern. One visitor complaining about your colour scheme is not a reason to redesign. Look for repetition.
Do not turn every question into an FAQ entry. A page with forty FAQs is a page nobody reads. If a question is central to the decision, it belongs in the main copy. If it is occasional, an FAQ is fine. The AI FAQ generator can help draft entries once you have decided which ones earn a place.
Do not quote customers publicly. Use their language, but never paste a transcript line onto your site or into an ad. It is a privacy problem and it breaks the trust the chat was built on.
And watch out for questions the page should never answer. If people keep asking your assistant for medical or legal advice, the fix is a clear statement of what you do and do not provide, not a new paragraph pretending to advise.
Keep the page and the assistant saying the same thing
Once you rewrite a page, your assistant's knowledge is out of date. If it was trained by crawling the old page, it may keep quoting "competitive pricing tailored to your needs" while the new page gives real ranges. Customers notice contradictions quickly.
After publishing, re-crawl the page or update the relevant Q&A pairs. Then ask the assistant the same questions from your spreadsheet and check that the answers match the new copy. The guide to turning unanswered questions into website pages covers this loop in more detail, and the features page lists the ways to teach an assistant.
Your first rewrite
Pick the one page that gets the most chat traffic. Spend an hour building the spreadsheet from its last 50 conversations. Choose the three most repeated topics, rewrite those sections in customers' own words, and move them higher up the page.
Then leave it alone for a month. Count how often those same questions come up in chat afterwards. If they drop, the page is doing its job and you can move on to the next one. If they do not, the answer is still unclear, and you rewrite again.