Report an issue

Issue reports, routed with precision.

If something behaved incorrectly, capture the context clearly and QC can route it to the right fix path faster.

Product informationUpdated April 2026

What needs attention?

Start with the closest issue area. QC uses it to route your report toward delivery, account, or product behavior triage before the team reviews the details.

Response timing

Delivery-impacting bugSame-day triage

Account-blocking bugWithin 24 hours

General product bugWithin 24–48 hours

Priority is based on delivery impact, account blocking severity, and whether the issue affects core product behavior.

Report basics

Start with the account and issue category involved. QC uses this to send the report into the right triage lane before review begins.

Account emailUse the email tied to the QC account involved.Issue typeChoose the closest match so your report can be routed correctly.Delivery outcomeUse the closest result so delivery triage starts with the right assumptions.

When and where

Tie the report to the moment, route, and device context where the issue actually happened.

Time issue occurredUse your local time if exact timestamp data is not available.Affected moment ID (optional)Include it if the issue is tied to a specific scheduled or delivered moment.Page or route (optional)Useful when the issue only appears in one part of QC.Device and browserFor example: iPhone 16 Pro, Safari 18.

What happened

Capture the issue clearly. Focus on what happened, what you expected, and what occurred instead.

Issue titleA short summary makes triage easier.DescriptionThe clearer your description, the faster the review can be routed and reproduced.

Steps to reproduceList the sequence clearly so the team can recreate the behavior.Additional environment detailAnything extra that may explain why the issue appears in this environment.Expected behaviorWhat should have happened instead?Actual behaviorDescribe the issue as it actually appeared.

Add context

Optional, but screenshots or recordings often shorten investigation time significantly.

Choose a screenshot or recordingPNG, JPG, MOV, or MP4. Keep files under 20 MB when possible.

Choose file

Submit report

Clear reports move faster. QC triages by impact, reproducibility, and whether delivery or access is affected.

View system status

Reports are reviewed based on severity and product impact.

What issue reporting covers

This page is for reproducible bugs, broken flows, incorrect delivery behavior, visual glitches, and product behavior that does not match the intended QC experience.

If the issue is urgent and tied to a live delivery problem, use Support Contact so it reaches the right queue immediately.

Prefer direct contact?

If reporting through the form is unavailable, send the issue directly with the same details.

vera@qcapp.co