At a high level, once a Service agent has been built and tested with its topics and actions, what is the correct general process for making it available to owners through a new channel such as the group's mobile app, without pinning the answer to a specific menu path or button label?
Select an answer to reveal the explanation.
Short Explanation
Wiring up a new channel is turn it on, make sure identity is set up right for that channel, then actually test it end to end. The topics and actions you already built don't need a rebuild, they just need a new door to walk through.
Full Explanation
The durable, channel-agnostic process is: enable the channel for the agent and configure it, make sure the identity and authentication context appropriate to that channel is established, such as an authenticated Experience Cloud user for a portal or app, and then verify behaviour end to end once real traffic can flow, since a channel can introduce its own quirks even when the underlying topics are unchanged. This mirrors how the objective is phrased, as a process, deliberately without anchoring to a specific setup screen or button, because those details shift release to release while the underlying steps stay stable. Rebuilding every topic and action for the new channel is unnecessary and wasteful; topics and actions are largely channel-agnostic configuration, and a new channel is an additional delivery surface, not a reason to start over. Channels do not connect themselves automatically on activation; connecting a channel is a deliberate, explicit configuration step a specialist performs. And channel connection is not restricted to newly created agents or to a single agent type; an existing, already-live Service agent can absolutely be extended to additional channels over its lifetime, which is a routine part of iterating on a deployed agent.