Does your website only answer visitors, or help them get things done?

A visitor asks whether your team can handle their project. The chatbot explains the offer, then sends them to a form asking the same questions again. The website answered, but left the visitor to repeat the work.

A useful website can prepare the next step: gather the necessary details, check what can be checked and hand over an actionable request. AI helps only if it reduces that break. A well-designed form or a connection to your business system may be enough.

No time to read? Get the essentials in video. — Audio in French; on-screen text in French.

▶ Play video

Define the task the visitor wants to finish

Choose a journey: check whether a request fits, prepare an appointment or submit supporting records. ‘Chat with our AI’ is not an outcome. Visitors should understand what they will receive, which details are needed and when a person will take over.

For an illustrative service request, the site can collect the need, location and constraints, then prepare a summary. It must not promise availability without a current authoritative source. Preparing a request and accepting the job are different actions.

Hand over context without making premature promises

The useful handover puts confirmed information into the file the team actually tracks. The visitor receives a reference and confirmation; the owner gets the request with any missing details. ‘Message sent’ alone does not prove the business system created the record.

Design for transmission failure. Retain appropriate evidence, avoid inventing a confirmation, and reconcile the outcome before retrying a create action. A double click or network recovery should not produce two independent cases.

Separate public information from account actions

Explaining public terms needs different controls from viewing an order or changing an appointment. Access to a personal record requires identity and permissions checked by the application. What someone types into a chat is not proof of authorisation.

Collect only the details necessary for the task and explain their use. Visitors need a way to get help or contact the team without sharing sensitive information in an open conversation. Human handover is part of the journey, not a failure to hide.

Test completion, not conversation counts

Test a routine request, an out-of-scope request, a missing document and a network interruption. Check both what the visitor sees and what the team can actually find. A pleasant conversation that leaves no actionable next step has not completed the task.

Observe completed tasks, repeated questions, errors and handling effort. More conversations prove neither better conversion nor time savings. The trial should help choose between improving the interface, connecting existing software or adding one specific AI capability.

SAY Digital can start with an existing visitor journey, locate the break and prototype an improvement connected to your business tools. You test a completed task, not simply another chatbot added to the website.

SAY Go Big Online — discuss your first use case

Continue exploring this case

• AI digital agency: why the website is no longer enough

References and limitations

• Anthropic — Building effective agents
• NIST — AI Risk Management Framework

These references explain mechanisms and risks. The situations are illustrative; no quantified client benefit is claimed.