Put support on your own site.

What you need before setup

Bring the site where the conversation will appear, your current help centre, the identity method you use, a working handoff destination, and one bounded customer request to test. Use a test workspace and reviewed sources before you expose customer work.

Site access

List each origin where the widget may load. Test every permitted origin and one origin that must be rejected.

Customer access

Define how your system will verify customer identity, account scope, and permission before exposing an account fact or action.

Safe completion

Define the exact change and any charge that the customer must confirm. Check that a failed request never appears as completed.

Human handoff

Test the actual destination, the context it receives, and when a person is available.

How the widget path works

The reviewed app source includes a loader that reads public widget configuration and embeds the chat frame. Origin checks and tenant live-state checks control where the widget appears. A visitor opening the widget does not establish verified identity, permission, or a completed task.

Current capability depends on tenant setup. Confirm the allowed origins, handoff address, reviewed knowledge, identity connection, and supported request before launch. No named helpdesk connector is implied by the widget, and a source review does not certify a customer deployment.