Check a chat installation before inviting customers
Read the guide →Guide preview
A visible widget is the beginning of acceptance, not proof of a working service.
Check installation, queue ownership, routing and visitor access with fictional conversations before relying on the channel. Keep a usable fallback outside the widget.
Prove one ordinary exchange, then test the busy, inaccessible and unavailable cases.
New to the topic? Begin with the first guide. Otherwise, go straight to the question you need to answer.
A visible widget is the beginning of acceptance, not proof of a working service.
Test the full queue and its customer message before raising the conversation limit.
Create only the groups whose ownership and fallback you can explain.
A transfer succeeds when the recipient understands the promise and accepts responsibility.
Use reusable facts and next steps, then adapt the answer to the actual question.
Test the device and the ownership fallback; a notification alone is not a service promise.
Evaluate the whole page with the widget closed and open, not just the vendor’s claim.
Collect only what the next support action needs and keep sensitive matters on an appropriate route.
Keep a known contact route and an owner for unresolved work before an outage happens.