CC&Rs on demand: Celeste for HOA management

Nobody reads the CC&Rs until the day they suddenly care, and then they do not read them either. They email the management company. Can I paint my door this color. What is the fence height limit. Do I need approval for a shed. When is the pool open. An association manager with a portfolio of communities answers these all day, each answer already written in a governing document the homeowner has owned a copy of since closing.

This is close to an ideal queue for Celeste: the questions repeat, the answers are written down, and the asking happens at night and on weekends when homeowners are actually home looking at the fence.

The governing documents become the desk

Ingest each association’s CC&Rs, bylaws, architectural guidelines, and amenity rules, and the agent answers homeowner email and website chat from what those documents actually say. Not a paraphrase from memory of a similar community, and not two different answers from two different staff members. The same clause, cited consistently, for the fortieth asker as for the first.

Communities differ, and the knowledge is kept per association, so the answer about fence height in one community never leaks into another’s. When a document is silent, the agent does not fill the gap with something plausible. It says the documents do not address it, routes the question to your team, and logs a named knowledge gap so the answer gets written once.

Architectural requests arrive complete

The architectural request is the classic half-finished submission: an owner emails “I want to build a deck” with no drawings, no dimensions, no materials. The agent runs the intake your guidelines require, dimensions, materials, placement, drawings or photos, and what reaches the committee is a complete submission instead of a three-week correspondence about what a complete submission is. The agent explains the process and the timeline; the decision belongs to the committee and never to the agent.

Dues are records, so identity comes first

“What do I owe” gets a real answer, but only to the right person. A homeowner verifies their identity, and every lookup runs scoped to their own account by code outside the AI. No neighbor sees another lot’s balance, and an unverified sender gets no account data at all. Anything past status, payment plans, hardship, disputes about a charge, goes to a person with the context gathered.

Some subjects should never get an automated reply in a community, and you decide which. Put “violation,” “fine,” “lien,” “attorney” on the escalation keyword list, and a message containing one is barred from an autonomous answer and held for your staff, flagged with the word that tripped it. Board-only material, collection procedures, enforcement discretion, legal posture, lives in private playbooks the agent follows but never recites, and outgoing drafts are mechanically scanned to keep it that way.

One community, one topic at a time

Start in shadow mode on one association’s inbox and read the drafts against real homeowner questions. Amenity hours and rules questions typically graduate first, architectural intake next, dues status once verification has proven itself. Every topic has its own dial per your comfort, and the escalation list is live in every mode.

For a management company, this is portfolio math. Homeowner questions scale with doors; your staff does not. Every rules question the documents already answer is one that never needed a coordinator, and the manager’s day gets back the hours the fortieth fence question used to take.

See how it works or the product. The trial starts silent, so you can watch it answer one community’s real questions before it sends a word.