Lassen Sie einen Agenten ins Reservierungsbuch schauen

Read the organization: its name, locale and which product modules (menu, booking, events, outreach, loyalty, staff) are switched on. Call it when an action is refused because a module is off — only an owner can switch one on.

List the venues (properties) in an organization. Start here to get the propertyId that menu, booking, event and staff tools ask for.

Read one venue in full: address, timezone, opening hours and booking configuration. Use it to find out whether a venue is bookable at all before asking why get_booking_availability returns nothing.

Create a venue: name, URL slug, type, address and timezone. Set its opening hours and booking settings afterwards with the set_property_ tools. A key narrowed to particular venues cannot call this — the new venue is not one of them.

Change a venue’s name, description, address, city, country or timezone. Only the fields sent are written. The URL slug is not changeable here, because a printed QR code resolves through it.

Set a venue’s opening hours. Only the days you name change; the rest of the week is left alone, and exceptions merge by date, so adding one holiday cannot drop the others. removeExceptionDates takes one back off.

Configure how a venue takes bookings: interval, lead time, buffer, auto-confirm. enabled must be true or no slot is ever offered. publicBookingEnabled publishes the venue and requireStaffShiftCoverage can close its diary — confirm both.

List an organization's menus with their status (draft, published, archived). Supports a search term.

Read one menu in full: its categories, the items filed under each, prices, allergens and dietary tags.

Search the dish catalogue by name across the whole organization. Items live independently of the menus they appear on, so use this to find a dish when the menu is unknown.

List the organization's dish sections (starters, mains, wine) as catalogue records. A section is filed here once and placed on any number of menus, so use this to find the categoryId add_category_to_menu needs.

List a menu's daily specials with the dates each one runs.

Create a menu for a venue: an empty shell with a name and a URL slug. Fill it with add_category_to_menu and add_item_to_menu_category, then publish_menu. Nobody sees it until it is published.

Rename a menu or change its slug, description, language, currency or display options. This edits the menu itself and not what is on it; a dish is edited with update_menu_item.

Create a dish section in the catalogue — starters, mains, desserts. It is on no menu until add_category_to_menu places it, and one section can be placed on several menus.

Rename a catalogue dish section or change its description or image. The change lands on every menu that section appears on.

Create a dish in the catalogue with its price, allergens and dietary tags. It is on no menu until add_item_to_menu_category files it under a section of one.

Edit a catalogue dish: name, description, base price, allergens, dietary tags. It changes on every menu it appears on — to change one menu only, use set_menu_item_availability on that placement.

Put an existing catalogue section on a menu at a given position. Returns the assignmentId that add_item_to_menu_category needs — that id, not the categoryId, is what dishes are filed under.

Put a catalogue dish on one menu under one section, optionally with a price override for that menu alone. Takes the assignmentId add_category_to_menu returned, not a categoryId.

Add a daily special to a menu for a given date or date range.

Change the availability note or price override of one item as it appears on one menu. This is how a dish comes off tonight, or goes lunch-only, without being deleted.

Publish a menu so the venue's public page and QR code serve it. Draft edits are invisible to guests until this runs.

Take a menu out of service: it stops being served publicly and is filed as archived rather than deleted. publish_menu brings it back. There is no way to delete a menu here, by design.

List event inquiries for an organization, filterable by venue, stage, owner and whether the next action is overdue. This answers "what has come in, and what has nobody chased".

Read one inquiry: who asked, what for, when they want it, what stage it is at and the notes on it.

Count each pipeline stage and what it is worth, plus how many open inquiries are past their next action date. Money is reported per currency and never summed across them.

Log an enquiry taken by phone or forwarded by mail: who asked, what for, roughly when, how many people. Only the name is required — leave dateFrom out when they have not picked a date rather than inventing one.

Edit an enquiry: dates once the customer firms them up, headcount, owner, when it is next chased, internal notes. Setting estimatedValueCents needs analytics:read too. Use set_inquiry_status to move stage.

Move an enquiry through the pipeline: new, contacted, site_visit, quoted, negotiating, won or lost. Marking one lost requires a lostReason. Its own tool rather than a field on update_inquiry, so nothing can set lost and never be asked why.

Free booking slots at a venue on one date, optionally narrowed by party size, service type or resource. Call before create_booking. Name the venue by propertyId or by propertySlug.

List the bookable resources at a venue — tables, rooms, chairs, courts — with their capacities.

List the service types a venue takes bookings for (dinner service, treatment, rental) with their durations.

List a venue’s closures — holidays, maintenance windows, a table out of service — over an optional date range. This is why a date with opening hours can still offer no slots.

List bookings for an organization, filterable by venue, date range, status and guest name. This answers "who is coming in tonight".

Read one booking: guest, party size, time, assigned resources, status and notes.

Define something a venue takes bookings for — dinner service, a treatment, a court hire — with its duration and optional price. Create these before resources, which reference them by id.

Rename a service type or change its duration, price or order. Send isActive false to retire one: it stops being offered and the bookings already taken against it keep saying what was booked. There is no delete, by design.

Add something a booking can be assigned to — a table, a room, a chair, a court — with its capacity and largest party. serviceTypeIds narrows it to particular services, so create those first.

Change a bookable resource: name, capacity, largest party, which services it takes, its own weekly availability. Send isActive false to take it out of service without destroying which parties sat at it.

Close a venue, or one resource, for a period: a holiday, a private hire, maintenance. Times are the venue’s own wall clock, not UTC. recurrenceRule takes FREQ=DAILY or FREQ=WEEKLY, optionally with ;UNTIL=YYYY-MM-DD.

Move or shorten a closure, change its reason, or scope it to one resource. Shortening it to a past window is how a closure is lifted — there is no delete here, and the original times are what an undo restores.

Take a booking for a guest at a venue on a date and time. Check get_booking_availability first; an identical repeat is answered from the first call, not booked twice. No confirmation is sent, but the venue may still send its own reminder.

Confirm a pending booking. This call emails nobody, but a confirmed booking becomes eligible for the venue's automatic reminder, which may reach the guest. Do not tell the caller the guest has been notified.

Move an existing booking to a different date or time, keeping the guest and party size. The guest is not emailed about the change; the venue tells them.

Cancel a booking, with an optional reason recorded against it. The reason does not reach the guest and no cancellation email is sent; the venue tells them.

List events, filterable by venue, status, category, search term, or upcoming-only.

Read one event: schedule, venue, capacity, ticketing and whether it is published.

List who has registered for an event, with party sizes and check-in state. This answers "how many are coming to the quiz".

Create an event at a venue. It starts as a draft and is not public until publish_event runs.

Change an event: title, description, dates, capacity, venue details, category or ticket links. Only the fields sent are written. Changes to a published event are live on the public page immediately.

Publish a draft event so it appears on the venue's public page and starts taking registrations.

Create a category for the programme — live music, quiz, private hire — with a URL slug. It is on no event until create_event or update_event names its id. Slugs are unique within the organization.

Rename a programme category or change its slug, description, colour, image or order. The change lands on every event filed under it, and a new slug changes the category’s public address.

Search guests by name, email or phone, optionally within one contact group. Use it to resolve a name to a contactId.

Read one guest: contact details, consent state, and the email and phone endpoints they can be reached on.

List contact groups (segments), static and rule-based, with member counts. Use it to find the groupId for add_contact_to_group.

Add a guest to the contact book. Creating a contact is not a marketing opt-in — consent is recorded separately.

Correct a guest’s details: name, email, phone, tags or custom fields. Only the fields sent are written, and at least one of email, phone or an external id must remain. This cannot change their marketing consent.

Put a guest into a contact group. Groups are how this product tags people — there is no separate tag. Adding somebody who is already in it changes nothing.

Create a contact group (a segment) to file guests into. Names are unique within the organization. Leave definition out for a hand-picked list; a definition makes it a rule-based group the platform recomputes.

Rename a contact group or change its description, colour or matching rules. Changing the rules of a rule-based group changes who a campaign addressed to it will reach.

Take a contact group out of use: it stops appearing in the ordinary listing and is filed as archived rather than deleted, keeping every membership. unarchive_contact_group brings it back. There is no delete, by design.

Put an archived contact group back into use. Refused if it is not archived, so this cannot be used to check whether one is.

Visit history: recorded guest check-ins, filterable by guest, venue, status and date range. This answers "when was she last in".

List the people on a venue's team, with their roles and employment state.

The rota over a date range: who is on, when, in what role, and which shifts are still open. Requires from and to dates.

Coverage for one venue on one date: rostered hours against expected demand, hour by hour, so a gap is visible. This answers "are we short on Saturday".

What publishing the rota for a venue over a date range would take off sale: with requireStaffShiftCoverage on, an unpublished shift leaves a resource bookable and a published one constrains it. Read this before publishing.

File a shift on the rota at a venue: date, start and end in the venue’s own wall clock, optional role and break. Leave staffMemberId out for an open shift nobody is assigned to. It is a draft until published.

Move a shift, reassign it, edit its role or break, or send status published to put it on the rota and draft to take it off. Where the venue requires shift cover, publishing changes what guests can book — read get_staff_publish_impact first.

Booking trend, capacity use, no-show rate, revenue and margin over a date range. The general "how did we do" number.

Booked covers by day and service type over a date range.

Rostered labour cost against booked covers for one venue over a date range, including cost per cover.

How the enquiries taken over a date range turned out: won, lost, win rate, what the won ones were worth per currency, median hours to a first quote, and lost reasons by count. Only the value block needs analytics:read.

List what THIS key has already done — its own changes and reads, newest first, with the id of each one and whether it can still be undone. Call it to check whether a write landed after a timeout, or before reporting back what you changed.

Ask what undoing one of your own actions would do, and what it would refuse, without undoing anything. Call it before revert_agent_action when the change is not one you made seconds ago.

Undo one change YOU made, named by its id from list_agent_actions. Refused if it was not yours, was already undone, is older than an hour, or the record has changed since — the refusal says which.

Undo the last change you made — this conversation only, when your client sends a session id. Pass expectedTool to be refused rather than undo the wrong thing if the ledger disagrees with what you think you did last.