Match each Salesforce case capture mechanism to its corresponding architectural design or operational behavior.
- Web-to-CaseGenerates HTML form code for website placement and sends overflow submissions beyond daily request limits to the default case owner via email.
- On-Demand Email-to-CaseConverts customer emails into cases entirely through Salesforce cloud infrastructure without requiring behind-the-firewall application installation.
- Email-to-Case AgentRequires an executable service installed behind the company network firewall to process emails locally and support attachments up to 25 MB.
Cevap
Web-to-Case matches with generating HTML form code and routing daily overflow to the default case owner. On-Demand Email-to-Case matches with processing emails entirely in the cloud without local software installation. Email-to-Case Agent matches with requiring an executable installed behind the firewall to keep traffic internal and process large attachments.
Web-to-Case creates web forms and sends overflow submissions exceeding daily limits to the default case owner. On-Demand Email-to-Case routes emails through Salesforce cloud servers without local software. Email-to-Case Agent requires local software installed behind the corporate firewall to keep network traffic internal and process large attachments.
Adım Adım Çözüm
Anahtar Kavram
Salesforce Case Capture Mechanisms (Web-to-Case vs. On-Demand Email-to-Case vs. Email-to-Case Agent)