TravelPal for TheHouseMonk resident teams
TravelPal passes the support tickets residents raise in your resident app to your team. It connects with the API host and Authorization value that Monk Tech support gives you.
TravelPal does not reply to guests in TheHouseMonk yet. Your team does. Each item is explained below.
What TravelPal reads from TheHouseMonk
Co-living and build-to-rent property management companies run TheHouseMonk, mostly in India, Southeast Asia and the Middle East. They rent by the bed and by the month, not by the night.
Units, and the homes leased from them
TheHouseMonk keeps the physical unit and the leased home as two separate records. TravelPal reads both: address, locality, bedrooms, bathrooms, the building form, and the amenities switched on for that unit. Photos are stored as file keys, not image links. A unit has no check-in time and no house rules. So the guidebook is built from what your team writes.
A lease is the stay, not a booking
A stay here runs for months or years. It has a move-in date, the lease's stated end, and a status. The status runs from move-in pending through under notice to moved out. Only a cancelled occupancy is dropped. TravelPal takes any lease that overlaps the period it is filling in. Say you connect in month seven of a one-year contract. TravelPal still brings in the resident who lives there today. Nothing arrives from a booking site, because there is none. You sign leases directly with residents. Someone 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 has their own move-in date and their own end date. Each one becomes a separate stay. Nothing is ever sent to the home as a whole. A housemate never gets another resident's message. TravelPal asks for residents under notice by name and does not drop them. Their departure is the nearest one in your portfolio, and the one most worth getting right.
Residents keep one identity across units
TheHouseMonk gives a resident one number, and the number stays the same when they move to another unit. A resident who moves inside your building is recognized, not treated as a stranger. Their ticket history is found by the person, never by the home. That keeps a housemate's thread out of it. Owner-occupied homes arrive marked as owner-occupied. An owner who lives in their own unit is not handled like a tenant.
Tickets, and both sides of them
TravelPal reads a resident's open or in-progress ticket, and the ticket comes in with its comments. TheHouseMonk keeps resident-visible comments apart from team-only comments. So TravelPal knows what the resident was told and what was only said about them. TravelPal drops bank details, identity numbers and lease documents from a resident's record. This happens 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 to TheHouseMonk
Here is what TravelPal sends through TheHouseMonk today, and what it leaves to your team.
TheHouseMonk tickets go to your team
The ticket in your branded resident app is the one place TheHouseMonk can reach a resident. TravelPal adds no comment to that ticket today. It puts the resident's ticket in your team's TravelPal inbox and emails your team. A person on your team answers the resident in TheHouseMonk.
Team-only comments are read, never written
TheHouseMonk has a real comment type that residents cannot see. It is read back apart from the resident-visible side. TravelPal does not write team-only comments on TheHouseMonk tickets today.
The lease is left where it is
Rent, dates and contract terms are an agreement between you and your resident. TheHouseMonk keeps an occupancy inside the home record, not as a booking you can edit. TravelPal writes nothing into TheHouseMonk today. It changes no date, makes no charge, and writes no figure on anyone's ledger. A monthly rent is not a stay price.
Connected in four steps
TheHouseMonk turns on API access for your account. TravelPal does the rest itself.
Ask Monk Tech for API access
Send 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 ask support to confirm yours and do not assume the standard one.
Paste the host and the header value
Paste both into TravelPal exactly as support sent them. If the Authorization value came with a Bearer prefix, keep it. TravelPal adds nothing to what you paste. TravelPal checks the pair against your own unit list before it saves the connection. So a wrong paste is caught there, not the first time a resident writes.
Set the time zone on each building
This is the one property field you fill in by hand. 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. Tickets raised from then on reach your team. A lease added after you connect is read at the next check, within about an hour. TheHouseMonk's own list pages stop at 3,000 homes in one pass. If your portfolio is larger, tell us before you connect. The import stops and says so, and it does not quietly bring in only part of your buildings.
TravelPal shows the connection at every step: connected, last update, and any error in plain words. To see the other setup steps, read what onboarding involves.
What the TheHouseMonk connection will not do
Know the limits of TheHouseMonk before you turn anything on. Every property management system has its own limits. TravelPal works inside them, not around them.
The resident starts the conversation
TheHouseMonk has no conversation object. It has 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. Today TravelPal does not answer those tickets either. TheHouseMonk does not tell TravelPal when your team replies. So TravelPal cannot see that your team already answered the resident.
One rail, and it is the resident app
TheHouseMonk holds residents' email addresses and phone numbers, but neither one makes a resident reachable. The system has no free-text email, SMS or WhatsApp send. TravelPal uses no route outside the ticket. It does not promise a resident something in a way their system will not deliver.
No time zone exists in the record
Nothing in TheHouseMonk says what time it is at a building. This matters more here than on a short-stay system. These portfolios sit in India, Southeast Asia and the Middle East. Until you set each property's time 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 in its terms is left alone. TravelPal does not give it one. Otherwise, move-out messages and deposit deadlines would fire on a date the resident never agreed to. So would everything else timed from a departure. Put the end date in TheHouseMonk before you connect. An end date added later is not read today.
When TravelPal's AI is not sure, it stops and asks your team instead of guessing. This rule is the same on every system: see the safety guardrails.
TheHouseMonk integration FAQ
Does Monk Tech have to switch anything on before TravelPal can connect?
Yes, and it takes one email to your account manager. Monk Tech support gives you two things. They are the API host your account is served from and the Authorization value for it. TheHouseMonk is deployed white-labeled, and both are set for each account and not 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 TravelPal has nowhere to write first. Once a resident opens a ticket, TravelPal emails your team about it.
Who answers a resident's ticket in TheHouseMonk?
Your team does, today. The concierge writes no reply and no team-only comment there. Your own console holds the whole thread.
What happens to residents whose lease has no end date?
They are left out unless the lease has a stated end when you connect. That is either a move-out date on the occupancy or a contract end date in the terms. Open-ended leases are normal in this product. If TravelPal made up a departure, it would schedule a move-out message for a date nobody agreed to. A date you add after the connect is not picked up today.
Not the system you use?
TravelPal connects to 33 property management systems. Below are the systems closest to TheHouseMonk in how widely they are used.
Updated
TheHouseMonk is a trademark of its owner. TravelPal is not affiliated with or endorsed by TheHouseMonk.