Service Agent connections to digital experiences
Key Takeaway
A Service agent reaches an Experience Cloud site through three linked pieces. An Enhanced Chat messaging channel is one. Routing sends that channel's conversations to the agent. An embedded service deployment places the chat on the site.
Visitors on a website or Experience Cloud site talk to a Service agent through Enhanced Chat, a messaging channel that shows a chat window on the page. Setup links the channel to the agent through routing. An embedded service deployment then places the chat on the site. How you build the routing depends on whether the channel uses Enhanced Chat v1 or v2.
Three linked pieces
A Service agent connection to a site has three linked pieces:
- Messaging channel: defines the type of chat, such as Enhanced Web Chat.
- Routing: sends the channel's conversations to the agent.
- Embedded service deployment: puts the chat window on the site.
An agent can connect to many inbound channels, but each inbound channel can connect to only one agent.
Routing must never send a conversation to a service rep and an AI agent at the same time. When a bot and a rep are both engaged, the messaging session can get stuck in Waiting or Inactive status.