Question

Difficulty: MediumCase Capture Mechanisms (Web-to-Case and Email-to-Case)

An administrator is preparing Salesforce for an upcoming promotional event and wants to ensure support operations remain functional if customer inquiries spike. The administrator needs to verify how Salesforce handles web-generated cases if the organization exceeds its daily Web-to-Case limit.

Which statement accurately describes the system behavior when the daily Web-to-Case submission limit is exceeded?

  1. Submissions over the limit are rejected from online record creation, and the submitted case information is emailed to the Default Case Owner.Answer
  2. B
    Surplus case requests are held in a temporary system buffer and automatically created as Case records when the daily limit resets.
  3. C
    The Web-to-Case form display is automatically disabled, rendering an error message to end users until an administrator raises the limit.
  4. D
    Overflow submissions are automatically converted into Tasks assigned to the System Administrator for manual case creation.

Answer

Submissions over the limit are rejected from online record creation, and the submitted case information is emailed to the Default Case Owner.
When an organization exceeds its daily Web-to-Case submission limit, Salesforce halts automatic case record creation in the database. To prevent customer inquiry loss, the system generates an email notification containing the submitted form data and sends it directly to the email address associated with the Default Case Owner specified in Web-to-Case settings.

Step-by-Step Solution

1
Identify the daily limit mechanism for Web-to-Case in Salesforce.
Salesforce imposes a maximum limit of 500 Web-to-Case submissions per 24-hour period (unless additional capacity is granted).
Governor limits ensure system stability across multi-tenant environments.
2
Determine the fallback mechanism configured in Web-to-Case settings.
Salesforce routes overflow submission data via email notification to the specified Default Case Owner rather than creating database records.
This prevents data loss during high-volume spikes while maintaining database governor limits.

Key Concept

Web-to-Case Daily Limits and Overflow Handling
Rate this question