AI resident messaging for Yorlet
TravelPal connects to Yorlet with the secret API key from your own Developers page, then answers residents by email in the Inbox thread they already wrote in. It reads your units, your tenancies and the dates on them, and the customer record behind each lease, so somebody who renews or takes a second unit is recognized as the same person. Yorlet's Inbox sends email, so email is where TravelPal answers.
One connection, running both ways. Every item on it is detailed below.
What TravelPal reads from Yorlet
Yorlet runs UK residential portfolios: long lets, co-living buildings, and student housing, where a resident signs a lease for months rather than booking nights.
Units become properties
Your Yorlet units arrive with their name, full address, bedroom and bathroom count, floor, and floor area, and become the properties 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, written once and used on every lease in the building.
Tenancies, not bookings
Occupancy in Yorlet is a lease against a unit: a start date, an end date, and the people who signed it. An active lease is a live one and a completed lease still counts, so a past resident's history stays with them instead of being 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 outlives any single tenancy, so somebody who renews, moves to another unit, or comes back for a second academic year is recognized rather than starting from nothing. Where a lease has more than one signatory, TravelPal answers one named resident rather than writing to everybody 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, answers in resident threads, and leaves landlord threads to your team. It reads the messages already in a thread in the order they happened, so it picks up a conversation mid-tenancy instead of asking a resident in month nine something your team answered in month one.
Yorlet says when your own team replies
Yorlet announces the messages your people send, not only the ones residents send. When somebody on your team picks up a thread in the Inbox, the concierge sees that send and stands back rather than answering over a colleague.
What TravelPal writes back
Every message goes out through Yorlet, never around it, so your own inbox shows exactly what each guest was told.
Replies in the thread the resident already started
Every answer goes out through the Yorlet Inbox as an email on the existing thread, never around it, so 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 and expects a reply to reuse the thread's own with Re: in front. TravelPal does exactly that, so an answer lands in the conversation already open in the resident's mail client. Where a thread carries no subject at all, TravelPal holds it for a person rather than inventing a line the resident would read.
Addressed to the customer, not to a typed address
Each send names the customer record on the thread, so the reply reaches the address Yorlet holds today even after somebody 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 plain, so a mid-conversation answer reads as a reply from your team rather than as a marketing send.
Connected in four steps
The credentials are yours to create inside Yorlet. TravelPal does the rest itself.
Copy the secret key
Yorlet Dashboard, then Developers. Take the secret key, not the publishable one. It is yours to create right now: 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 instead to point TravelPal at Yorlet's sandbox, so you can run a whole tenancy through on test data before a resident ever sees a message.
Paste the key into TravelPal
The key is checked against your own unit list on the spot, so a wrong paste is caught immediately and costs nothing but a retry. TravelPal then subscribes itself to Yorlet's tenancy and message announcements, and removes that subscription again the day you disconnect.
Set the time zone, then your units import
Yorlet publishes no time zone on a unit or a building, so tell TravelPal once which one your portfolio runs in rather than having London addresses scheduled on American hours. Your units then arrive as properties, and every tenancy with a move-out date on it gets its own private resident link. Each unit is billed at the same flat rate: see what it costs.
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 Yorlet connection will not do
Every property management system draws its own lines, and the ones Yorlet draws are worth knowing before you switch anything on. TravelPal works inside them rather than around them.
Email is the only way to reach a resident
Email is the channel the Yorlet Inbox uses, so there is no SMS or WhatsApp fallback on this connection and no channel inbox to answer in. A resident with no address on their customer record cannot be reached at all, and TravelPal tells you that rather than posting a reply nobody receives.
No note that only your team can see
A Yorlet thread holds messages, status changes, and assignee changes, and every message in it is an email the resident receives. So there is nowhere in a Yorlet thread to leave a line meant only for your team, and TravelPal does not improvise one: what it holds for a person reaches your team channel and your own email rather than the resident's inbox.
A rolling tenancy waits for an end date
A periodic or rolling lease genuinely has no contractual end in Yorlet, and TravelPal will not invent one. Those tenancies are left alone rather than set up, because a guessed move-out date would drive the checkout message, the deposit conversation, and every cutoff 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 there is no figure on the lease to compare before and after a change, and money a resident spends is not read back off the lease the way it is on a nightly system. Lease dates move through Yorlet's own lease-change flow, so TravelPal does not touch them: a resident asking to move their dates reaches your team with what they asked for.
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.
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 and paste it into TravelPal. No partner application and no approval queue stand between you and a working connection. Use the secret key rather than the publishable one: TravelPal checks it against your unit list the moment you paste it.
How does TravelPal reply to a Yorlet resident?
By email, in the thread the resident already has, under that thread's own subject with Re: in front. Email is what the Yorlet Inbox sends, so there is no SMS or WhatsApp route here. Every reply goes out through Yorlet, so your team reads it in the same Inbox they already work in.
Can TravelPal answer in a landlord thread by mistake?
No. A Yorlet thread is against a customer or against an owner, and TravelPal checks which one before it writes. It answers residents. An owner thread is left for your team, and where 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, because the checkout message, the deposit conversation, and every timed reminder would then 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 run?
TravelPal connects to 33 property management systems. These are the ones nearest Yorlet in how widely they are used.
Updated