Identity
The basics Aria opens with. The property name appears in the greeting and across the admin UI.
Floor plans and amenities
The detail Aria uses to answer “what’s available?” and “what comes with the apartment?” Long-form free text is fine — Aria reads naturally from it.
Floor plans (detail) List every plan with bedroom count, bath count, square footage, and rent range. Bullets or paragraphs both work — Aria reads it as context, not a script.
Amenities (detail) Community amenities (pool, gym, parking, EV charging) and in-unit features (washer/dryer, appliances, finishes). Specifics beat generics.
Fees, specials, pet policy, awards
Fees Application fees, admin fees, deposits, pet fees — anything one-time.
Current specials Update when promotions change. If you keep this current, Aria can quote them confidently.
Pet policy What's allowed, breed/weight limits, fees, rules. Aria gets a lot of pet questions — be specific.
Awards / recognition Local awards, ratings, press. Optional but useful when a prospect asks 'how do you compare to the others?'
Pricing posture
Controls how confidently Aria quotes pricing. If you have an approved live source, fill it in. If you leave it blank, Aria quotes the rent ranges from your floor plans as starting prices and always says “the leasing team can confirm” before committing.
Approved pricing source E.g. 'website rents at brookridgeheights.com/floor-plans, refreshed daily' or 'Entrata feed (Phase 2).'
Routing
Where Aria sends maintenance emergencies and existing residents. The emergency line is the most safety-critical handoff in the product — make sure it’s correct.
Compliance & operations
Recording, retention notices, daily digest, error alerting, SMS follow-up. Each is opt-in — defaults are conservative.
Recording disclosure Spoken at call start when recording is on. Keep short. Default: "This call may be recorded for quality."
Transfer to human + voicemail
When Aria isn’t sure or the caller asks for a real person, the system warm-transfers to your transfer number during business hours, or captures voicemail otherwise. Without a transfer number set, Aria falls back to capturing a callback request.
Voicemail greeting Spoken before the beep. Leave blank for a sensible default.
Area knowledge
The “long-time local” knowledge — what makes Aria sound grounded instead of like a generic chatbot reading FAQs. Aria references this only when a caller asks about the area; she won’t lecture unprompted. Empty sections are skipped entirely.
Neighborhood overview The block, the side of town, the vibe. What's it like to live here? Demographics OK to include but not required.
Major employers nearby Companies prospects are likely commuting to. Include rough drive times if you know them.
Schools District names, notable schools, ratings. Aria uses this when families call. Mention that exact school assignments depend on address — leasing team confirms.
Shopping Malls, plazas, grocery, big-box — what's in walking or driving distance.
Dining Notable restaurants nearby. A few specifics beat a long generic list.
Parks and recreation Parks, trails, gyms, sports venues, weekend destinations.
Transit and commute Bus, airport, highways. Drive times to the major employers callers are likely heading to.
Quick selling points A short hit-list version of the above. E.g. 'East-side Bloomington · 5 min to Eastland Mall · 8 min to State Farm · easy I-55.'
Local color
Free-form context that makes Aria sound like she actually lives here. Cultural notes, regional vocabulary, things a long-time local would know but a stranger wouldn’t. Aria reads this as background, not a script — the prompt explicitly tells her to use it sparingly so it doesn’t feel performative.
Local color Examples: names of local newspapers, twin-city dynamics, weather realities, in-jokes, sports teams, historical notes.
Extra guardrails
Optional. Free-form rules appended to Aria’s system prompt. Use this for things like “never quote rents without saying ’starting at’” or “always offer the leasing team’s email for written follow-up.”