Respond to a customer requesting a feature that isn't planned

A customer emails:

"Any plans to add multisite network support? I run 40 sites on one WP install
and really need this to work across the whole network, not per-site."

ROADMAP REALITY: [not planned for the next 12 months; the architecture would need
a near-total rewrite of the licensing system to support it; a workaround exists
using per-site activation but it's genuinely more manual work]

Write the reply, as the support lead who also relays product feedback.

Requirements:
- Say clearly that it's not currently planned, with the actual timeframe ("not in
  the next 12 months," not "no plans at this time" left permanently vague).
  Vague non-answers just generate a follow-up ticket in 3 months asking the same
  thing.
- Give the real reason in one sentence (architecture, not "resources" as a
  catch-all excuse), since a real reason is more credible than a boilerplate one.
- Offer the actual workaround, honestly described as more manual, not oversold as
  "just as good."
- Log the request internally, mention that you're doing this, so the customer
  knows it's tracked even though it's a no, and ask one clarifying question about
  their use case if it would genuinely help product prioritize later.
- Don't promise it'll happen "eventually" unless that's actually true.

Replace the customer message and ROADMAP REALITY block with your real situation
before running this.