When should your website assistant hand off to you?

Your website assistant should hand a question to you when it needs a judgment call, a custom quote, a confirmed appointment, or information it does not have. It should also respect a direct request to speak with a person. The handoff means collecting an inquiry for review, not promising that a human is joining the chat now.

An assistant can explain your services and collect the question. When only the owner can decide, another round of automated answers just makes the visitor wait longer.

Identify the questions it should not settle

Write down the boundaries before configuring the assistant. Common handoff situations include:

• A price depends on the property, project, or inspection.
• The visitor asks for a specific appointment or arrival time.
• The request is outside the published service area or normal scope.
• The visitor is unhappy or needs help with a sensitive issue.
• Approved information is missing or contradictory.
• The visitor asks for a person instead of another automated answer.

The assistant can gather a short description and preferred contact details. It should not require the visitor to repeat the entire conversation or keep pushing optional questions after the person asks to stop.

For a fictional repair business, "Do you repair gates?" may be answered from the approved service list. "Can you fix this gate today for this price?" needs review. Those are different jobs even when they concern the same service.

Say what the handoff actually does

A useful handoff message tells the visitor which detail needs review, what information to leave, and how the business normally responds.

Suggested wording might be: "This needs the owner's review. Leave your contact details and a short description so the business can follow up. This is an inquiry, not a confirmed appointment."

Replace the general wording with the real process. Do not say "Connecting you now" unless a live transfer exists and someone is available. Do not say "Your booking is confirmed" because a visitor selected a preferred time.

Keep a published contact route available for people who prefer to call or use the form. The assistant should be an additional route, not a gate customers must pass to reach the business.

What happens in LeadSpark's standard plans?

The current Business Hub plans include an AI Website Assistant using approved business information for questions and inquiry capture. Launch provides a daily email inquiry summary. Growth and Reach email the business as new inquiries are submitted.

Those differences concern the business's notification timing. They do not establish a staffed live chat or a guaranteed human reply time. Around-the-clock assistant availability is not around-the-clock human support.

CRM connections, automated customer follow-up, scheduling workflows, and integrations are separately scoped custom work.

What if the assistant does not know the answer?

Give it an approved uncertainty response and a review route. "I do not have that information confirmed" is preferable to a plausible answer about a service exception or price.

Review recurring unknown questions. Add an answer only after the business approves it. If the question always needs judgment, keep the handoff instead of trying to solve it with a longer instruction.

Check the boundary with ordinary customer questions

Before launch or after changing the approved information, test a custom quote request, an unavailable fact, a complaint, and an explicit request for a person. Review what the visitor sees and where the inquiry reaches the business.

Our guide to AI versus automation explains why people keep control of promises. If the website needs a clearer inquiry route, compare Business Hub plans. Agree on the human response process alongside the assistant, so visitors know what happens after it stops answering.