AI resident messaging for Yorlet
TravelPal connects to Yorlet with the secret API key from your own Developers page. When a resident writes in the Yorlet Inbox, TravelPal alerts your team.
One Yorlet connection works in both directions. Each item is explained below.
What TravelPal reads from Yorlet
Yorlet runs UK residential portfolios: long lets, co-living buildings, and student housing. A resident signs a lease for months, not nights.
Units become properties
TravelPal reads your units, tenancies and the customer record behind each lease. Each Yorlet unit arrives with its name, full address, bedroom and bathroom count, floor, and floor area. It becomes a property the concierge answers about. A Yorlet unit is a letting record, so it holds no house rules, arrival window, or access instructions. Those live in your knowledge base. You write them once, and they are used on every lease in the building.
Tenancies, not bookings
In Yorlet, occupancy is a lease on a unit. It has a start date, an end date, and the people who signed it. An active lease is a live one. A completed lease still counts, so a past resident's history stays with them and is not dropped. The lease carries its own currency, so a portfolio billed in pounds is never quoted in dollars.
One resident across several leases
A Yorlet customer lasts longer than any one tenancy. A resident may renew, move to another unit, or return for a second academic year. TravelPal knows it is the same person. The resident does not start again from nothing. Where a lease has more than one signatory, TravelPal answers one named resident. It does not write to everyone who signed.
The thread, and who is on the other end
A Yorlet thread belongs to a customer or to an owner. TravelPal checks which before it writes a word. It leaves landlord threads to your team. It reads the messages already in a thread in the order they happened. It does not ask a resident in month nine something your team answered in month one.
TravelPal cannot see your team's replies on Yorlet
Yorlet announces each message, but the announcement names no tenancy. So TravelPal cannot match it to a resident or see when your team replies. That is why TravelPal alerts your team to each resident message and does not answer itself.
What TravelPal writes back to Yorlet
Here is what TravelPal sends through Yorlet today, and what it leaves to your team.
Messages in the thread the resident already started
TravelPal sends every message through the Yorlet Inbox as an email on the existing thread, never around it. Your own Inbox holds the full record of what each resident was told and when.
Under the subject the thread already carries
Yorlet requires a subject on every email. It expects a reply to reuse the thread's own subject with Re: in front. TravelPal does exactly that, so its message lands in the conversation already open in the resident's mail app. If a thread has no subject at all, TravelPal holds it for a person. It does not invent a line for the resident to read.
Addressed to the customer, not to a typed address
Each send names the customer record on the thread. So the message reaches the address Yorlet holds today, even after someone on your team corrects it. A typed address is used only where the thread names nobody.
Plain email, not a branded one
Yorlet keeps a branded template for standalone official mail and a plain one for thread replies. TravelPal uses the plain one. A message in the thread then reads as mail from your team, not as a marketing email.
Connected in four steps
You create the access details yourself, inside Yorlet. TravelPal does the rest itself.
Copy the secret key
Open Yorlet Dashboard, then Developers. Take the secret key, not the publishable one. You can create it right now. There is no partner form, no approval queue, and nobody at Yorlet to ask first.
Say which environment it points at
Leave the environment field blank for production. Enter sandbox to point TravelPal at Yorlet's sandbox. Then you can run a whole tenancy on test data before a resident sees a message.
Paste the key into TravelPal
The key is checked against your own unit list at once. A wrong paste is caught right away, and you only need to paste again. TravelPal then subscribes itself to Yorlet's announcements, so lease changes reach it. It removes that subscription again on the day you disconnect.
Set the time zone, then your units import
Yorlet publishes no time zone on a unit or a building. Tell TravelPal once which time zone your portfolio uses, so London addresses are not scheduled on American hours. Your units then arrive as properties. Every tenancy with a move-out date gets its own private resident link. Each unit is billed at the same flat rate: see what it costs.
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 Yorlet connection will not do
Know the limits of Yorlet before you turn anything on. Every property management system has its own limits. TravelPal works inside them, not around them.
Email is the only way to reach a resident
Email is the channel the Yorlet Inbox uses. So this connection has no SMS or WhatsApp fallback and no channel inbox to answer in. A resident with no address on their customer record cannot be reached at all. TravelPal tells you that. It does not post a message nobody receives.
No note that only your team can see
A Yorlet thread holds messages, status changes, and assignee changes. Every message in it is an email the resident receives. So a Yorlet thread has no place for a line meant only for your team. TravelPal does not invent one. What TravelPal holds for a person goes to the chat where your team is alerted. It also goes to your own email. It does not go to the resident.
A rolling tenancy waits for an end date
A periodic or rolling lease has no contractual end in Yorlet, and TravelPal will not make one up. Those tenancies are left alone and not set up. A guessed move-out date would set the checkout message, the deposit conversation, and every cutoff. All would run from a day nobody signed. Put an end date on the lease, and it is picked up on the next change.
Lease dates and lease money stay in Yorlet
A Yorlet tenancy is billed by subscription and carries no accommodation total. So the lease has no figure to compare before and after a change. Money a resident spends is not read back off the lease, as it is on a nightly system. Lease dates change through Yorlet's own lease-change flow, so TravelPal does not touch them. A resident who asks to move their dates reaches your team with what they asked for.
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.
Yorlet integration FAQ
Does Yorlet have to enable anything before I connect?
No. You create the secret API key yourself in the Yorlet Dashboard under Developers. Paste the key into TravelPal next. No partner application and no approval queue stand between you and a working connection. Use the secret key, not the publishable one. TravelPal checks it against your unit list the moment you paste it.
How does TravelPal reply to a Yorlet resident?
It does not reply in Yorlet today. Resident messages go to your team instead. TravelPal's own messages go by email in the resident's thread, under its subject with Re: in front. Email is what the Yorlet Inbox sends, so there is no SMS or WhatsApp route here.
Can TravelPal answer in a landlord thread by mistake?
No. A Yorlet thread is against a customer or an owner. TravelPal checks which before it writes. An owner thread is left for your team. If TravelPal cannot tell who is on the other end, it holds the thread and asks you.
What happens to a rolling tenancy with no end date?
It is left alone. Yorlet allows a tenancy with no contractual end, and TravelPal will not guess a move-out date. The checkout message, the deposit conversation, and every timed reminder would run on a day nobody agreed to. Add an end date to the lease, and that tenancy is set up on the next change.
Not the system you use?
TravelPal connects to 33 property management systems. Below are the systems closest to Yorlet in how widely they are used.
Updated
Yorlet is a trademark of its owner. TravelPal is not affiliated with or endorsed by Yorlet.