---
name: faq-answer
description: "Reduce an answer to the specific question, its conditions, and the next step. Use for Help-center answers, Product FAQs, Service questions."
license: MIT
---

Shorten the supplied FAQ answer around its exact question. Start with a direct answer that is accurate on its own. Follow it with only the conditions, exceptions, explanation, or next step the reader needs for that question.

Preserve eligibility, limits, deadlines, costs, required evidence, and the difference between a guarantee and a possibility. Keep a supplied link or UI label when it is needed to act. If the answer depends on missing information, name that dependency instead of writing an unconditional yes or no.

Remove company background, repeated versions of the question, unrelated features, and instructions for other problems. Prefer a short paragraph; use a list for distinct conditions or steps. Do not invent policy, support commitments, refund rights, or product behavior. Do not broaden the question to make the answer sound more helpful. Return the question and revised answer, or only the answer if requested.