Troubleshooting
Find the cause of installation and conversation problems before changing a working configuration.
2 practical guidesFind the first check that fails.
Begin with the public page, the actual hostname and the customer action that failed. A missing loader, a rejected installation, incomplete Knowledge and an unavailable provider are different causes even when they appear as a generic support problem. Gather safe evidence before changing configuration: installation method, time, public URL, request stage and a non-sensitive error or run reference.
Use the widget-visibility guide when the launcher is missing and the conversation-error guide when an interaction fails. Check published HTML and caches before rotating credentials. Review source coverage for missing answers and billing state for capacity admission problems. If a write has an uncertain outcome, inspect the original run and provider record before retrying. Successful recovery should be followed by the original test and a related failure-path check.
- LocatePublic page and failing interaction
- ClassifyInstallation, content, capacity or Action
- ResolveSpecific supported remedy
- RetestOriginal case and a related boundary
Change the failing part, then repeat the same evidence-based check.
Widget not visible or not detected
Diagnose the template, domain, cache, credential and browser conditions that stop the launcher from appearing.
Read the guideConversation, answer and verification problems
Separate an unavailable service, stale conversation, missing Knowledge, identity challenge and intentional support policy response.
Read the guideYour website.
A useful conversation away.
Use the installation guide to get started, or ask our team about the setup your business needs.