Editing and removing knowledge base entries
How to update, replace, or delete facts in a building’s knowledge base.
Your knowledge base is meant to change as your building does. Editing it is quick, and updates take effect for new conversations right away.
A knowledge base is a living document, codes rotate, policies evolve, amenities open and close, and its value tracks how faithfully it mirrors reality. The mechanics of editing are trivial; the discipline is what matters. This page covers both: how to make each kind of change, and the habits that keep changes from leaving debris behind.
- Edit a fact: open the building’s knowledge base, find the entry, and update the text
- Replace a document: re-upload the new version; Rezi re-indexes it automatically
- Remove a fact: delete the entry so Rezi stops referencing it
Editing a fact
Open the building’s knowledge base from its Properties page, find the entry (search by any word in it), and change the text. The edit is indexed immediately, the next guest question on that topic gets the new answer. While you’re in there, give the entry a quick quality pass: is it specific, self-contained, and phrased the way guests ask? An edit is a free chance to make a mediocre entry great, see writing entries that work.
Replacing a document
When a house manual or welcome guide gets a new version, upload the new file and remove the old one. Rezi extracts and indexes the new content automatically. The removal half is the part people skip, and it’s the dangerous half: two versions of the same manual means two versions of every fact that changed between them, and the AI has no way to know the 2024 edition lost the argument. One document, one truth.
Removing a fact
Delete entries for anything that’s no longer true, the amenity that closed, the promotion that ended, the local spot you stopped recommending. Deletion takes effect immediately. If you’re hesitating because the information might come back (a seasonal pool, say), you can instead edit the entry to describe reality: “The pool is closed for the season and reopens Memorial Day weekend” is more useful than either keeping the summer entry or deleting it outright.
Remove the old before adding the new
When a policy changes, delete or update the old entry rather than just adding a new one. Two contradictory facts are the most common cause of inconsistent answers.
Habits that keep it clean
Make the update part of the change itself: new lock code, update the entry before you leave the property; new pet policy, edit the entry the day it takes effect. If a team member owns building operations, they own the entries too, edits are tracked, so activity history shows who changed what. And once a season, skim the whole knowledge base top to bottom; ten minutes of reading catches the drift that no single escalation ever surfaces.
Do edits affect conversations already in progress?
Can I bulk-edit or export the knowledge base?
Who on my team can edit knowledge?
Is there a history of past versions?
Was this article helpful?