Does knowledge carry across buildings?
Each building has its own knowledge base, so answers are always specific to the right property.
No, each building has its own isolated knowledge base. That’s by design: the WiFi password, codes, and rules for one property should never leak into answers for another.
The isolation follows from how conversations work. Every building has its own phone number, so when a message arrives, Rezi knows with certainty which property it concerns, and it retrieves answers only from that building’s knowledge base. There is no “global pool” of facts the AI might accidentally draw from. A guest texting your beach cabin physically cannot receive the gate code for your downtown loft, the cabin’s AI has never seen it.
Why this matters
- A guest texting one building only ever gets that building’s information
- You can run very different properties under one account without cross-contamination
- The assistant’s built-in voice is the same everywhere, but facts stay per-building
Cross-contamination isn’t hypothetical, portfolios are full of almost-identical facts that differ in the details that matter. Both buildings have quiet hours, but one starts at 10pm and the other at 11pm. Both have a handyman, but different ones. If knowledge were shared, every retrieval would be a gamble on which building’s version surfaced. Isolation turns that gamble into a guarantee.
What is shared across buildings
Settings and structure, not facts. The assistant’s built-in identity is the same everywhere. Your team and roles, notification routing, and billing all live at the account level. So the assistant feels identical across your whole portfolio while its knowledge stays strictly local to each property.
Reusing common info
If several buildings share a policy, you’ll add it to each one. It’s a small duplication that guarantees every answer is correct for that exact property.
Working efficiently across many buildings
The practical pattern for portfolios: keep a master “house rules” document with your portfolio-wide policies, paste or upload it into each new building during setup, then add the building-specific facts (codes, parking, quirks) on top. When a shared policy changes, update it in each building, the scaling playbook recommends a reusable checklist so no building gets missed. It’s a few minutes of duplication per change, traded for zero ambiguity in every answer.
Can I link two buildings that share a campus?
If I delete a building, does its knowledge affect others?
Does a guest who moves between my buildings carry context?
Is there any way to share a knowledge base on purpose?
Was this article helpful?