A website agent handoff works when the visitor knows a person will respond, the right team receives a useful summary, and someone accepts responsibility for the next step. Define the trigger, the minimum information to pass, and the fallback if no one is available before enabling the transfer.
Fictional example: A visitor to Selby Home Repair asks whether the company can inspect a roof leak in Hollis, a town missing from the published service-area list. The site also says routine appointment requests receive a reply during business hours. The agent cannot confirm coverage or dispatch help. It may explain that the site does not list Hollis, ask whether the visitor wants a team member to check, and prepare a handoff draft with the visitor’s requested callback window.
A handoff is a decision point with an owner, not just a transfer icon.
Choose the moments that require a person
Route a visitor to a person when the answer is outside published information, sources conflict, the request needs a commitment, or the visitor asks for human help. Define any additional triggers for complaints, accessibility needs, safety concerns, or account-specific questions. The agent should not treat a lack of information as permission to guess.
For Selby, the trigger is an unlisted location. A missing callback number is not permission to collect unrelated details; first ask what the visitor wants to share and explain why the team needs it. Do not call a routine service request an emergency route unless the company has defined and staffed that response.
Prepare a short summary for the receiving team
Give the receiving person enough context to continue without asking the visitor to repeat everything. A useful packet may include:
- The visitor’s original question and their stated goal.
- The relevant published page and the detail the agent could not confirm.
- Any answer already given, clearly separated from unresolved facts.
- Contact details the visitor chose to provide and the agreed way to follow up.
- The time of the request, current status, and the team expected to respond.
Keep personal information to what the next step needs. Let the visitor inspect or correct the summary when practical. Make clear whether a request has only been prepared, has reached a queue, or has been accepted by a person.
For Selby, the handoff draft could say: “Please check whether roof-leak inspections are available in Hollis and call after 3 p.m. if coverage is confirmed. The visitor asked about a roof leak; the published service-area page does not list Hollis. No appointment has been offered.” The agent has not made a booking or promised service.
Assign ownership and acknowledgement
Name the team that watches each queue, the hours it is monitored, a response expectation, and a backup owner. Decide what the visitor sees after submitting a request. If no immediate response is available, state when and how the team expects to reply, or offer another contact path. Do not show “connected” or “accepted” until a person or system has actually confirmed ownership.
For Selby, show distinct messages for confirmed and unconfirmed handoffs:
Acknowledged: “The Selby team has received your request to check service in Hollis. The site says routine appointment requests receive a reply during business hours. No inspection has been booked.”
Unconfirmed: “I can’t confirm that the team received your request, so it has not been accepted yet. Please use the contact method published on the site.”
Keep unconfirmed requests pending and do not promise a response time beyond the published guidance.
Test routine hours, after-hours requests, unavailable queues, duplicate submissions, and a visitor who changes or withdraws the request. Check whether the right person receives the packet, whether the visitor sees an accurate status, and whether the case can be followed through to a response. A transfer event alone does not show that the handoff was completed.
Use human review and escalation to choose the decision point. For the website conversation itself, see website AI agents and evaluate the visitor workflow.