The group wants pet owners to reach the Service agent directly from the branded pet-owner portal they already log into to view records and pay invoices. Which channel connection fits this requirement?
Select an answer to reveal the explanation.
Short Explanation
Owners are already logged into the portal to see their pet's records and pay a bill. Don't send them somewhere else to talk to the agent, put the agent right there on the page they're already standing on.
Full Explanation
Connecting the Service agent to a digital experience channel means embedding it directly inside the Experience Cloud portal the owners are already authenticated into, so the conversation happens in the same branded, logged-in context where they view records and pay invoices, with no extra channel to reach. That is the intended fit whenever the requirement explicitly describes an existing portal experience. Slack is a channel built for messaging-app-based conversations, typically internal staff or occasionally external partners with Slack access; it is not the natural fit for a branded self-service portal owners already use, and choosing it here would fragment the owner experience across two different surfaces. Email is a valid, separate channel for asynchronous, inbox-based interactions, but it is a poor match when the requirement specifically describes owners already inside a live, authenticated portal session; routing them out to email would be a step backwards in that context. Agent API is for embedding an agent into a custom or external application via API calls, typically when there is no existing Salesforce-hosted surface to extend, such as a future native mobile app, but the scenario describes a portal that already exists and can be extended directly, making a digital experience channel connection the more direct and appropriate answer.