Pre-launch checklist

Five minutes here saves you from a guest getting a wrong answer on day one. Walk through this list for each property before you publish the number.

The logic of the checklist is simple: the moment you put the number in your check-in instructions, Rezi is speaking for you. Every item below exists because skipping it has burned a real host, a stale WiFi password shared with a guest at midnight, an emergency escalation pointed at an old phone, a booked date that Rezi quoted as available. None of them take long to verify, and together they cover the failure modes that actually happen.

Knowledge base

• WiFi network name and password are correct
• Check-in / check-out times and instructions are accurate
• Parking, trash day, and amenity details are filled in
• House rules and quiet hours are included

Accuracy beats completeness. A missing fact makes Rezi escalate to you, mildly annoying, self-correcting. A wrong fact makes Rezi confidently tell a guest the old door code, much worse. As you review, prioritize verifying what’s there over adding more. Anything that rotates, codes, passwords, seasonal hours, deserves a second look, and a habit: whenever it changes in real life, update the entry the same day.

AI configuration

• Emergency keywords are configured (water leak, no heat, lockout, smoke)
• Escalation contact is a number you actually monitor
• Calendars are connected so Rezi never quotes a booked date

The escalation contact is the one to triple-check. Everything else on this list degrades gracefully if it’s wrong; a dead escalation path means a 2am emergency goes nowhere. Confirm the number in Settings → Notifications is a phone someone actually watches after hours, and if you have a team, consider an on-call rotation so it isn’t always the same person.

Test like a guest

Text the property number at least five real questions, a WiFi question, a check-in question, a parking question, an emergency keyword like a leak, and something you intentionally did not put in the knowledge base. Confirm the emergency alerts you and the last one escalates to you rather than guessing.

If voice answering is enabled, also place a test call: confirm the greeting names the right property, ask a question, and say something that should trigger an escalation. Voice and text share a brain but are configured separately, see setting up voice, so each deserves its own test. Double-check that calendar feeds are connected and a recently booked date shows as unavailable.

Activate, then verify

When you activate a property, you pay and Rezi provisions its dedicated number, but it does not go live to guests right away. It enters Setup, and two short checks confirm it works before any guest can reach it. Rezi texts your host phone a code that you reply with, and you call the number and say a secret word. Both are required and both expire, so do them in one sitting. The moment they pass, the property flips live automatically. The practice testing above happens during this Setup window, on the real number. Step-by-step in verifying your building.

After you launch

Going live isn’t the finish line, it’s the start of a short tuning period. Expect a handful of escalations in the first week as guests ask things you didn’t anticipate. That’s the system working: each escalation shows you exactly which fact to add, and hosts who clear them weekly see escalations drop sharply within a month.