[DELTA - Web Chat, new page]
(1) Proposed title "Web Chat" (shipped UI label), slug (proposed) https://help.luware.com/webchat. Suggested category: Instant Messaging.
(2) Sources: Feature 136000 (public description, AC) and PBIs 144821, 145006, 145014, 145016, 145017, 153711, 153747, 155918, 158409; code on Nimbus / Nimbus.UI develop (2026-11-17).
(3) Feature flag EnableServiceWebChat (tenant, default off). [CHECK] Is it on for all customers with 1.138? If not, publish later or hide the page.
(4) Screenshots needed: tenant "Web Chat" section, service "Web Chat" block with Snippet, Configuration > Instant Messaging > CORS, widget on a website, chat in My Sessions.
(5) Once published, link this page from the "Web Chat Setup" tab of Use Case - Setting Up Instant Messaging (inserted article) and update the links on the other drafts (currently /webchat).
Web Chat lets visitors of your website chat with your Nimbus services. A visitor opens the chat widget on your website, enters a name and a first message, and the chat is routed to an available user through the service's Instant Messaging workflow. Your users accept and answer the chat in My Sessions, the same way as WhatsApp or SMS/RCS chats.
Web Chat is a channel of the Instant Messaging modality. It doesn't need an Interact license, a Microsoft Teams client or an Azure Communication Services instance of your own. Chats and audio/video calls directly with a user remain part of Interact.
PRECONDITIONS
โ Licensing
- Service: The service has a Contact Center license and offers the Instant Messaging modality.
- Users: Users who answer Web Chat chats have the Instant Messaging modality enabled in their General User Settings and are members of the service.
- No Interact license: Web Chat is included in the Instant Messaging modality.
โ Configuration and integration setup
A Tenant Administrator activates Web Chat once for your tenant. Service Owners or administrators then enable it per service, and a website administrator embeds the service's snippet on your website.
๐ Also refer to Instant Messaging for the preconditions and integration channels of the modality.
How Web Chat Works
[DELTA: Upload IM_Channels_Updated_138.drawio.png (Webchat 138 folder) or a crop of its website lane here.]
- A visitor opens the Web Chat widget on your website and starts a chat with your service.
- Nimbus checks that the website is allowed to show the chat and that Web Chat is active for the tenant and the service.
- The service's Instant Messaging workflow handles the chat, for example with a welcome message and a Queue Task activity.
- A user with the Instant Messaging modality accepts the chat in My Sessions and replies there.
- Either side ends the chat. The session appears in Nimbus Reporting like other Instant Messaging sessions.
Setting up Web Chat
Step 1: Activate Web Chat for your Tenant
โ Tenant Administrator rights are required.
- In Nimbus Admin, open your tenant and go to the Modalities tab.
- In the Web Chat section, switch Active on.
โฎ Nimbus generates the Widget Key for your tenant and shows the further options. - Check the Session Recovery Timeout in Seconds (default 20). Within this time, a visitor who reloads the page continues the same chat.
- Save your changes.
๐ All options are described in Modalities Tenant Settings.
[DELTA: The section is on the Admin tenant edit page (Modalities tab). Code shows no Portal equivalent. Confirm the navigation path customers use.]
Step 2: Create an Instant Messaging Workflow
- Go to Configuration > Workflows and create a workflow of type Instant Messaging.
- Start with an Accept Conversation and a Message activity to welcome the visitor.
- Add a Queue Task activity to distribute the chat to your service's users.
๐ Refer to Workflows and to the supported activities listed in Modalities Service Settings.
[DELTA: The Web Chat workflow dropdown filters workflows of type "InstantMessagingWebChat" (mapped to Instant Messaging). Check on stage that regular Instant Messaging workflows are listed.]
Step 3 (optional): Restrict the Allowed Websites
A CORS domain template defines which websites may open the chat of a service. Web Chat uses its own templates. They are separate from the Interact Domain Templates (CORS).
- Go to Configuration > Instant Messaging > CORS and click Create New.
- Enter a Name (unique in your tenant) and select the Organization Unit.
- Under Domain, add each website origin that may show the chat, for example
https://www.example.com. - Save the template.
โ IMPORTANT โ CORS templates
-
Exact match: The page's origin must match one of the domains exactly, including
https://and any port. Enter the origin without a path. - No template: A service without a CORS template accepts chats from any website.
- In use: A template assigned to a service can't be deleted.
[DELTA: Code compares the browser Origin with each template entry as a whole string (case-insensitive). Check on stage whether an entry with a trailing slash or path still matches.]
Step 4 (optional): Define Messages and Display Names
Service System Messages define the messages your visitors see at certain session events and the names shown for your users and service. Create one under Configuration > Instant Messaging > Service System Messages.
๐กWithout a Service System Message, Web Chat shows your users as Hidden and the service with its initial name.
Step 5: Enable Web Chat on the Service
- Open your service and go to the Modalities tab (Modalities Service Settings).
- Make sure Instant Messaging is enabled.
โฎ The Instant Messaging section lists the inbound channels, including Web Chat. - Switch Web Chat on and select:
- Instant Messaging Workflow (required): the workflow from step 2.
- Service System Messages (optional): the configuration from step 4.
- CORS (optional): the template from step 3.
- Save the service.
โฎ The Snippet section appears.
Step 6: Add Users to the Service
Make sure at least one user with the Instant Messaging modality is a member of the service. The modality is enabled in the user's General User Settings.
Step 7: Embed the Chat on your Website
- In the service's Web Chat block, expand Snippet.
- Click Preview to try the chat as your visitors will see it.
- Click Copy and paste the snippet into your web page, or pass it on to your website administrator.
The snippet contains an empty element with the id nimbus-webchat, where the chat appears, and a script that loads the widget with your service ID and widget key:
<div id='nimbus-webchat'></div>
<script> ... window.Nimbus.WebChat({ serviceId: "<service ID>", widgetKey: "<widget key>" }); ... </script>
<script id='nimbus-bootstrap' src='https://<web chat host>/static/js/bootstrap.js' publicurl='https://<web chat host>'></script>[DELTA: Shortened structure from the snippet generator (chat-service-snippet.component.ts). The host is webchat.<cluster domain> and is marked in code as a placeholder, not the final subdomain. Replace with a real example once final.]
๐ก TIPS โ Snippets
- Copy, don't type: Always copy the snippet from the service. It already contains the correct service ID and widget key.
- One snippet per service: Each service has its own service ID. The widget key is the same for all services of your tenant.
- New widget key: After a Regenerate Widget Key in the tenant settings, replace the snippets on all your web pages.
- Own chat page: To build your own chat interface, use the Web Chat SDK.
Chatting via Web Chat
| Topic | Behavior |
|---|---|
| Starting a chat | The visitor enters a display name and, optionally, an email address and a first message. |
| First message | The first message is available as the Initial Message parameter, so workflows and Power Automate flows can use it. ๐ See System Fields and Parameters. [DELTA: Code passes the first message as InitialMessage on the call information; the last step to the workflow parameter was not traced. Verify on stage.] |
| Message length | A message can have up to 1600 characters. |
| Page reload | A visitor who reloads the page or moves to another page continues the same chat, as long as this happens within the Session Recovery Timeout of your tenant. |
| In My Sessions | The chat card is titled Web Chat. Users accept, decline, park and answer chats like other Instant Messaging tasks. Web Chat messages show no delivery or read status. ๐ See Instant Message Handling. |
| Transfers | Chats can be transferred to another service. The visitor then sees the display names configured for the target service. |
| Ending the chat | Either the visitor or the user can end the chat. During After-Call Work (ACW), the conversation stays readable in My Sessions until ACW ends. |
| Chat limit | Each service accepts a limited number of concurrent Web Chat tasks (default 20). When the limit is reached, new visitors can't start a chat until the number drops. |
| Reporting | Web Chat sessions are reported as Instant Messaging sessions, like Interact web chats. [DELTA: Code uses the existing reporting endpoint value 8 "WebChat" (channel AcsWebChat). The OData label was not verified.] |
Moving from Interact Chat to a Service
If your website already uses Interact to chat with a service, you can move this chat to Web Chat:
- Set up Web Chat for the service as described above. You can reuse the service's Instant Messaging workflow and Service System Message.
- Create the allowed websites again under Configuration > Instant Messaging > CORS. Interact domain templates are not shared with Web Chat.
- Replace the Interact snippet on your web page with the Web Chat snippet of the service.
๐กInteract chats and audio/video calls directly with users are not affected.
[DELTA: Draft based on code facts only. The official migration guide (PBI 145019) is not started, and the retirement of Interact Chat to Service is prepared via backend flag DecommissionInteractChatToService (default off). Confirm with the PO whether this section stays, and whether the Interact widget and the Web Chat widget can run side by side on one page.]
Troubleshooting
โ IMPORTANT โ Chat doesn't start
- Tenant and service: Check that Web Chat is active in the tenant settings and switched on for the service, with an Instant Messaging workflow selected.
- Snippet: Copy the snippet again from the service. After a regenerated widget key, old snippets stop working.
- Website: If the service has a CORS template, check that the page's origin is listed. To test, remove the template from the service for a moment.
- Availability: Check that the service's chat limit isn't reached and that users with the Instant Messaging modality are available.
๐ Developers find the error codes returned to the widget on the Web Chat SDK page.
Known Limitations
โ IMPORTANT โ Known Web Chat limitations
- Chat only: Web Chat has no audio or video. For audio/video calls from your website, use Interact.
- No attachments: Images and files can't be sent.
- Messages: Messages can't be edited or deleted, and there are no delivery or read receipts.
- Formatting: Messages are plain text.
- Sign-in: Visitors start a chat without authentication. The tenant Authorization Mode is fixed to None.
- No Teams integration: Web Chat chats are not delivered to Microsoft Teams and don't use Adaptive Cards.
[DELTA: Out of scope per Feature 136000: media (F 142029), edit/delete, receipts, presence, token validation. Open PBIs not built: basic formatting (145003), opening hours via SDK (153221), additional authorization (154536). Allowed File Types shows a "Web Chat" column marked "Future".]