BBugRelayby Rizaklabs
☰
FOR AGENCIES AND CLIENT TEAMS

Keep client feedback close to the fix.

Give clients a clear way to show an issue, and give your developers the context to work with it.

AGENCY WORKFLOW

Separate projects. Clear boundaries.

Keep client websites and staging environments in their own projects. Scope member access to the projects they need.

AGENCY WORKFLOW

Invite clients with the right role.

Use read/comment access for external reviewers, and reserve assignment, triage and sharing controls for contributors.

AGENCY WORKFLOW

Replace the back-and-forth.

Keep reproduction steps, labels, assignment and discussion next to the screenshot, recording and diagnostic evidence.

A PRACTICAL CLIENT REVIEW
  1. 01Create a project for the client website.
  2. 02Invite the client with the project scope they need.
  3. 03Capture and review a report with visual evidence.
  4. 04Assign a developer and discuss the reproduction.
  5. 05Close the loop with a scoped link or configured delivery.
Understand project permissions
FOR THE PEOPLE ON BOTH SIDES OF THE ISSUE

Different roles.
Same clear picture.

From the first client review to the final release check.

01 / AGENCIES & CLIENTS

Make feedback actionable.

Give every client website its own project. Keep feedback, visual evidence and the next conversation together.

Built for your handoffs
02 / DEVELOPERS

Start with context.

See the steps, inspect selected console and network events, and connect the report to a configured GitHub repository.

Explore the evidence
03 / QA & PRODUCT

Keep the review moving.

Capture a broken interaction, assign the report, and follow its status through the team’s workflow.

Follow the workflow
Your websiteReviewed capture
BBugRelayCONTEXT, CONNECTED.
GitHub issuesEmail notifications

Available with configured integrations and selected delivery.

LESS COPYING. A BETTER HANDOFF.

Keep the context.
Move the work.

Your report is the starting point. Connect GitHub and email, choose the details to include, and track delivery from the workspace.

Explore integrations
CONTEXT IS USEFUL. CONTROL IS ESSENTIAL.

A little more deliberate.
A lot more considered.

Choose when capture starts, review what goes out, and decide who gets to see it.

Explore security & privacy

You press start.

Explicit capture. Visible recording state. A clear stop control.

You review the evidence.

Select diagnostics. Mask screenshot pixels. Approve video separately.

You choose the audience.

Private reports, project permissions and expiring, revocable links.

LESS BACK-AND-FORTH. MORE CONTEXT.

Your next bug report
can explain itself.

Start with your workspace