Request a Response (RaR)

• Benefits of Request a Response
• How to Request a Response
• Tracking and Managing Requests

The Request a Response (RaR) feature allows a Researcher to formally request a timely update on a submission from the Bugcrowd or customer triage team when the submission needs attention.

Benefits of Request a Response

The Request a Response feature enables a Researcher to request a response on a submission from Bugcrowd or a Customer and can be helpful in the following scenarios:

• If you have more questions.
• You need your submission re-evaluated.
• You have additional information to provide.

How to Request a Response

1. Locate the Submission: The Researcher should navigate to the specific submission on which they need an update.

   • Eligibility: The Researcher can request a response on submissions in the following substates: Triage, Unresolved, Resolved, Not Applicable, Out of Scope, Not Reproducible, and Informational.

   • Note on ‘Not Applicable’: This substate is not an option for requests directed to Customers.

   • Limit: The Researcher can request a response only twice on a single submission.

2. Open the Request: The Researcher should look for the Request a Response button or link within the submission interface.

3. Confirm: The Researcher must confirm their decision to open the request. The request is immediately logged, and the relevant triage team is notified.

Tracking and Managing Requests

• Finding Active Requests: The Researcher can use the submission filtering options on their main Submissions page, found under the Work tab, to easily find all submissions that currently have an open Request a Response.

• Using Tokenized Filters to Search:
  • On the Submissions page, type requested-to: in the search box.
  • Select the requested-to:present option to view all submissions where the Researcher has requested a response.
  • The Researcher can also filter submissions further using requested-to:none, requested-to:bugcrowd, or requested-to:customer.

• Quota Limit: The system clearly displays the Researcher’s remaining quota (e.g., “1 of 2 requests remaining”).

• Time Limit: If a response is not provided, the Request a Response will automatically expire after 10 business days.

• Expiration: When a request expires, the Researcher’s quota is immediately returned, allowing them to open a new one. The expiration is noted in the submission’s Activity Log, and the Researcher will receive an email notification.

• Status Visibility: The Researcher will see the time remaining until the 10-business-day expiry period ends for any active RaR. All RaR actions (opened, responded, expired) are logged in the Activity Log.

---