Open the customer's request and read the description and discussion before choosing a response. The right next step depends on whether you need more detail, already offer the feature, have a duplicate request, or have made a decision.
Use an internal comment for team discussion. Customers cannot read internal comments. If you use AI to draft a reply, check the instructions and promises before posting it.
For example: "You can do this from the export menu. Choose CSV to download the list. Here are the steps: [help link]. Does that cover the data you need?"
You can create an Already available status for this. It is not a default status. Open Settings → Content organization → Statuses → Add status, choose the board it belongs to, and leave Unlisted off. Then use that status on the request.
Unlisted means customers cannot see the post on boards, find it in search or open its direct link. This includes the person who submitted it. Admins keep access. Some templates make Won't Do unlisted by default, so check before using it for a response the customer should be able to revisit.
For the full setting, see unlisted statuses.
Check that the requests describe the same need. If they do, merge the duplicate into the existing request. Votes and discussion are combined, and the old link leads to the remaining post. Review the target carefully because merging cannot be undone.
Use linked posts instead when requests are related but should keep separate discussions.
Reply with the decision and a short reason. Include a workaround if you have one. Move the request to a visible status such as Declined if you want the customer to keep access to the explanation. Create that status if it does not exist and leave Unlisted off.
If you need to stop new customer comments while preserving the answer, lock the comments. This leaves the existing discussion readable to people who can access the post. You can pin your answer so it stays above later activity.
Link the request to roadmap work and explain the next step you have decided on. Avoid a delivery date unless your team is ready to share it. When the feature ships, update the request's followers.
Public comments can trigger email without waiting for a digest, but following and notification preferences affect delivery. A reply to a comment and a new top-level comment have different recipients. See comment and mention notifications.
A status update has its own Email followers choice. Review it before confirming the change. Keeping the request visible lets the customer return to your answer even if no email arrives. Check the customer view and use Delivery history when investigating a specific message.