Skip to main content
Web Chat adds an inbound conversation widget to a website. Visitors can start a conversation with the Agent, but Web Chat is not available as the first outbound channel in a cadence.
If Agent Settings is not available for your role, ask an administrator of your Nexor account to configure and install the widget.

​
Open Web Chat settings

1

Open the agent's channels

Select the agent in the left sidebar. In the right pane, go to Channels and choose Add. The Channels window opens.
2

Configure Web chat

On the Web chat row (Website widget), choose Configure. Nexor opens that agent’s Web Chat editor.
3

Save before installing

Configure the widget, select Save changes, and then test the installed widget on an allowed website.
The editor brings together three setup areas: behavior, design, and installation.

​
Configure behavior

Use these controls to define the first experience and the Agent’s writing style:
  • First message: the message shown when a visitor opens the chat. It can include {{first_name}}, {{last_name}}, {{full_name}}, {{email}}, or {{phone}}.
  • Agent style: free-text rules for tone, wording, and what the Agent should or should not do.
  • Example messages: sample replies that demonstrate the preferred voice, length, and format.
  • Capture lead info: ask for selected contact fields before the visitor can chat.
Lead capture can request First name, Last name, Email, and Phone. Select only the fields the team needs.
Example messages teach the Agent how to write. Suggested questions are clickable prompts displayed to visitors on the widget home screen. They serve different purposes.

​
Configure design

The design controls are grouped into these visible sections:
  • Identity: Agent name, avatar, chat title, and chat subtitle.
  • Home screen: a two-line home greeting, message card title, and up to four suggested questions.
  • Appearance: accent color and a rounded or square shape.
  • Live preview: switch between Home and Chat to review the result before saving.
The avatar accepts a public URL or an uploaded JPG, PNG, or WebP image up to 5 MB. The widget language follows the Agent’s configured language.

​
Add allowed domains

Open Install, then add the production hostnames where the widget should run.
  • Enter a hostname such as example.com, without a protocol or path.
  • Use a wildcard such as *.example.com when the same widget should run on that domain and its subdomains.
  • You can save up to 50 entries.
The Web Chat key and its Allowed domains list belong to the workspace. Changing the list from one Agent affects other widgets that use the same workspace key.
Add explicit domains before publishing the widget. A blank Allowed domains list does not currently block the standard widget, despite the empty-state message in the dashboard. Do not use a blank list as an off switch. The allowlist applies to the normal widget transport when the browser reports a parent hostname. It is not an authorization guarantee for the SDK v0.1.44 requestContact flow, which is not supported on untrusted public sites while backend hardening is pending.

​
Use the correct key

The Install section shows API Key, Agent ID, and Client ID. The widget key starts with nxr_pub_. It is browser-visible, is not a secret, and is intended for Web Chat.
Never replace it with a REST key that starts with nxr_live_. A nxr_live_ key is secret and must not be placed in HTML, JavaScript sent to a browser, screenshots, or a public repository.

​
Choose an installation method

Both methods use the browser-visible nxr_pub_ key and the Agent ID shown in Install. Do not initialize either method with an nxr_live_ REST key.

​
Install the hosted widget

The basic installation does not require npm. Under Embed snippet, use Copy to copy the generated values for the current Agent. The snippet has this shape:
1

Copy from Nexor

Copy the complete Embed snippet from the Agent’s Install section. Do not reuse IDs or keys from another workspace.
2

Paste it into the website

Add the script just before the closing </body> tag on every page that should show the widget.
3

Deploy and test

Publish the website, open it on an allowed hostname, and start a real conversation. Confirm the launcher, home screen, lead capture, and Agent reply.
The hosted URL is a managed delivery path, not an npm package version. Copy the current snippet from Nexor and do not infer a loader version from its URL.

​
Install with the npm package

Use the npm package when application code needs to open or close the widget, send a message, update page-specific prompts, read the session ID, or react to lifecycle events. The SDK exposes initChat, callbacks for open, close, messages, lead capture, and errors, and a handle for programmatic control. See the JavaScript SDK reference for installation, configuration, callbacks, and handle methods.
The npm package and hosted loader are separate distribution paths. Pin and upgrade the npm dependency through your application’s normal release process; the hosted loader URL does not state which npm release it serves.

​
Troubleshooting

​
The launcher does not appear

Confirm that the script is present in the rendered page, that the data-workflow and data-key values came from the same Agent setup, and that the key starts with nxr_pub_. Also confirm that Web Chat is not disabled for the Agent.

​
The site is not authorized

Add the exact production hostname under Allowed domains. Do not include https://, a port, or a path. Add a wildcard when subdomains need access.

​
Changes do not appear in the widget

Select Save changes, reload the website without an old cached page, and open a new widget session. Use Live preview to confirm that Nexor saved the intended design.

​
Nexor cannot load the Web Chat key

Reload the Agent settings and try again. Do not substitute a REST key while the public key is unavailable.

Review Agent settings

See how Web Chat fits with the Agent’s language, prompts, and other channels.
Last modified on October 5, 2026