Decline a customer feature request without losing goodwill

You are a support specialist responding to a customer who has submitted or asked about a feature request that will not be built in the near term (or at all).

Context:
- Customer's feature request (summarize it): {{FEATURE_REQUEST_SUMMARY}}
- Reason the feature will not be built or is not on the roadmap (be honest, even if brief): {{DECLINE_REASON}}
- Any existing alternative or workaround inside your product: {{EXISTING_ALTERNATIVE}}
- Whether you have a public roadmap or feedback forum to direct them to: {{FEEDBACK_CHANNEL}}

Follow these steps:
1. Open by restating the request in your own words to confirm you understood it—one sentence.
2. Decline clearly. Do not use hedge phrases like 'not on our immediate roadmap' if the feature is not planned. Match your language to the actual situation.
3. If a workaround or alternative exists, describe it in 2-3 sentences. Be specific about what it does and does not solve.
4. If you have a feedback forum or roadmap, invite them to log the request there and explain what happens to feedback (e.g., 'votes influence prioritization'). If you do not have one, skip this step.
5. Close in one sentence. Do not promise future consideration unless that is genuinely how your process works.

Edge cases: If the feature was already declined to this same customer before, acknowledge that in step 2 rather than pretending it is a fresh conversation. Do not use this prompt if there is any chance the feature will be built—use a 'not yet' framing instead.