Seats for the weekend
Tom Reilly, operations manager at a Northwind walking tour company, asked how many seats were left on Saturday's tours. Memtro listed each open slot with its seats left.
How many seats are left on Saturday's tours, and who has booked?
Bookeo shows you bookings by date or last change, with product, customer name, participants, price and amount paid. Memtro also reads customers by name with booking history counts, payments and refunds, open slots and seats, products, people categories, resources and blocked time. When asked and granted, it can create or cancel a booking, telling the customer only when you say so, and record a payment. It can also create, update or delete a customer, and block or unblock resources or seats. Customer contact details are never read, and the business's account owner must install the application.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Bookeo tool, reads what it needs, and answers with the source cited.
These tools change something in Bookeo. 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 Bookeo 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.
How many seats are left on Saturday's tours?
Which bookings were made since yesterday?
How much was paid in the last seven days, and how much was refunded?
What has Priya Sharma booked with us?
Block the kayak guide's time next Tuesday morning.
Tom Reilly, operations manager at a Northwind walking tour company, asked how many seats were left on Saturday's tours. Memtro listed each open slot with its seats left.
Maya Okafor, bookings lead at Acme Ltd, asked Memtro to hold six seats on Friday's harbour cruise for a school group. With the action granted, Memtro blocked the seats so customers could not book them, and nobody was notified.
The teams that lean on Bookeo most, a question each of them asks, and what they connect beside it.
A record in Bookeo 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.
Sign up for a free Bookeo developer account, register an application with the API Key method, and copy the secret key. Add the permissions you need to the Authorization URL and have the account owner install the application.
Open Connections → Bookeo in Memtro and paste the Secret key and the API key the owner was shown.
An administrator grants actions such as create a booking or delete a customer by name to the teams that may use them. Changing permissions later issues a new API key.
Ask how many seats are left on Saturday's tours.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Bookeo tools are the same everywhere.
Only when you ask, and only what it has been granted: create a booking, notifying the customer and staff only when told to; cancel a booking, notifying the customer only when told to; record a payment received (or a refund) against a booking; create a customer; update a customer's name, email or phone; delete a customer; block time on resources; remove a resource block; block seats on an event; remove a seat block. 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.
Secret key and API key. Sign up for a free Bookeo developer account, register an application with the API Key method, and copy the secret key. Add the permissions you need to the Authorization URL and have the account owner install the application.
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