Give your website a front desk that knows where to start.

Begin with a question that leads somewhere: finding the right service, explaining your coverage or preparing a quote request.

Define what the assistant should answer, what it should ask and what needs a person’s judgement. A focused first journey gives you something concrete to test.

Bring together the service descriptions, coverage information, policies and next steps the assistant needs. Resolve conflicting details and identify who keeps them current.

SiteKnova’s knowledge setup helps connect a question with relevant business information. The business remains responsible for approving the facts it wants visitors to rely on.

Prepare your business knowledge ↗

Visitors can start with their own words. “I need a clean before I move out” gives the conversation a different direction from “I’m looking for weekly cleaning.”

The assistant can ask useful follow-up questions, carry forward the details already shared and accept corrections. The aim is a clearer request without making the visitor repeat their story.

The visitor sees the proposed enquiry and can edit it before confirming. Service details, location, timing and contact information should say what they intended.

A preferred date stays a preference until the business confirms availability. A request for a quote stays a request until the business supplies one.

Explore reviewed enquiries ↗

In the controlled pilot, explicit confirmation can save the enquiry and route a notification to the configured business recipient. Setup determines which handoff is available.

The team can then review the request and respond through its agreed process. Saving a request, routing a notification and confirming a booking are different steps; the visitor’s status should reflect the step actually completed.

Ask about an unavailable service. Change the address halfway through. Request a price that is not published. Stop before confirming.

These cases show whether the assistant respects the business’s boundaries and the visitor’s choices. They belong in the demo alongside the straightforward questions.

Read the evaluation checklist ↗

• One visitor journey to focus on.
• Current information covering that journey.
• A person who can approve the answers and boundaries.
• A clear destination and owner for enquiries.

Technical fit, rollout and available connections are assessed before a pilot. A demo is the next step for discussing your website.

Request a demo ↗