Field note
How we built a website chat handoff you can inspect
Trace one buyer question from the public API to a sample lead record and rendered sales notification, with a real screenshot and a repeatable request.
Xillix field reference
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
We asked about employee and website audiences, chose the fictional contact, and compared the two outputs from the public demo.
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.
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.
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
Field note
Trace one buyer question from the public API to a sample lead record and rendered sales notification, with a real screenshot and a repeatable request.
Guide
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.
Field note
Read two actual buyer questions about pilot pricing, the answers LuxonLeadAssist returned, and what carried through to the sample sales record.
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.
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.