What should happen when a website AI assistant cannot answer?

Give the visitor a clear route to a person, and agree what context that person receives before relying on the handoff. Test the unanswered question, assigned follow-up and next-shift review as one workflow; a visible contact button alone does not demonstrate that anyone received or resolved the request.

Reviewed

All answers

What to check

  • Agree escalation triggers: missing facts, a disputed answer or a request for a person.
  • Define the minimum approved context, responsible team and response expectations.
  • Run a shift-change scenario and check what remains unresolved.
Handoff checks to put in the scope
StepQuestion to resolveEvidence to request
Visitor asks for helpWhat is sent, with whose confirmation?The visitor-facing handoff text and submitted context
Team follows upWho sees the pending question and owns the next action?A pending item and the agreed follow-up process
Shift changesCan the next person see the necessary context?A walkthrough using the scoped access and retained information
Issue is answeredShould the approved knowledge change?A reviewed source update and repeated question

How to use the evidence

List conversation history, notifications, assignment and retention as requirements to verify, rather than assuming all of them come with an AI reply. Keep sensitive information out of evaluation examples and agree the access boundary before sharing real conversations.

Where WEAVIST fits

WEAVIST ACE passes questions needing a person to the team. WEAVIST Workspace shows questions awaiting a person’s reply, follow-up to-dos and knowledge submissions and review; the published scope does not specify full transcript transfer or shift-assignment automation.

Follow-up questions

Does WEAVIST Workspace handle tour enquiries?

Tour enquiries use SPATIAL 3D’s own workflow. WEAVIST Workspace is ACE’s admin for usage, pending visitor questions, follow-up to-dos and site knowledge.

Can we assume the full conversation is transferred?

Ask to see the exact context and access available in your proposed workflow. Include the required transcript, retention and shift-change checks in the written scope.