Pet owners frequently email the clinic's general inbox asking about invoice details or requesting a refill, and staff want the Service agent to read incoming messages, draft accurate replies grounded in the owner's records, and route anything sensitive to a human. Which channel configuration matches this requirement?
Select an answer to reveal the explanation.
Short Explanation
The most direct answer to "owners keep emailing us" is to let the agent live where the email already is, not build a relay through Slack or a custom polling script to get it there the long way round.
Full Explanation
Connecting the agent directly to the email channel lets inbound owner messages become a native conversational input for the agent, so it can read the request, ground a reply in the owner's actual records, and hand off to a human whenever the content warrants it, without any intermediate relay. This is precisely the built-in channel designed for asynchronous inbox-based interactions like the scenario describes. Building a nightly scheduled batch Flow addresses a completely different pattern, a one-way broadcast of generic updates, not a responsive, grounded, two-way conversation replying to specific inbound requests, so it does not satisfy the requirement at all. Manually forwarding emails into Slack introduces an unnecessary staff-dependent relay step and abandons the native email channel entirely for a workaround that adds latency and human effort exactly where automation is wanted. Polling a mailbox from a custom external script via the Agent API reinvents a channel connection Agentforce already provides natively; Agent API is the right tool when there is no existing Salesforce-native channel to use, which is not the case here since email is a supported channel connection point directly on the agent.