FAQs

Questions your community answers often enough to write down. Requires the FAQs entitlement.

Writing them

A question, an answer, and an optional category to group them.

Category and last-edited date on each entry.

Write the question the way residents ask it, not the way the rule is worded. "Where can guests park?" gets found; "Article 7 parking provisions" does not.

Public FAQs

Tick publicly visible to publish an FAQ on the public website. Prospective residents and buyers get the same answer without an account, which removes a large share of inbound email.

Keep the internal-only ones internal: gate codes, key collection, anything that is useful precisely because it is not public.

Where they come from

Your message history. Anything you have answered three times is an FAQ. This is the cheapest support reduction available in the product, and the most consistently neglected.

Keeping them true

Wrong FAQs are worse than missing ones, because residents act on them. Review them whenever a rule, a vendor or a schedule changes.