Xillix field reference

How website AI chat hands a buyer inquiry to sales

A website chat handoff connects a visitor’s request for follow-up to contact details, a source page and a conversation a rep can review. Answering a visitor and requesting a sales follow-up are separate steps.

From the public demo

The sales record showed the exchange. The email held a reference to it.

We asked about employee and website audiences, chose the fictional contact, and compared the two outputs from the public demo.

How to test it yourself

  1. Start with a buyer question

    Choose a page and a question buyers ask there. For a visitor comparing two products, the answer should first explain which audience each one serves.

  2. Let the visitor choose

    Keep the response readable before inviting a follow-up. In the sample, the visitor can inspect the answer and then choose to reveal a fictional handoff.

  3. Read it as the rep

    Look for the buyer’s own wording, the answer already given and the source page. Open the notification separately and see what it tells a rep to look up.

Further reading

Guides and field tests

Guide

Website chatbot lead handoff checklist

Check what a sales rep receives from website chat. Test contact choice, page context, the conversation, and the difference between a lead record and an email.

Questions teams ask

Does asking a question submit an inquiry?

In the public demo, asking displays the assistant’s answer. Selecting the sample follow-up reveals a fictional lead record. The demo does not deliver a sales email.

Does the notification contain the full transcript?

The sample email includes contact details, the source page and a conversation identifier. The full question and answer are visible in the sample record. A deployed notification depends on the fields chosen for its rule.