The weekend's arrivals
Maya Okafor, guest experience manager at Acme Ltd, asked who was checking in this weekend. Memtro listed the reservations with listing, guest name, number of guests and check-in time, in each listing's time zone.
Who is checking in this weekend, and at which property?
Guesty connects Memtro to your property management. It reads listings with title, nickname, type, size, city and country, check-in and check-out times and tags, and reservations by status, listing, source, confirmation code, check-in, check-out or booking dates. It reads a guest's name and a reservation's internal comments. When asked, and once an administrator has granted the action by name, it can comment on a reservation, create a task such as a cleaning or maintenance job, or delete a task. Guest contact details are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Guesty tool, reads what it needs, and answers with the source cited.
These tools change something in Guesty. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Guesty for you. Each event can start a job, with the event as its input. Guesty signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Guesty is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Who is checking in this weekend?
Which reservations at the Harbour View flat came from Airbnb this month?
What are the check-in and check-out times at the Old Mill?
What did the team note on reservation HX7Q2?
Create a cleaning task for the Harbour View flat on Friday
Maya Okafor, guest experience manager at Acme Ltd, asked who was checking in this weekend. Memtro listed the reservations with listing, guest name, number of guests and check-in time, in each listing's time zone.
Tom Reilly, operations lead at Northwind, asked Memtro to create a cleaning task for the Old Mill on Sunday afternoon, assigned to Sarah Chen. Memtro created the task in Guesty, which may notify Sarah.
The teams that lean on Guesty most, a question each of them asks, and what they connect beside it.
A record in Guesty is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Guesty, open Integrations → Developer tools → OAuth applications and create a new API application for Memtro.
Copy its Client ID and Client secret. The secret is shown only when the application is made. Give Memtro its own application, as Guesty allows five access tokens a day per application.
In Memtro, open Connections → Guesty and paste Client ID and Client secret.
Ask your first question: who is checking in this weekend?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Guesty tools are the same everywhere.
Only when you ask, and only what it has been granted: add an internal comment to a reservation (mentioned users may be notified); create a task, such as a cleaning or maintenance job, on a listing or reservation; delete a task (permanent). Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Client ID and Client secret. In Guesty, open Integrations → Developer tools → OAuth applications and create a new API application for Memtro.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Guesty for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time