The record of how Propflow has changed.

Every inbound SMS is checked for regulated keywords before it reaches Clara. STOP, START, and HELP are answered by a fixed, non-AI handler — the tenant gets the legally required response, the opt-out state is recorded, and Clara is not invoked on that message. Consent is captured and logged at sign-up with IP, user-agent, and timestamp, and every inbound is validated against that record. There is no path where the AI can accidentally reply after an opt-out, because the AI never receives the message.

What happens

Opt-out keywords answered by fixed code, not the AI

Consent record

IP, user-agent, and timestamp captured at sign-up, checked on every inbound

On opt-out

Tenant receives the legally required reply; Clara is not invoked

Audit

Every inbound logged with the intercept verdict before any AI processing

Before Clara sends any reply on a leasing or tenant thread, the message is screened for protected-class topics — every Fair Housing dimension listed in the spec below, including the state-extended ones. If the screen trips, that reply is not sent. Clara politely tells the tenant she can’t weigh in on that topic and keeps the conversation moving toward what she can help with. This runs on every turn, on every thread, automatically. Compliance isn’t a vibe or a prompt wish — it’s the answer to “what does Clara literally do when a prospect asks about neighborhood demographics.”

When it runs

Before every outbound reply, on every thread

Scope

Leasing and tenant threads alike — same rules in both modes

Protected dimensions

Race, color, national origin · Religion · Sex (including sexual orientation and gender identity) · Familial status (families with children, pregnant persons) · Disability · Age · Marital status · Source of income, including housing vouchers

Jurisdiction

The same check runs on every thread — including the classes that are state- or locally-extended rather than federal, such as source of income

On a trip

Clara declines politely and redirects; the unsafe reply is never sent

Every action Clara takes on a thread — every lookup, every decision, every vendor contact, every work-order change — is persisted alongside the human-readable messages. Property managers open any thread in Propflow and replay exactly what Clara did, in order, with the inputs she used and the results she got back. We treat the audit trail as a product surface, not as hidden logs — you can walk a compliance reviewer through Clara’s reasoning turn by turn, in plain language.

What’s captured

Every action, every input, every result — per turn, with timestamps

Scope

Same audit applies to leasing and maintenance threads

Retention

For the life of the customer relationship; deleted on offboarding

Visibility

PM dashboard → conversation detail → expandable Clara audit log

Every work order Clara opens, every tour she schedules, every vendor she dispatches, every outbound reply she drafts — all of it lands in the PM dashboard and can be paused, edited, reassigned, or rolled back. Clara isn’t a black box that acts on your property without you. She’s an operator whose every move you can see, approve, and change. Trust an agent the way you’d trust a new hire: let her run, check the work, intervene when your judgment disagrees.

What can be overridden

Every work order, tour, vendor dispatch, and outbound reply

How to intervene

Approve, edit, reassign, or roll back from the conversation or work-order view

On pause

Clara stops acting on that thread; a human takes over without losing context

Audit ties in

Every override is logged alongside Clara’s original action