Brief sales and support on a feature before it launches

Write an internal launch brief about the feature below for {{teams}}, so they can explain it to customers accurately on launch day and know where its limits are. They will skim it once before launch and come back to it when a customer asks something, so it has to be easy to scan.

Feature facts (spec, release notes, design notes):
"""
{{feature_facts}}
"""

Launch details (date, who gets it, plans or regions, pricing): {{launch_details}}
Known limitations and bugs at launch: {{limitations}}
Questions customers have already asked about it: {{customer_questions}}
How to reach the product team with questions: {{escalation_route}}

Use these headings:
1. In one sentence: what customers can now do.
2. Who it is for, and who it is not for.
3. How it works: up to five steps from the customer's side.
4. What it does not do: each limitation stated plainly, with the workaround if there is one.
5. Availability: who gets it, when, and on which plans.
6. Questions and answers: 8 to 12 likely customer questions, each with a short answer a rep could say out loud.
7. When to escalate: which questions or problems go to the product team, and how.

Keep it under 700 words. Answers should sound like a knowledgeable colleague, not marketing copy: short sentences, no superlatives.

For example, a good answer to a limitation question reads: "Not yet. Exports cover the last 12 months only. If a customer needs older data, open a ticket and support will run it by hand." This example shows the form only; use the real facts.

Do not invent features, dates, prices, plans or roadmap promises, and never say a limitation "will be fixed soon" unless the facts above give a date, because reps repeat what they read to customers. If something a rep will certainly be asked is not covered by the facts, add it to a final list headed "Need an answer before launch" instead of guessing.