Prepare your content. Ask the awkward questions.
Check where the answer takes someone.
Fictional examples. Use the method with your own facts.
We visit Northbridge and Westfield. The team needs to confirm whether there is a slot today. Send your postcode and preferred time.
The service area is a fact. Today’s availability needs a person.
Source: service-area page · checked 8 October 2026
The call-out fee covers the visit and inspection. Parts and additional work need a quote before you agree to go ahead.
Keep the qualification with the price information.
Source: pricing FAQ · checked 8 October 2026
The information I have does not say whether customer-supplied parts are accepted. Ask the team before booking.
Name the gap and give a useful next step.
Source: booking FAQ · this policy is not covered
I would begin with the information you already give customers. Gather the facts, keep the conditions close and make it clear who checks each source.
A service page, a pricing FAQ and a short booking guide are useful starting points. Read them together. If they disagree about the same service, settle that disagreement before using them as chatbot knowledge.
Download source packPut the service area, exclusions and booking conditions beside the relevant fact. “We offer repairs” leaves too much room for an answer about a job you do not take.
Someone should be able to confirm that a fee, contact detail or policy is still current. Record the date as well as the name. Recheck the source when the business changes it.
A customer saying a repair was finished that afternoon describes a particular visit. Keep that review attributed, and use the business's current policy for availability questions.
A question about today's availability, a custom quote or an uncovered policy usually needs somebody who can confirm it. Give the visitor the right contact route and say what information will help.
In the fictional call-out example, the team needs a postcode and a preferred time. “Contact us” becomes more useful when the visitor knows what to send and why.
Open the contact link yourself. Check that it reaches the team who handles that question, and that the visitor can still read the page on a phone.
If the reply promises a callback or a booking confirmation, check the actual process behind that promise. A polite sentence does not complete a handoff.
Save the exact question and reply, the source you expected it to use, and what you changed. Then ask again.
Try the question in the words a visitor would use. Include a follow-up: a different location, a missing detail or a request for something the business does not offer. A good first reply can still lose its qualification later in the conversation.
A source record, an answer review and space to note the fix.
Open printable worksheetThe worksheet opens as a plain page. Use your browser's Print command to print it or save a PDF.
The source pack and worksheet work on their own. These resources cover a chatbot on your website and a separate question: how the business appears in search answers.
ElfChatbot can use website pages, files and Q&A as source material. Prepare those sources and test the answers with your own business questions.
JustReviews brings reviews from their original platforms onto your website. Keep customer experiences attributed when you use them alongside business facts.
The AI Readiness Audit checks technical access to website content. Use it when retrieving the page is the problem.
I contribute to Beamtrace at Elfsight. These tools concern recorded search answers, rather than the chatbot answers on your own website.
Follow whether the business appears across the questions you monitor.
Keep position observations with the question and answer context.
Inspect businesses appearing in the same recorded answers.
Review when and how the business is mentioned.
Look at the pages cited in answers and what they support.
Read descriptions and reputation themes with the underlying answer available.
The audit and research briefings are my independent work. These readings concern search measurement; they do not establish how a website chatbot will perform.
Briefings with their original sources attached.
Read the language and market context with the observation. Original paper.
Examine the tested setting before applying a finding to your content. Original paper.
Keep appearing in an answer separate from someone visiting the website. Original paper.