An administrator is evaluating intake mechanisms to capture customer support inquiries into Salesforce. Match each Case Capture mechanism or configuration setting to its corresponding architectural capability, limit, or deployment requirement.
- Web-to-CaseGenerates HTML code for external sites, enforces a default daily request limit of 5,000 cases, and redirects overflow to an email notification.
- On-Demand Email-to-CaseProcesses incoming emails directly through Salesforce cloud infrastructure without local software, supporting attachments up to 25 MB.
- Email-to-Case (Installed Agent)Requires installing an executable application behind the company firewall to manage email traffic locally, supporting attachments up to 100 MB.
- Default Case CreatorSpecified automated user or administrator assigned as the owner of cases created via web intake when assignment rules fail to match.
Cevap
Web-to-Case matches with the generation of HTML forms for external sites enforcing a 5,000 daily request limit. On-Demand Email-to-Case matches with processing emails directly through Salesforce cloud infrastructure with a 25 MB attachment limit. Email-to-Case (Installed Agent) matches with requiring an executable application behind the firewall supporting up to 100 MB attachments. Default Case Creator matches with the automated user assigned as owner when assignment rules fail to match.
Each feature corresponds to its specific architecture: Web-to-Case relies on standard HTML forms with a 5,000 daily request limit; On-Demand Email-to-Case routes emails through Salesforce cloud services up to 25 MB per email; Email-to-Case (Installed Agent) runs local software inside the company firewall supporting up to 100 MB attachments; and the Default Case Creator serves as the fallback owner for cases when rule criteria are not met.
Adım Adım Çözüm
Anahtar Kavram
Salesforce Case Capture Architecture and Limitations