Use the Live Chat channel settings to choose which contact details visitors enter, enable CAPTCHA and visitor monitoring, and set session and message limits.
Use the Admin role in the space that owns the Live Chat channel. Start with an installed, active widget. If you still need to install it, follow Install a Live Chat widget on your website.
Visitors complete the enabled form before sending their first message. Submitting the form alone does not start a conversation. Without prefill, the first message starts the conversation without requiring those form fields.
Entering a name or email in this form does not verify the visitor’s identity.
Monitoring starts when the widget loads, even before the visitor opens the chat panel. It reports activity, whether the visitor is typing a chat message, and the current page title and path. Query strings, URL fragments, form values and the text being typed are not included in these monitoring updates. Make sure monitoring matches the privacy information you provide on your website.
CAPTCHA helps reduce automated messages. It does not verify a visitor's identity or guarantee that an attachment is safe.
See Cloudflare's Turnstile setup guide for creating your widget. HEDESU currently supports Cloudflare Turnstile for this setting. You manage the website hostnames in your own Cloudflare account.
Every visitor must verify before submitting details, messages or attachments, including visitors whose identity is verified by your website. An active verified session can continue without a challenge on every message. A new or reopened session, or changed CAPTCHA settings, requires verification again. Visitor monitoring and messages sent proactively by your team remain available before verification.
The saved secret is not shown again. Leave Secret key blank to retain it. If you replace the Site key, enter the matching secret too. Turning off Enable CAPTCHA retains the saved keys; existing message limits continue to apply.
The appearance preview does not run CAPTCHA. Test on a website hostname registered on your Turnstile widget.
If verification expires or cannot load, select Retry verification. If retrying does not help, check that the site and secret keys belong to the same Turnstile widget, that its registered hostnames include the website, and that the website allows Cloudflare's verification scripts. After too many attempts, wait before retrying.
When CAPTCHA is enabled and verification is unavailable, visitors cannot submit details, messages or attachments. You can correct the configuration or turn off Enable CAPTCHA and save to restore access without verification.
Security and verified identity contains Visitor JWT verification. This is for a website integration that supplies signed visitor tokens. Only enable it after your website developer has prepared and tested that integration; missing or invalid tokens can prevent visitors from starting a session.
The prefill form and verified identity serve different purposes. Prefill collects visitor-provided details; verified identity relies on the signed identity supplied by your website. This guide does not cover building that integration.
Use whole numbers. Idle close accepts 1–1,440 minutes, Messages per minute accepts 1–600, and Burst capacity accepts 1–1,000. These are visitor messaging controls, not a promise about your team’s response time.
Reopen the channel settings to confirm the saved values. On a test page, start a fresh visitor session and check that the expected prefill fields appear. If a required field is missing, check that Show field is enabled for it. If a visitor is temporarily unable to send repeated messages, allow time for the message allowance to replenish.