Reply to a customer's feature request you cannot promise

Write a reply to the customer's feature request below, for a support or success agent to review and send. The customer should come away knowing exactly where their request stands, feeling heard, and with the best option they have today.

The customer's message:
"""
{{customer_message}}
"""

Where the request stands, from the product team or our roadmap notes (not planned, under consideration, planned with no date, or similar): {{status}}
Workarounds or existing features that cover part of the need: {{workarounds}}
How we track requests, and whether we tell customers when something ships: {{tracking}}

Write the reply in three short paragraphs:
1. Restate what they want to achieve in their terms, which shows we understood the goal behind the request.
2. Say plainly where it stands, using only the status above, and what that means for them.
3. Offer the workaround with numbered steps if there is one, and say what happens to their request next.

Keep it to 90 to 160 words of plain text, signed "{{agent_name}}".

Do not promise or hint at a release date, a timeline or that the feature will be built unless the status says so, because a vague "soon" becomes a broken promise. Avoid "Great suggestion!" and "I'll pass this along to the team" with no follow-up. Do not discuss other customers or what competitors offer.

For example, a status sentence with the right honesty: "This isn't on our plan for this year, so I don't want to give you false hope. I've added your use case to the request so the product team can see why it matters."

If the status is unknown or blank, write the reply without a status in paragraph 2 and add a first line, "FOR THE AGENT: confirm the status with the product team before sending." If the request is really a bug, or something the product already does, say so in that line instead.