A AtomicX Chat
Help Sign in

Updated October 14, 2026

Test your chat

Overview

Before you put the widget on your website, try it yourself. The Chat Widget Test page loads your real widget onto a sample web page, so you can chat with it just as a visitor would. You'll see your colours, position, display mode, welcome message, workflow, and AI answers in action.

To open it, go to Insights → Chat test.

Steps

Run a test chat

  1. Go to Insights → Chat test.
  2. Under Configuration, pick the widget you want to try from Chat Configuration. Its colours, position, and display mode are loaded from that configuration.
  3. Leave API URL as it is. You don't need to change it.
  4. Under Widget Theme, choose Light or Dark.
  5. Under Actions, click Initialize Widget. The status box below the buttons shows whether the widget started. It reads "Ready to test" before you start.
  6. Find the chat button in the corner of the page. If the configuration uses full-page mode, the chat opens in the centre instead.
  7. Click the chat button and have a conversation. Ask the questions your visitors are likely to ask.
  8. When you're finished, click Destroy Widget to remove it from the page.

The Sample Content Area on the page stands in for your website, so you can check that the widget doesn't cover anything important.

What to check

  • First impression. Are the chat title, welcome message, logo, and colours right?
  • Answers. Does the AI answer correctly from your knowledge base? If not, add or update your content.
  • Workflow path. Do questions, forms, and branches happen in the order you expect?
  • Handoff. If your workflow can pass chats to a person, trigger it. Then make sure your team sees the chat in Chat → Live monitor.
  • Booking. If you offer appointments, try booking one.

Check confirmed calls and improvement releases

For a callable workflow, test both Start and Not now. Check that a positive conversational answer alone does not start it. Try reloading during collection, cancelling, completing the form and asking the AI a follow-up question. Test staff takeover and return to AI control if your team uses handoff.

For AI contact forms, submit the missing details, choose either remember-consent option when offered, then check that the AI conversation continues.

For improvements, prepare verified regression cases and evaluate before approving and publishing. Evaluation uses synthetic runs; this Chat test page creates real conversations. After publishing or rollback, start a new conversation to check the new release: an existing conversation keeps its captured settings.

Check other languages

  1. Write a message in another language (for example, French or Bulgarian on an English page) and check that the chat switches. Check standard controls, approved title and welcome text, workflow questions, option labels, forms and booking prompts where used.
  2. Generate or save a translation draft without approving it and start a new test chat. The field should still use its existing current approval, or an automatic translation if it had none. Approve the draft, then test the reviewed wording.
  3. Change an English source field after approval. Check that the next chat in that language gets a new automatic translation, which you can then review.
  4. Switch language mid-chat by writing in the other language while a form is open. Check that entered values and selections remain intact and the workflow still follows the same branch.
  5. Reload during a chat and check that the saved conversation language is restored. Earlier messages should retain their original wording.
  6. Test page-language detection on your embedded website. Check a page in a language other than English. The Chat test page uses its own page language.
  7. Ask your usual knowledge-base questions in other languages. Check facts, names, numbers and links, as well as reply language. If you use handoff or visitor transcript emails, check those too; human replies and transcript messages retain their original wording.

For callable workflows, republish the agent after changing the workflow before testing a new call. Existing calls keep their captured version. See Chat languages and translations.

Other quick previews

  • On the configuration editor (Chat → Configurations → Edit), the Live Preview panel runs the real chat widget and updates as you change settings, before you save. Messages typed there are not sent. Chat test uses your saved settings, including the chat button character and the welcome bubble.
  • On Settings → Branding, the Live preview shows your branding the way visitors will see it.

These previews are great for checking the look. Use the Chat test page to try a full conversation.

Tips

  • Test chats are real conversations. They appear under Chat → Conversations, count toward your dashboard numbers, and use AI the same way visitor chats do.
  • After you change a configuration, click Destroy Widget and then Initialize Widget again to load the latest settings.
  • If the widget doesn't start, make sure the configuration is Active and has a workflow selected. If it still doesn't work, contact support.
  • Ask a teammate who didn't build the workflow to test it. They'll spot confusing questions faster.
  • While a test chat is running, the Atom AI button in the top bar is unavailable; hover over it to see why. It becomes available again when you click Destroy Widget or leave the test page.
An unhandled error has occurred. Reload ×