For property managers
Your PMS runs the bookings. Homatic runs the units.
Your channel manager, pricing tool and guest messaging already handle the reservation. Nothing in that stack checks that the door locked after checkout, that the cleaner could get in, or that the AC isn’t cooling an empty unit. At ten properties someone does that by hand. At fifty, nobody does.
Homatic is the layer that sits beside the tools you already use. It reads your booking calendar, runs the locks, thermostats and sensors in every unit off it, checks its own work, and only tells you when something needs a person.
Start free — no credit card See what you get
What you get
| Feature | What it means for you |
|---|---|
| Guest access from your PMS calendar | Every reservation gets its own door code, live for that stay only. No codes typed into lock apps, and no guest told a code the lock never accepted. |
| Verified turnovers | Doors locked and confirmed after checkout, climate reset, units ready before arrival, on every booking. Fewer drive-bys to check a door. |
| Crew access | A fresh code for every clean that expires on its own. No permanent cleaner codes, and nothing to revoke when a crew member leaves. |
| One rule for every property | Set up a process once and roll it out across the portfolio. Adding unit sixty takes minutes, not an afternoon. |
| Reports from device data | Stay reports for disputes, recurring problems caught before a guest finds them, and runtime and outage history for every unit. |
| Team and owner access | Your staff get exactly the functions they run. Owners see their home without seeing guest contact details. |
| Exception-only alerts | You hear about a failed step, a leak or a dead connection, not every successful one. One person can oversee far more units. |
Arithmetic from stated assumptions, not a measured result. Substitute your own numbers.
20 properties × 8 turnovers per month = 160 turnovers. If door codes, thermostat changes and a device check take 10 minutes of manual work per turnover:
160 × 10 minutes ≈ 27 staff hours per month
It scales with turnovers, so it grows every time occupancy improves. Which parts of that are automatable at 20+ rentals →
Guest access, driven by your PMS calendar
Your PMS already knows every reservation. Homatic turns each one into access, so nobody on your team types a code into a lock app again:
- A code per reservation, created from the booking in your PMS and live from shortly before check-in to checkout, in the property’s own time zone.
- One code for every door in the unit by default, so the guest has one number to remember. You can switch to a separate code per lock.
- Sent only once the lock confirms it. A code the lock never accepted is the 11 p.m. phone call, so the guest isn’t told until the lock says it’s set.
- Removed after checkout and checked, so an old guest’s code isn’t marked gone while it still opens the door.
- Problems surface in one place: a code that couldn’t be set, or couldn’t be removed, shows on the access screen with the reason, and the second case is treated as urgent.
Nothing to migrate. Connect OwnerRez, Hostaway, Guesty or Lodgify, or paste the calendar export from Airbnb, Vrbo or Booking.com. Your PMS stays the system of record.
On Barefoot or Streamline? Both are built.
Homatic has direct integrations for the two Inhabit property-management systems most larger vacation-rental managers run on:
- Barefoot reads reservations and guest details using your Barefoot account’s own API credentials.
- Streamline reads reservations and units using your Streamline API token set. Updates sync incrementally, so a large portfolio stays within Streamline’s rate limits, and tokens are renewed automatically before they expire.
Both are in early access. We switch them on account by account, after your first sync has been checked against your real reservations, because a partly-mapped booking feed is worse than none. Email contact@homatic.ai and we’ll connect your account with you.
The turnover, handled
This is the work your team does between every stay. Homatic does it on every booking, from every channel, in every unit:
| When | What happens |
|---|---|
| Checkout | The guest’s door code stops working. The door is locked, then read back to confirm it latched. If it didn’t, Homatic retries, then texts you once. |
| After checkout | The thermostat goes to its vacant setting and the lights go off. |
| Cleaning window | The cleaner gets their own code for this turnover only, texted to them, active between stays and never overlapping a guest. |
| Before check-in | The unit is brought to temperature, and the next guest’s code goes out only after the lock confirms it. |
| You | Hear about it only when a step fails. A jammed lock is reported as jammed, not as “unlocked”. |
You set this up by describing it in a sentence (“after checkout, lock the front door and text me if it doesn’t lock”). Homatic writes the rule and checks every step against the devices that unit actually has.
Crew access: a fresh door code for every clean
A permanent cleaner code is a key you can never take back. Anyone who ever had it, whether a former cleaner, their friend or a subcontractor, can still get in. Homatic replaces it with crew access: your cleaners, maintenance techs and inspectors each get their own code for each turnover, and it expires on its own.
How crew access works
- A new code every turnover. It’s active from checkout (plus any offset you set) until shortly before the next guest, and never overlaps a stay.
- Capped in length. Set a maximum, so a long gap between bookings doesn’t leave a code working for days.
- Follows your calendar as it changes. If a booking moves or is cancelled, the crew code’s window moves or the code is revoked. It’s rechecked continuously, not set once and forgotten.
- Texted to the crew near the start of the clean, including a note of any doors or windows currently open, so they know what they’re walking into.
- Never sent until the lock confirms it, and never the same PIN as the guest’s.
- The crew can be included in your rules: “after checkout, if a window is still open, text the cleaner”.
Crew members are contacts, not accounts: no app, no login, nothing to install. Codes are issued only on locks that enforce the end time themselves (such as locks connected through Seam), so an expired crew code can’t keep working just because a deletion was delayed. The crew access guide walks through the setup with screenshots.
Set up crew access → Add your cleaner as a contact, pick the locks, and the next turnover gets its own code.
Write the rule once, not sixty times
A rule you build for one unit is usually a decision about how you run all of them. Apply it to your portfolio and Homatic finds the matching lock, thermostat or sensor in each unit. It won’t guess: every property is listed with where it stands. A unit with no leak sensor says so, and a unit with two locks asks you which one.
For alerts that span everything you own, a portfolio rule watches a kind of device rather than a specific one: “if a leak sensor goes wet at any of my properties, text me.” One rule, one phone number to change, one history. Properties without that kind of sensor are named as not covered, rather than quietly counted as dry.
Know when a connection breaks
When a lock or thermostat vendor stops answering, or an account needs reconnecting, Homatic emails you. It says which one is the problem and whether reconnecting will actually help. That way a dead thermostat doesn’t go unnoticed for two weeks just because nobody logged in.
Your team and your owners, each seeing the right thing
A management company isn’t one person with a password. Homatic gives access per job, not just read or write:
- Hand over a function, not the whole property. Bookings, guest messaging, door codes, guidebook, expenses and automations can each be assigned to a manager, and the owner steps back from that function while it’s yours.
- Owners keep their home. They always keep control of their own devices and property details. Adding devices, deleting the property and managing the team stay with the owner.
- Guest details stay with whoever runs the booking. When you manage bookings for a unit, the owner sees the stay with the guest’s first name and last initial, not their phone or email.
Reports built from what your devices recorded
Every reading your locks, thermostats and sensors send is recorded. Homatic turns that record into reports you can act on or hand to someone else. You don’t have to build dashboards or export raw data yourself.
| Report | What it tells you |
|---|---|
| Stay report | A timeline for each booking: noise that stayed above your limit, the front door opening six times in half an hour, a leak, a device that went offline, what your automations did, and who was texted when. Kept for 60 days and exported as CSV or as a claim packet for Airbnb or Vrbo. |
| After-stay email | Optional. Once a stay ends, the report arrives in your inbox with the full log attached. When there was a noise incident, it includes every door opening and unlock during the stay. A long offline stretch is flagged as possible tampering. |
| Issues from each home’s history | Patterns in each property’s own data, each with the count that backs it up: “the garage sensor went offline six times in 14 days”, “no rule watches this leak sensor”, “the front door was left unlocked overnight on 4 nights”, plus low batteries. Each one comes with a suggested rule to fix it. |
| Devices that stopped acting normal | A device that still responds but has broken from its own pattern: “reported motion on 11 of the last 14 days and none in the last 3”. |
| Runtime and uptime | How long each AC or furnace actually ran and when, compared with the temperature outside, and every outage with its duration. A failing system or a guest running the heat with the windows open shows up here before the utility bill does. |
You can also just ask. “How long was the thermostat at Unit 4 offline last week?” or “What happened during the Smith stay?” The assistant answers from the same records, for the properties you have access to.
Built for a portfolio
- Buildings, not a list of sixty names. Group units by building, complex or region, each with its own address, even when the units belong to different owners. Search finds “Unit 2” by typing 2.
- Dashboards per building. Scope revenue, arrivals and device health to one building or the whole portfolio.
- “Is the house OK?” on one screen. Jammed locks, leaks, offline devices and low batteries across every unit, with the urgent ones first.
- Every physical action is audited: locks and unlocks (by a person or an automation), door codes created or revealed, cameras viewed.
- Unusual activity is flagged: one account unlocking many doors, touching an unusual number of properties, or unlocking in the small hours of the property’s local time.
Run a pilot on one building
Connect the units, let the device summary fill in, and turn on the two or three rules that match work someone does by hand today: the checkout lock check, the cleaner code, the vacant setback. Then watch a few real turnovers. That’s the only test that matters.
The free trial runs 30 days with Starter features and no card. For more than twenty properties, or if you need SSO, custom onboarding or a security review, email contact@homatic.ai and we’ll set it up with you.
Related
Automating operations across 20+ rentals → · What gets monitored → · Guest and crew codes on your locks → · Smart home automation vs a PMS →
Common questions
Can staff be given some functions but not others?
Yes, and the model is per-capability rather than per-role: bookings, messaging, access codes, the guidebook, expenses, automations, device control and property editing are eight separate grants.
Can a manager run a function without the owner losing visibility?
A property manager can hold a function exclusively — the owner steps back from it while the manager runs it. Device provisioning, deleting a property and managing the team stay with the owner and cannot be delegated.
Is there a record of who unlocked what?
Every physical action is audited: locks and unlocks, whether a person or an automation did it, access codes created or revealed, and camera views and snapshots.
Do I have to share a vendor login with my staff?
No, and not having to is most of the reason this exists. Staff act through Homatic with the capabilities you granted, instead of through a shared SmartThings or Schlage password that cannot be scoped or revoked per person.
Can I group properties by building?
Yes. Buildings, complexes, portfolios and regions sit a level above the unit, and the dashboard scopes to one.
See Homatic on your own properties
Connect a property and the dashboard fills in from your real devices — your locks, your thermostat, your calendar. Free for 30 days on Starter, no card required.