guestavo.com

Read the organization: its name, locale and which product modules (menu, booking, events, outreach, loyalty, staff) are switched on.

List the venues (properties) in an organization.

Read one venue in full: address, timezone, opening hours and booking configuration.

Create a venue: name, URL slug, type, address and timezone.

Change a venue’s name, description, address, city, country or timezone.

Set a venue’s opening hours.

Configure how a venue takes bookings: interval, lead time, buffer, auto-confirm.

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

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.

List the organization's dish sections (starters, mains, wine) as catalogue records.

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.

Rename a menu or change its slug, description, language, currency or display options.

Create a dish section in the catalogue — starters, mains, desserts.

Rename a catalogue dish section or change its description or image.

Create a dish in the catalogue with its price, allergens and dietary tags.

Edit a catalogue dish: name, description, base price, allergens, dietary tags.

Put an existing catalogue section on a menu at a given position.

Put a catalogue dish on one menu under one section, optionally with a price override for that menu alone.

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.

Publish a menu so the venue's public page and QR code serve it.

Take a menu out of service: it stops being served publicly and is filed as archived rather than deleted.

Free booking slots at a venue on one date, optionally narrowed by party size, service type or resource.

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.

Define something a venue takes bookings for — dinner service, a treatment, a court hire — with its duration and optional price.

Rename a service type or change its duration, price or order.

Add something a booking can be assigned to — a table, a room, a chair, a court — with its capacity and largest party.

Change a bookable resource: name, capacity, largest party, which services it takes, its own weekly availability.

Close a venue, or one resource, for a period: a holiday, a private hire, maintenance.

Move or shorten a closure, change its reason, or scope it to one resource.

List event inquiries for an organization, filterable by venue, stage, owner and whether the next action is overdue.

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.

Log an enquiry taken by phone or forwarded by mail: who asked, what for, roughly when, how many people.

Edit an enquiry: dates once the customer firms them up, headcount, owner, when it is next chased, internal notes.

Move an enquiry through the pipeline: new, contacted, site_visit, quoted, negotiating, won or lost.

List bookings for an organization, filterable by venue, date range, status and guest name.

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

Take a booking for a guest at a venue on a date and time.

Confirm a pending booking.

Move an existing booking to a different date or time, keeping the guest and party size.

Cancel a booking, with an optional reason recorded against it.

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.

Create an event at a venue.

Change an event: title, description, dates, capacity, venue details, category or ticket links.

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.

Rename a programme category or change its slug, description, colour, image or order.

Search guests by name, email or phone, optionally within one contact group.

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

Add a guest to the contact book.

Correct a guest’s details: name, email, phone, tags or custom fields.

List contact groups (segments), static and rule-based, with member counts.

Put a guest into a contact group.

Create a contact group (a segment) to file guests into.

Rename a contact group or change its description, colour or matching rules.

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.

Put an archived contact group back into use.

Visit history: recorded guest check-ins, filterable by guest, venue, status and date range.

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.

Coverage for one venue on one date: rostered hours against expected demand, hour by hour, so a gap is visible.

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.

File a shift on the rota at a venue: date, start and end in the venue’s own wall clock, optional role and break.

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.

Booking trend, capacity use, no-show rate, revenue and margin over a date range.

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.

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.

Ask what undoing one of your own actions would do, and what it would refuse, without undoing anything.

Undo one change YOU made, named by its id from list_agent_actions.

Undo the last change you made — this conversation only, when your client sends a session id.