Skip to main content
People can use your agent through a website widget on a phone or through its separate shared chat page. Check the actual route you will give customers so you can explain what they see.

​
Choose the route

Creators can obtain the standalone link from Home: select the intended agent, then open Deploy → Share link + QR. These are separate presentations. A working QR destination does not prove that the website installation works.

​
Try a short phone visit

If the intended chat is already open, start at step 3.
  1. Open the chosen website or chat link.
  2. Open the chat launcher if you are using an embedded widget.
  3. Check the agent name and welcome content.
  4. Open Chat if the message box is not visible.
  5. Tap the message box.
  6. Type a short question.
  7. Tap the arrow button labelled Send message.
  8. Wait for a reply or displayed error.
  9. Scroll the conversation.
  10. Open Account if offered.
  11. Return to Chat.
For a fictional practice café, ask about the menu using facts you supplied. Use the actual customer task when checking a real release. The chat adapts to the available screen. The host website and browser affect how much room an embedded widget has, so inspect the actual page as well as the builder preview.

​
Check text, prompts and files

Read the welcome content at normal phone size. Try any starter prompts you intend to offer. If uploads are enabled, check that you can reach the device’s file picker and read any sharing notice shown. Files visitors send you explains that separate task. Creators can adjust welcome wording and starter questions in Build. Appearance and features are in Design. Use short, clear wording that makes sense on a narrow screen. A phone message follows the ordinary chat flow: wait for a reply or the displayed error. There is no separate phone-only Save step.

​
If the keyboard covers the conversation

Close the keyboard to read the conversation, then tap the message box when you want to type again. If a link opened inside another app and behaves differently, try it in the phone’s normal browser. If the layout remains difficult, report the device, browser, website or link, and the particular control that is hidden. A screenshot can help; remove private conversation details first.

​
If the chat does not connect

Use Retry when offered and check the connection. If only the embedded widget fails, ask the creator to check the website installation and restrictions using When the widget will not load. A completed check means you could identify the intended agent, send a question, read the result and use the available navigation on that device. It is useful evidence for that device and browser, not a certification of every phone browser.