From Email-to-Case to the Boardroom: How Inherited Agents Break Governance Built for Software
Oct 19, 2026
Artificial Intelligence / Enterprise Security
In Salesforce Agentforce, the recommended way to make an agent respond to events is a Flow: a record is created or a case is updated, and the Flow passes data into the agent's prompt. Separately, Email-to-Case and Web-to-Case turn inbound customer messages into case records; it is how airlines and hotels run support intake. Both are standard, documented, as-designed features. Chained together, they produce this path: public internet → email → case record → agent prompt → agent action → case comment → outbound reply An unauthenticated outsider now has a route into an internal agent's instructions, and the agent's reply leaves through the same door. Nothing was misconfigured. The finding, documented by researchers in August 2026, is a clean example of how agents that arrive inside existing platforms fail: through the application around them, not the model inside them. The risk is in the application, and the application is the thing nobody re-reviewed Which intake fea...