Turn “I’m interested” into a next step.

The service they asked about. The situation they explained. The correction they made halfway through.

These details belong in the enquiry when they help the team respond. The visitor should not have to start the story again at the final step.

Read it

The visitor sees the proposed enquiry with the service details and contact information together. They can check that it says what they meant.

Change it

The visitor can correct the scope, timing or wording. Their preferred date stays a preference, and anything the business still needs to confirm stays clear.

Confirm it

The visitor decides when the request is ready. An explicit confirmation moves the reviewed enquiry into the configured handoff. Preparing a draft does not submit it.

Fictional example — no request is sent

“I’m moving out of a furnished two-bedroom flat and would like to ask about an end-of-tenancy clean. My preferred date is 18 November. Please confirm availability, what the service includes and how to get a quote.”

The team has a starting point. The visitor has not been promised an appointment, a price or work outside the agreed scope.

See the full example ↗

In the controlled pilot, the confirmed enquiry can be saved and a notification routed to the business recipient configured for that workflow.

The receiving team reviews the request and takes the next step through its agreed process. Available routing and follow-up arrangements are discussed before rollout.

No. A request tells the business what the visitor would like. A booking requires confirmation from the business or its connected scheduling system.

The wording shown to the visitor should make that distinction clear at every stage.

Bring an example of the information your team needs to respond well. We can use it to shape a focused demo, from the opening question to the reviewed enquiry.

Request a demo ↗ · See how SiteKnova works ↗