Connect Webless conversations to Slack, Microsoft Teams, or Webex Contact Center.
Human handoff lets a visitor ask for a person from the Webless widget. The
visitor stays in the widget. Your team replies from Slack, Microsoft Teams, or
Webex Contact Center.
Webless carries the transcript and page context into the provider, then sends
human replies back to the same visitor conversation.
Use Microsoft Teams when agents or teammates work from a team channel. A Teams
tenant admin must install or approve the Webless app before the channel can
receive handoff requests.
Use Webex Contact Center when routing, business hours, agent assignment,
transfers, and closeout should stay in Webex.Webless does not replace Contact Center routing. Webless creates the bridge from
the widget into Webex, then Webex owns the contact-center workflow.
Webex digital channels, Webex Connect, or Engage enabled for your tenant.
A LiveChat asset for the website.
A website domain added to that LiveChat asset.
A Contact Center queue, entry point, team, or flow target for Webless
handoffs.
Agents who can accept and reply to the queued task.
For production, your Webex admin authorizes the Webless service app. You do
not need to create a separate Webex developer service app unless Webless
support asks you to for a sandbox test.
In Human Handoff, choose Webex Contact Center and authorize the
Webless service app from a Webex admin account.
Confirm tenant and region
Confirm the Webex tenant and region that should receive handoffs.
Create or select the LiveChat asset
In Webex Contact Center, use the LiveChat asset that represents the website
where the Webless widget runs.
Add the website domain
Add the exact website host to the LiveChat asset, for example
example.com or support.example.com. Do not include https:// or a path.
Map the Contact Center target
Map the LiveChat asset to the queue, entry point, team, or flow that should
receive Webless handoffs.
Save the target in Webless
Return to Console and select the Webex target. The setup steps should show
as complete.
The domain step is required. If the website domain is missing or does not match
the visitor page, Webex can reject the conversation before an agent ever sees it.The Webless setup screen separates what Webless needs from what should remain in
Webex Contact Center.
Confirm handoff is enabled in Webless Console and that the provider
connection is active.
Slack does not receive handoffs
Confirm the Webless Slack app is installed in the workspace. For private
channels, also confirm the app has been invited to the selected channel.
Slack authorization fails
Make sure you selected the correct workspace and that your Slack account can
install apps. If app installs are restricted, invite a Slack workspace admin
from Console.
The Teams bot does not appear in a channel
Ask a Teams admin to confirm Webless Handoff is uploaded, allowed, and
added to the target team. Then open Agents and bots in the channel and
search for Webless Handoff.
The Teams setup command does not connect
Make sure the message mentions @Webless Handoff and includes the current
setup code from Webless Console.
Webex accepts setup but no agent task appears
Confirm the LiveChat asset has the exact website domain, the Contact Center
target is mapped to a live queue or flow, and at least one agent can receive
that task type.
Webex reports the domain is invalid
Open the LiveChat asset website settings and add the exact host where the
Webless widget runs. Use example.com, not https://example.com/page.