Section 4 · AI Agents · 35% of exam
4.9 Connecting Agents to Digital Experience, Email, Voice, and Slack
Exam objective
Explain how Agentforce agents connect to supported channels and identify setup considerations for digital experiences, email, voice, and Slack.
Channels and connections
A channel is the platform, application, or interface through which a user interacts with an agent. Salesforce lists options such as the Agentforce panel, mobile, Slack, messaging platforms, email, and voice. Channel support varies by agent type and connection. A connection provides channel-specific instructions and response formats so the agent can reason and respond appropriately. An adaptive response format can structure output as text, links, buttons, images, or other supported components. Therefore, connecting an agent is more than placing a chat window on a page: the channel, response format, routing, identity, and supported capabilities all affect the user experience.
Digital experiences and messaging
For a website or mobile experience, select a supported Enhanced Chat or messaging setup for the intended agent type. A customer-facing service agent can be connected to enhanced messaging channels, while some employee agents can be deployed through an Experience Cloud site. Messaging conversations may use Omni-Channel flows to route the session to an agent and transfer the conversation to a person or another destination. Configure inbound and outbound routing where needed, and decide how escalation should work if the agent cannot resolve a request. Test the actual channel because its structured responses, identity context, and transfer behavior can differ from Builder Preview.
Email, voice, and Slack
Agentforce Service agents can handle service email inquiries when the email channel is configured. Voice-enabled service agents use Agentforce Voice and a telephony setup. These channels have distinct response and operational requirements: email is asynchronous, while voice needs real-time turn-taking and appropriate telephony routing. Salesforce documentation identifies Slack connection support for Employee agents; do not assume every agent type supports every channel. Review the supported connection for the target agent type and the required licenses or features. A standard connection may include behavior and response-format instructions that help the agent adapt to that channel.
Deploy and test the whole experience
A channel deployment typically requires enabling the feature, adding a connection, configuring the channel, routing, access, and agent activation. Salesforce notes that messaging and email agents use Omni-Channel flows, and that an outbound flow can route or escalate a conversation. For Slack, connect Salesforce and Slack, add the supported connection, grant user access, and complete setup in Slack. Test with representative users and devices. Check that responses render correctly, the right records are created, conversation context is preserved, and escalation reaches the intended queue or representative. Confirm that the agent’s actions are appropriate for the channel’s authentication and user permissions.
TIP: Confirm the agent type first, then choose a supported channel connection and configure the routing and response behavior required by that channel.
Channel availability changes by agent type and release. In Salesforce Help, verify current support for the exact combination of agent, channel, license, and connection.
Extra concept: A messaging or email connection can involve Omni-Channel flows in addition to the agent’s topics, actions, and response instructions.
Official references:
- Deploy Your Agent to Channels https://help.salesforce.com/s/articleView?id=ai.agent_surfaces.htm&language=en_US&type=5
- Set Up Connections in Agentforce Builder https://help.salesforce.com/s/articleView?id=ai.agent_connections_set_up.htm&language=en_US&type=5
- Connect an Agent to Slack https://help.salesforce.com/s/articleView?id=ai.agent_deploy_emp_slack.htm&language=en_US&type=5
Key takeaways
- Channels are user-facing surfaces; connections adapt agent behavior and response formats for those surfaces.
- Messaging and email can require Omni-Channel routing; voice requires supported telephony setup.
- Verify channel support for the target agent type and test the deployed experience, access, and escalation.
