SupaGent Website Chat & Handoff
Deploy chat on pages, verify account identity and let an available teammate take over.
Open interactive lesson and quizWhat you will learn
- Deploy an agent to a published Page or external site
- Distinguish a typed name or email from verified account identity
- Enable a human handoff alert and claim a chat
- Explain why SupaGent stops replying once staff take it
A visitor opens the website widget, asks about an Order and then asks to speak with a person. Your team must protect private data and respond without competing AI messages.
Lesson 1
Publish the widget in the right context
The agent setup provides a script tied to the BU code and agent. For a SupaChrome landing or form Page, choose Show SupaGent chat and the agent, then publish the Page. You may also paste the supplied script into the Page HTML; a published Page recognizes it. For an external website, add the script before the closing body tag and test the resulting live page. The widget script is public and does not contain a CRM credential. A private draft or a mismatched BU code will not give you the expected live experience.
Lesson 2
Verify identity before personal answers
A visitor’s name and typed email alone do not prove ownership of a Contact or Order. To request a code, use the email field in the chat or send the email address by itself as a chat message. A code is delivered only when name and email match a Contact in this BU. Enter the eight-character code in the verification field; it expires after ten minutes and has limited attempts. After verification, the assistant can look up that Contact’s eligible Order or service information. An address in another BU cannot reveal that other business’s data. If no code arrives, a team member can still help without disclosing private records.
Lesson 3
Hand off once to an available teammate
A human request flags the conversation for the BU Live chat queue. Responders need Live chat view and respond permission and must set their presence Available to claim a new conversation. The workspace handoff alert can ring or vibrate after a user enables audio in the open browser tab. Take chat assigns one responder; subsequent visitor messages do not trigger new SupaGent answers while assigned. Release makes it available again; Close ends the conversation. If someone else took it first, refresh the queue rather than replying from a stale view.
Practice · Run a safe chat handoff
- In SupaGent copy an agent’s Website deployment script. Enable Show SupaGent chat on a landing Page, publish and test the live URL.
- On a separate external test page, add the script before the closing body tag and confirm the selected agent opens.
- Using a Contact email you control in this BU, request a verification code from chat and enter it in the verification field. Ask about an Order.
- Set a Live chat responder Available and enable ringing in their workspace tab. Ask for a person, take the conversation and send a human reply. Confirm no new AI response appears after assignment.