Send and track support feedback

Question

Staff finds a bug, missing feature, or needs product/support help from inside SquareOS.

Steps

• Use the in-app support/feedback entry point from the affected route so route, module, browser/app version, tenant, gym, and actor context are captured.
• Choose the correct category: Bug, Feature request, Support request, or General feedback.
• Write a factual message with expected result, actual result, affected person/invoice/job/provider, and timing. Attach a screenshot/file only when it does not expose secrets.
• Submission requires a staff session. The backend records actor name, location ids, brand id, gym id, route, module, browser info, app version, metadata, and optional attachment.
• Managers/platform support can filter feedback by brand/status and move status through Open, Acknowledged, Resolved, or Dismissed.
• Use Audit Trail and the support.feedback.submitted.v1 outbox event when support needs proof that the report was created.

Correct outcome

Support receives reproducible context, staff can see that the report was captured, and status changes are auditable.