Write the FAQ your customers actually ask

Below are real customer messages. Build the FAQ they justify.

Steps:
1. Cluster the messages by underlying question, not by wording. Show cluster sizes.
2. For each cluster with 3+ messages, write the FAQ entry: the question phrased the way customers phrase it (not the way we'd phrase it), and an answer under 90 words that leads with the answer, then the caveat, then the next step.
3. Separately list questions that reveal a product or docs problem rather than an FAQ gap — these should be fixed, not answered.
4. Flag any question we currently answer inconsistently across the messages.

No marketing language. No "Great question!".

MESSAGES:
{{paste 20-100 support messages}}