This AI chatbot demo shows how a website visitor can ask a business question and explore a next step in chat. Open the chat button and ask about the demo business's services. The reply uses that business's information, not your own website content.
Use a fictional enquiry to explore the conversation. Do not enter private documents, passwords, payment details, or sensitive personal information. Demo conversations have strict usage limits.
The chat button opens the shared demo assistant. This is a trial conversation, not a binding service quote or a customer success story.
Test how it handles a real enquiry, rather than judging it from a single greeting. A useful reply should answer the question, stay within the available knowledge, and explain what happens next.
Try ?What website services do you offer?? or ask about a service mentioned by the demo business. Check whether the answer is relevant and easy to understand. If you ask for a price that is not supplied, look for a clear explanation or an invitation to contact the team, rather than an invented quotation.
Try ?What information would your team need from me?? A follow-up helps you judge whether the conversation remains useful. Compare the answer with the question you actually asked. If a response is vague, ask one narrower question instead of providing private information to make the trial more realistic.
Review the contact and appointment options available in the widget. Understand which details a visitor would be asked to share. An appointment request still needs the business to confirm it. Contact links depend on the widget configuration; a WhatsApp link opens WhatsApp rather than running a native WhatsApp bot.
The demo helps you assess the chat layout, reply style, and visitor journey. Open it on your phone as well as desktop. Check that you can close the chat, return to the page, and reopen it comfortably. Think about how the greeting and contact options would fit your website.
It cannot show how well your future assistant will answer every question about your own business. That depends on the knowledge you provide, your settings, available service capacity, and the questions visitors ask. The sample conversation and dashboard illustration on the homepage are labelled examples; their numbers are not measured customer results.
Create a free workspace and add a focused set of FAQs, service descriptions, prices, and policies you are authorised to use. In the dashboard tester, ask the questions you receive most often. Include an ambiguous request and a question outside your services. Correct the knowledge when a reply misses an important detail.
Follow the website chatbot installation instructions to approve your domain and publish the snippet. Submit a test enquiry with your own contact information and review it in your dashboard. Make sure the person who receives enquiries understands the follow-up process.
Review the Free plan and current usage limits before sharing the widget widely. Read the privacy policy for account and chat data, and check the optional visitor analytics controls. A declined analytics choice should not prevent the visitor from using the chatbot.
Once you add your business information, try a small set of realistic enquiries: ?Do you serve my area??, ?What is included in this service??, ?How can I speak to someone??, and ?Can I request an appointment?? These are suggested test prompts, not a transcript of a real customer's conversation.
Write down the answer you would expect from your team before asking the assistant. Include any conditions that matter, such as your delivery area or opening hours. Compare the reply with that reference, and correct missing knowledge before installation. Repeat the check after changing a price or policy so outdated information does not shape your follow-up.
Use these checks to record what you learn from the demo and repeat them with your own assistant. You do not need a numerical score or a long test document. A short note about the question, reply, and required correction gives your team a useful starting point.
Does the answer address the visitor's question directly? Can you trace its important details to information the business supplied? Try two ways of asking the same question. A useful assistant should be understandable in both cases, but check any important price or policy before relying on it.
Does the visitor understand whether they are requesting contact, asking for an appointment, or opening an external contact link? Avoid treating all of these actions as a completed sale. When you configure your own widget, make the greeting and contact options match what your team can actually deliver.
Can you read the answer without zooming, reach the message box, and close the panel? Try a short message and a longer one. If you have a sticky menu or another chat tool on your own website, check that the controls do not compete for the same corner.
Who will review a new enquiry, and what information do they need? In your own workspace, check the saved conversation and lead record after a test submission. Decide how your team will handle unanswered questions and appointment requests before sending real traffic to the widget.
Separate an interface problem from a knowledge problem. If a button is difficult to reach, review your widget design and placement. If the reply is incomplete, update the relevant business information and retest the question. If you need a capability beyond website chat, check availability before choosing a plan rather than assuming the demo includes it.
Start with one clear visitor journey, such as a service enquiry followed by a contact request. Once your team can handle that journey reliably, review other questions and add information where it helps. This gives you a more useful trial than enabling every option at once.
The public demo has strict usage limits. An unavailable reply may reflect capacity or configuration rather than your question. Try again later or use your own workspace tester. If you cannot see the chat button, check browser blocking extensions and whether scripts are allowed. The installation guide also explains domain approval and common setup issues.
Try an agency service question, then a follow-up about the next step. Use the demo to assess the reply and chat experience rather than to obtain a binding quotation.
No. The homepage walkthrough and preview use labelled sample data. The demo is a product trial, not a customer endorsement or evidence of a conversion result.
Create your free account, add your business knowledge, and test the assistant in your workspace. The shared demo uses the demo business information rather than your website content.
The shared demo has strict usage limits and depends on available service capacity. If it cannot reply, try later or test in your own workspace. Do not share sensitive information in the public demo.
Start with useful answers, then build a follow-up process your team can manage.