How Product Feedback Is Collected, Reviewed, and Answered
This page explains, in practical terms, where to send product input, how that input is triaged, how updates are communicated back, and how the feedback process itself is judged. It is written as a neutral template: replace the bracketed owner variables with the current publisher's confirmed details before publication.
Why user input matters
For a product-led team with limited resources, user input is not a courtesy — it is a primary source of direction. Engaged customers surface friction, unmet needs, and opportunities that internal roadmaps can miss. The goal is to collect that input efficiently, spot recurring pain points, and turn the most valuable ideas into shipped improvements for everyone, rather than treating each comment as an isolated request.
Feedback forum
{{OWNER_FEEDBACK_FORUM_NAME}} is available around the clock for submissions. Reach it from your account through the “Feedback” link at the bottom of the page. Typical topic areas include: Gantt View, Calendar View, List View, Board View, Exporting & Sharing, Resourcing / Workloads, Time Tracking & Estimation, Account Management, Application Performance, Mobile App, Integrations, and Reporting — but any other observation is also welcome. The product team reviews incoming posts on a weekly grooming cadence ({{OWNER_FEEDBACK_REVIEW_CADENCE}}), so new items are triaged rather than left unexamined.
Satisfaction survey
An in-page survey may appear at the bottom of the page asking for a satisfaction rating on a 1–10 scale ({{OWNER_SURVEY_SCALE}}). The score and any free-text comments go to the product team. Responses are checked daily, and anything flagged as high priority is escalated to the wider product team and leadership ({{OWNER_SURVEY_MONITORING}}).
Chat and email
Start live chat through the “Let’s chat” link in the bottom-right corner of the product, or write to {{OWNER_SUPPORT_EMAIL}}. Live support is offered {{OWNER_SUPPORT_HOURS}}. Customer Success aims to reply promptly ({{OWNER_SUPPORT_RESPONSE}}). If you have not already posted in the forum, the team will log your feedback there on your behalf so the product team can see it. Anything classified as a defect is handed to engineering for resolution ({{OWNER_BUG_ROUTING}}).
How updates are communicated
Feedback only works if the loop is closed. When a release addresses a forum post, its status is updated in {{OWNER_FEEDBACK_FORUM_NAME}}, and anyone who voted on or commented on that request receives an email notification ({{OWNER_UPDATE_NOTIFICATIONS}}). If you are actively working with Customer Success on an issue, you will be told when there is an update or when it is resolved ({{OWNER_ISSUE_UPDATE_NOTIFICATIONS}}).
How success is measured
A feedback process should be judged by whether it is responsive and whether it leads to shipped change — not by volume alone. The measures used here are: how many forum posts receive a reply each week, and how many requested features reach production ({{OWNER_SUCCESS_METRICS}}). Tracking both keeps the team accountable for answering people and for converting good ideas into product improvements.
Quick checklist before you submit
Before you send feedback, run this quick check: (1) Is this a new idea, a vote on an existing request, or a bug? (2) Which view or feature area does it affect? (3) Can you describe the outcome you want, not just the problem? (4) Have you searched the forum first so duplicates can be consolidated? Answering those four questions makes your input easier to triage and more likely to be acted on.