Guests waiting on a reply
Sarah Chen, operations manager at Northwind, asked which guests were waiting on a reply. Memtro listed the unread guest messages with their booking, property and when each was sent.
Who arrives this weekend, and which guests are still waiting on a reply?
Beds24 shows you your properties and rooms, then bookings by arrival, departure or change date with room, status and channel. Memtro also reads which bookings have unread guest messages, availability, calendar restrictions and prices, and priced offers for a stay. When asked and granted, it can create, change, cancel or delete bookings, and message a guest through the booking's channel. It can also mark messages read and set availability, minimum stays and prices on the calendar. Guest names, contact details and booking prices are never read, and a long life token connects read-only.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Beds24 tool, reads what it needs, and answers with the source cited.
These tools change something in Beds24. 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.
Once Beds24 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.
Which bookings arrive this weekend?
Which guests are waiting on a reply?
Which nights are free in the garden cottage next month?
What is the minimum stay on the sea view room over Easter?
Block the loft for maintenance from 3 to 5 March.
Sarah Chen, operations manager at Northwind, asked which guests were waiting on a reply. Memtro listed the unread guest messages with their booking, property and when each was sent.
Dan Fletcher, owner of a small holiday let business, asked Memtro to close the loft for three nights of repairs. With the action granted, Memtro set a blackout on the calendar for those dates, and Beds24 sent the change to the connected channels.
The teams that lean on Beds24 most, a question each of them asks, and what they connect beside it.
A record in Beds24 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 Beds24, open Settings → Marketplace → API and generate an invite code with the bookings, inventory and properties scopes. Leave out bookings-personal and bookings-financial.
Open Connections → Beds24 in Memtro and paste the Invite code within 24 hours. For a read-only connection, paste a Long life token instead.
An administrator grants actions such as cancel a booking or message a guest by name to the teams that may use them.
Ask which bookings arrive this weekend.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Beds24 tools are the same everywhere.
Only when you ask, and only what it has been granted: create a booking (can email the guest a confirmation); change a booking's dates, room, guests or status; cancel a booking (updates the channel it came from); delete bookings by id (permanent); send a message to a guest through the booking's channel; mark a guest message as read; set availability, minimum or maximum stay, a block or a price on the calendar (sent to channels). 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.
Invite code, or a read-only long life token. In Beds24, open Settings → Marketplace → API and generate an invite code with the bookings, inventory and properties scopes. Leave out bookings-personal and bookings-financial.
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