Skip to main content

Feedback inbox

Members and admins can submit feedback from inside the app. It lands in your platform feedback inbox.

Open the inbox​

Platform → Feedback.

You'll see all submissions, sorted by newest. Each item shows:

  • Submitter (org, role, email)
  • Date
  • Type (Bug, Feature request, General feedback, Praise)
  • Subject and body
  • Attachments (if any)
  • Status (New, In review, Acknowledged, Closed)

The platform feedback inbox. The platform feedback inbox.

Triage​

Process the inbox at least weekly. For each item:

  1. Read the submission carefully.
  2. Classify if mis-categorized (bug → feature request, etc.).
  3. Respond if appropriate:
    • Click Reply to send a message back to the submitter (uses platform email).
    • Use a templated response for common issues (configure templates in Settings).
  4. Update status:
    • In review — being investigated
    • Acknowledged — noted, no action planned
    • Closed — resolved, with a note explaining the resolution

Bug reports​

For bug reports, capture:

  • Reproduction steps
  • Browser / OS / mobile platform
  • Org name (so you can reproduce in their context if needed)
  • Screenshots or attachments

Cross-reference with your engineering issue tracker. Link the issue ID in the feedback notes for traceability.

Feature requests​

Maintain a list of recurring requests:

  • Tag related submissions
  • Use the Cluster view to see how many tenants have asked for the same thing
  • Communicate decisions back ("This is on our roadmap for Q3" or "We've decided not to build this because…")

Even "no" responses are better than silence.

Patterns to watch​

  • Same bug from multiple tenants — escalate priority
  • Same feature request from large/strategic tenants — flag for product
  • Repeated feedback from a single user — may indicate frustration; reach out personally
  • Critical bugs (security, data loss) — escalate immediately, don't wait for triage

Filter by:

  • Status
  • Type
  • Org
  • Date range
  • Has attachments

Search by keyword across submissions.

Closing the loop​

When fixes ship or features launch:

  1. Filter feedback by Status = Acknowledged AND tag = [feature].
  2. Bulk Reply with the launch notification.
  3. Bulk-update status to Closed.

Members feel heard; you maintain a clean inbox.

Tips​

  • Don't let it pile up. A 6-month backlog signals you don't care.
  • Automate triage. Use templated replies for common categories (password reset, "did you try X?", etc.) to keep response time low.
  • Share patterns with the org admins. If you're seeing 30 reports of the same UI confusion, the affected orgs probably want to know about it.