A support administrator is evaluating automated case intake mechanisms using Web-to-Case and On-Demand Email-to-Case. Which two statements correctly describe the native capabilities and architectural behavior of these case capture tools? (Select 2)
- When the daily Web-to-Case request limit is exceeded, Salesforce emails the submitted case information to the Default Case Owner instead of creating a Case record.Answer
- BIf a Web-to-Case submission fails custom field validation rules, the case record is created and placed into a system holding queue for administrator review.
- On-Demand Email-to-Case processes incoming emails using Salesforce cloud services without requiring an agent application installed behind the corporate firewall.Answer
- DOn-Demand Email-to-Case supports processing individual email attachments up to 100 MB in size.
- EStandard Web-to-Case HTML forms natively support file attachment fields without requiring custom Apex or third-party tools.
Answer
The statement regarding daily Web-to-Case limit overflow sending emails to the Default Case Owner and the statement regarding On-Demand Email-to-Case relying on cloud services without a local server agent are both correct.
Exceeding daily Web-to-Case request limits causes submitted case details to be emailed directly to the Default Case Owner instead of creating database records. Additionally, On-Demand Email-to-Case handles incoming emails entirely through Salesforce cloud infrastructure via forwarding, eliminating the need to install and maintain an on-premises Email-to-Case Agent.
Step-by-Step Solution
Key Concept
Web-to-Case and Email-to-Case Architecture and Limits