Customize the chat widget's appearance and content

The chat widget’s appearance helps customers recognize your service. Its welcome message explains what your AI agent helps with. Changing appearance does not change the agent’s data sources or response instructions.

Open the agent editor in Oma Aihio. You need permission to change the agent’s settings. Prepare an appropriate image and a short welcome message. Some customizations require a plan or add-on; check any field restrictions before planning your change.

Saved settings can affect a widget already in use. Keep a record of the current values if you may need to restore them.

Select Appearance in the agent workspace. Settings are organized into expandable groups; Content and Style are not separate workspace tabs.

1. Make your service recognizable

   Open Appearance → Content and set the name and image. Choose an appropriate theme and colors in Style. Check that the text and launcher remain distinguishable against your website’s background.

2. Explain what the agent helps with

   Open Content. Write a brief welcome message and add conversation starters that the agent has information to answer. Avoid promising actions you have not enabled.

3. Save and try it on your website

   Select Save and wait for confirmation. Reopen the widget on your website and check its name, image, welcome content and launcher. Repeat the check on a phone.

Adapt the text to your actual service. For example, for product guidance:

Test every starter: the agent needs information relevant to it. Add booking or order processing only when the corresponding action is configured and tested.

Choose the language version before editing welcome text or other localized content. Missing translations may use the default-language content. Widget interface language and agent response language are separate settings; see languages and localization .

• Check the save confirmation and confirm that the website embeds the correct agent.
• Refresh the website and reopen the widget.
• If only one language appears unchanged, check that language version and the default language.
• If text is hard to read or an image is cropped poorly, choose a clearer color or image. Restore the previous values and save if needed.

A working preview is only the first check. Other website elements can affect how easily customers find the chat widget.

Appearance → Content includes Show sources. Enable it, save and test a question whose answer uses a web source. Check the answer’s source link and destination. Not all knowledge-base content has a publicly accessible page; a citation alone does not guarantee correctness.

Appearance → Capabilities includes voice input. Check availability in the workspace, enable it and save. Test on the actual website with microphone permission, and check the recognized text before sending. If permission is missing or recognition fails, the customer can type their message. Voice input converts speech to text; it does not provide a telephone channel or spoken replies.

The Style group provides light, dark and automatic color modes. Test automatic mode on the embedding website too: the dashboard’s own theme is a separate setting. Check text contrast, keyboard focus, links and forms in both color modes.

New-message sound and language selection in the visitor menu are visitor preferences. Sound also depends on the browser allowing playback; a silent browser does not establish that a message is missing. AI replies appear progressively, and consecutive messages from the same sender can form one bubble group. Check the completed answer rather than treating unfinished text as the result.

The AI label on the first AI reply tells customers that AI is being used. It cannot be removed through appearance settings. On a small screen, also check the launcher, scrolling, message field and completion of any action card. Checking appearance does not replace testing the agent’s replies .

Also check availability and any applicable add-on in your workspace. This table gives minimum tiers for these features; it is not a workspace usage limit or a list of every integration.