Request a Response

Benefits

The Request a Response (RaR) feature allows researchers to formally request an update on a submission from either Bugcrowd’s triage team or customer when the submission needs attention. Using RaR promotes timely communication and helps submissions progress smoothly toward resolution.

The Request a Response feature enables you to:

  • Ask a follow-up question about your submission.
  • Request a re-evaluation of the submission’s status or decision.
  • Provide new or additional information relevant to the finding.

This feature helps maintain transparent, two-way communication between Researchers and Customers.

Eligibility

You can open a RaR for submissions in the following substates: Triaged, Unresolved, Resolved, Not Applicable, Out of Scope, Not Reproducible, and Informational.

Please note: The “Not Applicable” substate is available only for requests directed to Bugcrowd, not Customers.

Limits

  • Account Active Limit: You are allowed a limited number of open RaRs simultaneously. This limit is visible within the platform (e.g., “Account active limit: 1 of 2 available”).
  • Submission Limit: Each submission can have a maximum of two (2) RaRs opened throughout its lifecycle.

Limits Example: When one of your open RaRs is resolved, it frees up 1 active account slot allowing you to open a new RaR, but permanently counts as 1 of your 2 allowed requests for the specific submission.

How to Request a Response

  1. Locate the Submission: Go to the submission that requires an update.
  2. Open the Request: Click “Submit a request” within the submission view.
  3. Confirm: Review the prompt and confirm your request. Once submitted, the relevant party (Bugcrowd or Customer) is notified automatically.

Request a response UI Example UI: Submit a request screen with RaR quota shown

Tracking and Managing Requests

Finding Active Requests

  1. Go to the Submissions page under the Work tab.
  2. Use filters or search tokens to find active requests:
    • Requested-to:present – View all submissions with an open RaR.
    • Requested-to:none – View submissions without active RaRs.
    • requested-to:bugcrowd or requested-to:customer – Filter by recipient.

Visibility and Quota Tracking

  • The platform displays your remaining RaR quota or the entire account (e.g., “Account active limit: 2 of 2 available”) and also for the specific submission lifecycle (e.g., Submission limit: 1 of 2 available).
  • For each active RaR, you can view the date it was created, so you can track how long it has been open.

Activity Tracking

All RaR activity, including openings and responses, is tracked in the submission’s Activity for full visibility. An open RaR remains active until it is resolved. It requires at least one response to be answered, and can receive multiple responses. It is not closed automatically by a timer, so your request stays open until it is answered.

Tips

  • Use RaR thoughtfully – clear, concise requests are more likely to receive fast, constructive responses.
  • Avoid opening multiple requests on the same issue unless you have new information to share.
  • Check your Activity for updates before opening another RaR.