Live chat widget setup

What it does

The chat channel gives you a Microsoft-hosted chat widget that you paste onto a website as a script tag, plus the admin surface that controls how it looks and behaves. Conversations it raises land in a messaging workstream and are routed to representatives in Copilot Service workspace like any other channel.

Key facts

Configured in Copilot Service admin center under Customer support > Channels > Chat > Add chat channel. The wizard has four pages: Channel details, Chat widget, Behaviors and User features.
The embed is a snippet copied from the Chat widget tab and dropped into the <body> of the page. On Power Pages you paste it into the Chat Widget Code content snippet in the Portal Management app rather than editing a web template.
The widget needs cookies, session storage and local storage in the customer's browser. Third-party cookies must be enabled — that is a documented requirement, not a nice-to-have.
Microsoft collects widget telemetry by default (org ID, widget version, browser name, OS, and an IP address with the last octet scrubbed). Add data-enable-telemetry="false" to the script tag to turn it off.
Chat widget page settings: Title, Subtitle, Theme color, Logo URL and Representative display name, plus toggles for proactive chat, reconnect to previous chat, show only during operating hours, and show only on listed domains.
Behaviors page covers custom automated messages, pre-conversation survey, post-conversation survey, authentication settings, customer wait time and queue position display, and customer location detection.
User features page covers file attachments, unread-message count and sound, transcript download or email, voice and video calling, screen sharing and co-browse. Screen share and co-browse both need a non-Microsoft provider from the marketplace.
Persistent chat requires chat authentication settings to be configured first. Make chats persistent sits on the workstream; Show previous conversations and History duration (months) sit on the widget.
Live chat is subject to the platform quota of 100 incoming conversations per minute for the chat channel (adjustable via support), and roughly 28 KB per message including metadata (not adjustable).
Configuration changes take up to 15 minutes to propagate, so a widget that "didn't pick up the change" usually just needs a cup of tea.

When to use / skip

Chat is the channel almost every Customer Service project ends up doing first, and rightly so — it is the only digital channel where Microsoft supplies both ends of the pipe, so there is no third-party account, no phone number procurement and no provider contract to negotiate. If the client has a website with meaningful support traffic, put chat in.

Skip it, or at least defer it, if the client's web estate is a brochure site with no signed-in area, because unauthenticated chat gives you a stranger typing into a box and a representative doing manual customer lookup — which is worse than email for handle time. Also defer if the plan is "chat instead of phone" without any deflection layer in front; you will simply move the same volume onto a channel where each representative handles three or four at once and everyone complains about quality. The right shape is usually a Copilot Studio agent taking first contact with escalation to a human, which the chat channel supports natively including handing over the transcript.

Configuration decisions

Authenticated or unauthenticated chat. This is the single biggest one: authentication drives contact identification, persistent chat, and whether pre-chat survey data is trustworthy. It needs a JWT endpoint and a public key URL from whoever owns the website.
How much you ask in the pre-conversation survey versus how many customers abandon before submitting it. Every field is a drop-off.
One widget or several. Separate widgets per brand, per language or per product line each get their own workstream and their own routing, which is cleaner than one widget with heavy classification rules.
Whether a Copilot Studio agent fronts the widget, and what the escalation trigger is.
Which user features go on: file attachments (and therefore an antivirus and storage conversation), video, screen share and co-browse (and therefore a third-party contract).
Whether the widget hides outside operating hours or stays visible with an out-of-hours automated message.

Gotchas

Content Security Policy on the client's website is the most common go-live failure for chat. The snippet loads Microsoft-hosted script and connects to Microsoft endpoints; if the security team hasn't allowlisted them, the widget silently doesn't render and nobody notices until UAT.
Retro-fitting authentication after go-live is painful. Persistent chat and reliable customer identification both hang off it, and adding it later changes the customer-facing flow.
Browser hardening and tracking prevention break the widget quietly rather than loudly. Test in the client's managed browser build, not just your own Edge.
Pre-chat survey answers arrive as context variables. They are available to routing rules and to the representative, but they do not populate a case on their own — someone has to build that mapping.
On Power Pages, portal caching can keep serving the old content snippet after you update it. Clear the cache before concluding the snippet is wrong.
Screen sharing and co-browse are not included capabilities. They need a separately licensed provider, and clients routinely assume they are in the box because they appear as toggles in the admin UI.

Consultant notes

Demo bot-to-human escalation with the transcript carried across. That is the moment the client stops comparing you to their existing chat vendor on price.
Get the CSP change and the JWT endpoint onto the web team's backlog in week one. They are external dependencies and they are always the long pole.
Push back hard on long pre-chat surveys. Two fields and an authenticated session beats eight fields and a 40% abandon rate.
Before go-live, check the telemetry attribute against the client's privacy position, and confirm with their DPO that chat transcripts and their retention are covered in the privacy notice.
Agree the out-of-hours behaviour explicitly. "Hide the widget" and "show a message" are both defensible, but the client should choose rather than discover it.

Worth revisiting when the chat widget version bumps or if co-browse and video move to a first-party provider.