AI resident messaging for TheHouseMonk
TravelPal connects to TheHouseMonk with the API host and the Authorization value Monk Tech support issues for your account, then answers residents inside the support tickets they raise in your own branded resident app. It reads your units, the homes leased from them, and every lease on those homes, including residents already months into a contract and residents under notice. Anything it holds for a person goes on that same ticket as a team-only comment the resident never sees.
One connection, running both ways. Every item on it is detailed below.
What TravelPal reads from TheHouseMonk
TheHouseMonk is run by co-living and build-to-rent property management companies, mostly in India, Southeast Asia and the Middle East, renting by the bed and by the month rather than by the night.
Units, and the homes leased from them
TheHouseMonk keeps the physical unit and the leased home as two separate records, and TravelPal reads both: address, locality, bedrooms, bathrooms, the building form, and the amenities switched on for that unit. Photos are held as file keys rather than image links, and a unit carries no check-in time and no house rules, so the guidebook is built from what your team writes rather than from the unit record.
A lease is the stay, not a booking
A stay here runs in months and years: a move-in date, the lease's stated end, and the status on it, from move-in pending through under notice to moved out, with only a cancelled occupancy dropped. TravelPal takes any lease that overlaps the period it is filling in, so connecting in month seven of a one-year contract still brings in the resident standing in the unit today. Nothing arrives from a booking channel, because there is none: leases are contracted directly with you, and somebody still in TheHouseMonk's booking pipeline stays a lead until they move in.
Every resident of a shared home, separately
A co-living home holds several residents at once, each with their own move-in date and their own end. Each one becomes its own stay, and nothing is ever addressed to the home, so a housemate never receives another resident's message. Residents under notice are asked for by name rather than dropped, because their departure is the nearest one in the portfolio and the one most worth getting right.
Residents keep one identity across units
TheHouseMonk numbers a resident once and the number survives a shift from one unit to another, so somebody who moves within your building is recognized rather than met as a stranger. Their ticket history is found by the person and never by the home, which is what keeps a housemate's thread out of it. Owner-occupied homes arrive marked as owner-occupied, so an owner living in their own unit is not handled like a tenant.
Tickets, and both sides of them
The ticket TravelPal answers in is an open or in-progress one, and it comes in with its comments: TheHouseMonk keeps the resident-visible comments separate from the team-only ones, so the concierge knows what the resident was told and what was only said about them. Bank details, identity numbers and lease documents on a resident's record are dropped before anything reaches the knowledge base. TheHouseMonk sends no notifications of its own, so TravelPal checks for new tickets and new comments on a schedule.
What TravelPal writes back
Every message goes out through TheHouseMonk, never around it, so your own inbox shows exactly what each guest was told.
Replies inside the resident's own ticket
The ticket in your branded resident app is the one place TheHouseMonk can reach a resident, and that is where TravelPal answers: a resident-visible comment on the ticket they raised. It lands in the same ticket queue your team already works in, so the concierge adds a voice there rather than a second inbox nobody opens.
Team-only comments on the same ticket
TheHouseMonk has a real resident-invisible comment type, and it reads back separately from the resident-visible side. Where TravelPal is not sure, it holds the thread for a person, puts what it already knows in that note, and asks your team, and the resident never sees any of it.
The lease is left where it is
Rent, dates and contract terms are an agreement between you and your resident, and TheHouseMonk carries an occupancy inside the home record rather than as an editable booking. TravelPal writes comments and nothing else: no date change, no charge, and no figure on anybody's ledger, since a monthly rent is not a stay price.
Connected in four steps
TheHouseMonk switches API access on for your account, and TravelPal does the rest itself.
Ask Monk Tech for API access
One email to your account manager at Monk Tech Labs, the company behind TheHouseMonk. Ask for two things: the API host your account is served from, and the Authorization value for it. The host is usually api.thehousemonk.com, but TheHouseMonk is deployed white-labeled, so have support confirm yours rather than assuming the standard one.
Paste the host and the header value
Both go into TravelPal exactly as support sent them, including a Bearer prefix on the Authorization value if it came with one, because TravelPal adds nothing to what you paste. The pair is checked against your own unit list before the connection is saved, so a wrong paste is caught there rather than the first time a resident writes.
Set the time zone on each building
This is the one property field you fill by hand, because TheHouseMonk states no time zone anywhere on a unit. Do it before anything is scheduled: every timed message and your quiet hours read it.
Units and leases import
Your units become properties, every occupancy on every home becomes its own stay, and tickets raised from then on reach the concierge. TheHouseMonk's own list pages stop at 3,000 homes in one pass, so tell us before you connect if your portfolio is larger: the import stops and says so rather than quietly bringing in part of your buildings.
The dashboard shows the connection the whole way: connected, last sync, and any error in plain words. The rest of going live is covered in what onboarding involves.
What the TheHouseMonk connection will not do
Every property management system draws its own lines, and the ones TheHouseMonk draws are worth knowing before you switch anything on. TravelPal works inside them rather than around them.
The resident starts the conversation
There is no conversation object in TheHouseMonk. There are support tickets, and only a resident opens one, so TravelPal cannot write first: the move-in introduction, the unprompted offer and the reminder have no route on this system. What it does instead is answer every ticket a resident raises, at any hour, for the length of the lease.
One rail, and it is the resident app
Residents' email addresses and phone numbers are on file in TheHouseMonk and neither makes them reachable: the system carries no free-text email, SMS or WhatsApp send. TravelPal answers on the ticket or not at all, rather than promising a resident something on a rail their system will not deliver.
No time zone exists in the record
Nothing in TheHouseMonk says what time it is at a building, which matters more here than on a short-stay system because these portfolios sit in India, Southeast Asia and the Middle East. Until you set each property's zone in TravelPal, anything scheduled is timed for US Eastern.
An open-ended lease waits for an end date
A lease with no move-out date and no contract end date on its terms is left alone rather than given one. Move-out messages, deposit deadlines and everything else timed off a departure would otherwise fire on a date the resident never agreed to. Put the end date in TheHouseMonk and that resident is picked up on the next sweep.
Where the AI is not sure, it stops and asks your team rather than guessing. That is the same on every system: see the guardrails.
TheHouseMonk integration FAQ
Does Monk Tech have to switch anything on before TravelPal can connect?
Yes, and it is one email to your account manager. Monk Tech support issues the API host your account is served from and the Authorization value for it, because TheHouseMonk is deployed white-labeled and both are set per account rather than published. You paste the two into TravelPal and they are checked against your own unit list on the spot.
Can TravelPal message a resident before they open a ticket?
No. A conversation in TheHouseMonk is a support ticket and only a resident raises one, so there is nowhere for the concierge to write first. From the moment a resident opens a ticket, TravelPal answers it at any hour, including the nights and weekends when nobody is at your desk, and keeps answering for the length of their lease.
Will my team see what the concierge told a resident?
Yes. Every reply is posted as a resident-visible comment on the ticket in TheHouseMonk, so your own console holds the whole thread. TheHouseMonk also has a team-only comment type, so notes for your staff and anything TravelPal holds for a person sit on that same ticket where the resident cannot see them.
What happens to residents whose lease has no end date?
They are left out until the lease has a stated end, either a move-out date on the occupancy or a contract end date on the terms. Open-ended leases are normal in this product, and inventing a departure for one would schedule a move-out message for a date nobody agreed to. Add the date in TheHouseMonk and that resident is picked up on the next sweep.
Not the system you run?
TravelPal connects to 33 property management systems. These are the ones nearest TheHouseMonk in how widely they are used.
Updated