Choose a website conversation approach by the visitor’s need, the information available, and who must make the next decision. A scripted chatbot fits predictable paths; an AI agent can work across approved information for less predictable questions; live chat puts a person in the conversation. These options can also work together.
Fictional example: A visitor to Juniper Hall asks, “Can you host 80 seated guests, is the entrance step-free, and can I reserve the room for next Friday?” The venue’s published event page lists a seated capacity of 80, the accessibility page describes the entrance, and a request form collects event dates. The agent may answer those published details and prepare an availability inquiry, but it cannot see the live calendar or confirm a booking.
The visitor’s path can end in self-service or a clearly owned handoff.
Compare the work each option handles
Scroll horizontally to see all columns.
| Approach | A good fit when | Decide before launch |
|---|---|---|
| Scripted chatbot | Visitors can choose from a small set of known topics or steps. | Which paths are supported, and how does a visitor leave a dead end? |
| Website AI agent | Questions vary, approved pages can support answers, and the task has a safe stopping point. | What sources may it use, what can it do, and which cases require a person? |
| Live chat | A person needs to interpret nuance, make a judgment, or take responsibility for a request. | When is staff available, who owns unanswered requests, and what context reaches them? |
Present live chat as available only during times when a named person or team is assigned to monitor requests and can accept them. When nobody is on duty, switch to a contact or callback request, show the expected response window, and do not imply that a person is connected. If a request enters a queue, describe it as pending until the receiving team confirms ownership.
A search page, FAQ, or short form may be simpler than any of these when the next step is already known. A scripted flow can be easier to inspect for a fixed process. An agent can adapt a response to the visitor’s wording, but its flexibility makes source quality, boundaries, and testing important. Live chat lets a person handle the conversation directly, but it is available only when staff can respond.
Apply the comparison to one visitor request
For Juniper Hall, a scripted chatbot could direct visitors to the capacity, accessibility, and booking pages. That may be enough if most questions follow the same route. A website agent could combine the relevant published details in one answer and prepare the availability request. A staff member could confirm the date after checking the calendar and clarify any event requirements.
The visitor-facing answer should stay within the evidence: “The event page lists capacity for 80 seated guests, and the accessibility page describes a step-free entrance. I can prepare an availability request for next Friday. The venue team must check the calendar and confirm the date.” The agent has not sent a request or reserved the room.
The separate request draft for a staff member is: “Please check whether Juniper Hall is available for 80 seated guests next Friday. The visitor also asked about step-free access; the published accessibility page describes a step-free entrance.” The staff member checks the live calendar, sends the inquiry, and confirms any booking directly. If the visitor asks the agent to guarantee the date, it should explain that it cannot confirm availability and offer the staff handoff.
Decide what happens between self-service and a person
The choice does not have to be exclusive. A chatbot or agent can answer routine questions and offer a live handoff when it reaches a boundary. Make the transition visible: tell the visitor what information will be passed along, capture only what the team needs, and name the group responsible for replying. Set a path for out-of-hours requests so the experience does not imply immediate human coverage.
Before choosing an agent, list the top visitor questions and the approved page that supports each answer. Include a missing-source case, a conflicting answer, a request to make a commitment, and a case where a person is needed. Measure answer usefulness and handoff completion separately; a long conversation does not show whether the visitor reached a useful outcome.
For the agent pattern and its boundaries, read website AI agents. Use human review and escalation to define the handoff, then evaluate the workflow before expanding it.