A Salesforce administrator is configuring automated case intake mechanisms to meet specific organizational security, infrastructure, and volume requirements. Match each case capture mechanism to its corresponding technical architecture or operational capability.
- Web-to-CaseGenerates HTML code for website submission forms, enforcing a default daily limit of 5,000 requests and forwarding overflow submissions to the default case owner.
- On-Demand Email-to-CaseProcesses incoming customer email messages entirely within the Salesforce cloud infrastructure, supporting maximum message sizes up to 25 MB.
- Email-to-Case AgentRequires software installed behind the corporate firewall to keep email traffic behind the network perimeter and allow processing of attachments larger than 25 MB.
Answer
Web-to-Case matches with generating web form HTML with a default 5,000 daily request limit and default owner overflow routing. On-Demand Email-to-Case matches with processing emails entirely in the Salesforce cloud with a 25 MB maximum size limit. Email-to-Case Agent matches with requiring software installed behind the network firewall to keep traffic internal and handle attachments larger than 25 MB.
Web-to-Case provides HTML code generation with a 5,000 daily request ceiling and routes overflow to the default owner. On-Demand Email-to-Case processes emails up to 25 MB completely in the Salesforce cloud. Email-to-Case Agent uses installed software inside the corporate firewall to keep network traffic internal and handle attachments exceeding 25 MB.
Step-by-Step Solution
Key Concept
Case Capture Mechanisms (Web-to-Case and Email-to-Case)