- An active membership in the intended WRKZY organization
- Enough context to describe the problem or desired outcome safely
- Any screenshot cropped to remove unrelated customer data and secrets
Open Feedback & roadmap
Open Feedback from the workspace navigation, or open Command Lens and choose Feedback & Roadmap. The workspace has three views:
- Share feedback creates a new private submission.
- Your team’s feedback shows submissions from your organization, WRKZY replies, attachments, and any linked product decision.
- Roadmap shows only product items WRKZY has deliberately sanitized and published.
If Feedback is unavailable, confirm you are signed in to the intended active organization. The feature may be introduced to customer organizations in stages.
Share useful feedback
- Choose Share feedback.
- Give the submission a short title and describe what happened in your own words. Include what you were trying to do and where the workflow helped or broke down.
- Choose whether it is a problem, feature request, improvement, something you like, or another kind of feedback.
- Select the impact that best matches the current effect: blocked, slowed down, inconvenient, or an idea for later.
- Optionally describe the outcome you wanted.
- Optionally attach up to three PNG, JPEG, or WebP screenshots, each no larger than 5 MB.
- Review whether to include basic technical details. When enabled, WRKZY receives the current page address, application version, and browser—not page content or customer messages.
- Choose Send feedback and wait for the saved confirmation.
The automated receipt confirms that WRKZY saved the submission. A person reads every submission and replies in the company-visible thread within two business days. The automated receipt itself is not the human acknowledgement.
Keep private information out of screenshots
Your original wording, clarification thread, technical context, and screenshots remain private to active members of your organization and authorized WRKZY staff. They are not copied into the published roadmap.
Before attaching an image, crop or redact unrelated customer names, messages, phone numbers, email addresses, commercial terms, and records from other workspaces. Never attach passwords, one-time codes, invitation links, session data, access tokens, API keys, private keys, or payment information.
Continue the company conversation
Open Your team’s feedback to see the submission and its current state. Other active members of the same organization may see this company feedback.
- Received means the submission is saved and awaiting a human response.
- We replied means a WRKZY team member acknowledged it.
- On the roadmap means WRKZY linked it to a sanitized, published product item.
- Resolved or Closed records the outcome of the private submission.
Use Add context to answer a WRKZY question or provide a relevant update. Add new context to the existing submission instead of creating duplicates for the same issue.
Understand roadmap linking
WRKZY may connect several private submissions to one canonical product decision. Only the sanitized title, summary, product area, status, explanation, and official updates can appear on the roadmap. Raw customer wording, company identity, screenshots, private notes, internal rationale, and AI suggestions remain private.
Not every submission becomes a roadmap item. Support counts are evidence, not votes, and one serious customer problem may outweigh many lightweight suggestions. Planned communicates intent without promising a delivery date.
| State | Meaning |
|---|---|
| Considering | WRKZY is still evaluating the problem and evidence |
| Planned | WRKZY intends to address it, without promising a date |
| Building | Work is actively in progress but may still change |
| Shipped | The published update records what became available |
| Not planned | WRKZY has decided not to pursue it and explains why |
Support and follow an update
On a published roadmap item:
- Choose Support when the underlying problem matters to your organization. Supporting an item also follows it.
- Choose Follow when you want updates without adding organizational support.
- Use Settings → Notifications to control Customer Voice in-app and email updates.
- Unfollow an item when you no longer want notifications. Removing support does not automatically unfollow it.
Following keeps you informed about published status explanations and official updates. It does not reserve delivery, change priority automatically, or create an ETA.
Verify and recover
- Submission saved but a screenshot failed: the written feedback remains saved. Crop or convert the image, confirm it is under 5 MB, and add the missing context in the company thread if upload remains unavailable.
- Submission is missing: confirm the active organization and refresh Your team’s feedback. Feedback belongs to the organization, not only the workspace from which it was sent.
- No roadmap item appears: this can be expected. Only reviewed and deliberately published decisions appear, and WRKZY may need clarification before linking feedback.
- Support or follow does not update: refresh once and retry. If it still fails, preserve the item title, approximate time, and visible error without copying private submission details into a general support request.
- Feedback contains a secret or unrelated customer data: stop adding context and contact WRKZY Support with the submission identifier so the authorized team can apply the appropriate removal process.
- Correct organization confirmed
- Problem and desired outcome described
- Impact selected without exaggeration
- Screenshots cropped and free of secrets
- Saved receipt visible
- Human reply tracked in the company thread
- Published item supported or followed only when relevant
- Planned status not treated as a delivery date