STS Cloud Integration

Group sales and catering. Connected by a one-time link emailed to the property — the hotel approves access in their own STS Cloud account, so no credentials are shared with Maison. STS Cloud official site ↗

What it covers

STS Cloud is a sales and catering system: group enquiries, function space, and the pipeline behind them. Connecting it lets the concierge answer questions about meeting and event space, check what is available, and pass a qualified enquiry to your sales team instead of losing it to a contact form.

Setup steps

Ask Maison to send the connect invitation
Maison emails a one-time link to the address on file for the property. The link expires after seven days.
Open the link while signed in to STS Cloud
The link takes the property to STS Cloud's own consent screen. Whoever opens it must be signed in to the STS Cloud account the hotel wants connected.
Approve the requested access
STS Cloud shows what Maison is asking for and returns the property to Maison once approved.

The invitation is single-use and is consumed when access is approved, not when the link is opened — so a mail scanner following the link in transit will not burn it.

Available tools

10 tools are available for STS Cloud. The concierge calls them on a guest's behalf during a conversation; which are enabled is set per property, so you only turn on what you want it to be able to do.

Enabled by default (2)

On as soon as the integration is connected, with nothing else to configure.

Tool What it does

stscloud_get_function_space_availability Check which event/function spaces are free, held, tentative, or booked for a date range. Use this for any event-space availability question ('is the ballroom free on...', 'do you have space for a wedding in June'). start_date and end_date are ISO YYYY-MM-DD dates (e.g. 2026-09-01); the end date is INCLUSIVE. The range may cover at most 31 days per call — for a longer range make two separate calls and combine the results. Status meanings — explain them clearly: 'held' means a provisional hold with no confirmed party; 'tentative' means a booking is pending confirmation; 'booked' means a confirmed definite booking. A held or tentative space may still become available — the events team can advise. 'unknown' means the hotel's diary did not report occupancy for that space, so NOTHING is known about whether it is taken. Never present an 'unknown' space as free or available: say the hotel has the space and that the events team will confirm whether it is open for those dates, and offer to pass the enquiry on. Treat every 'unknown' this way even when the guest presses for a yes or no. IMPORTANT — status is for the WHOLE range you asked about, so a room booked for one morning reads as 'booked' for every day you queried. Always read the `conflicts` array before telling a guest a space is unavailable: each entry gives the startTime and endTime that are actually taken. If the guest's event does not overlap those times, the space may well be free — say what is taken and when, rather than a flat 'not available'. Narrow the date range to check a single day. Before handing an event inquiry to the events team, always collect: event type, approximate dates, guest count, and contact details. NEVER quote rates, pricing, or capacity numbers — rates are contract-negotiated and capacity is not available via this system; route all pricing, capacity, availability-confirmation, and large-event questions to the hotel's events team.

stscloud_get_function_spaces List the property's event/function spaces (meeting rooms, ballrooms) by id and name. Use this to tell a guest what event spaces exist or to resolve a space name before checking availability. IMPORTANT vendor limitation: capacity numbers and space descriptions are NOT available from this system — NEVER invent, estimate, or imply them; refer capacity questions to the hotel's events team. Takes no parameters — the property is resolved automatically. NEVER quote rates, pricing, or capacity numbers — rates are contract-negotiated and capacity is not available via this system; route all pricing, capacity, availability-confirmation, and large-event questions to the hotel's events team.

Tool	What it does
`stscloud_get_function_space_availability`	Check which event/function spaces are free, held, tentative, or booked for a date range. Use this for any event-space availability question ('is the ballroom free on...', 'do you have space for a wedding in June'). start_date and end_date are ISO YYYY-MM-DD dates (e.g. 2026-09-01); the end date is INCLUSIVE. The range may cover at most 31 days per call — for a longer range make two separate calls and combine the results. Status meanings — explain them clearly: 'held' means a provisional hold with no confirmed party; 'tentative' means a booking is pending confirmation; 'booked' means a confirmed definite booking. A held or tentative space may still become available — the events team can advise. 'unknown' means the hotel's diary did not report occupancy for that space, so NOTHING is known about whether it is taken. Never present an 'unknown' space as free or available: say the hotel has the space and that the events team will confirm whether it is open for those dates, and offer to pass the enquiry on. Treat every 'unknown' this way even when the guest presses for a yes or no. IMPORTANT — status is for the WHOLE range you asked about, so a room booked for one morning reads as 'booked' for every day you queried. Always read the `conflicts` array before telling a guest a space is unavailable: each entry gives the startTime and endTime that are actually taken. If the guest's event does not overlap those times, the space may well be free — say what is taken and when, rather than a flat 'not available'. Narrow the date range to check a single day. Before handing an event inquiry to the events team, always collect: event type, approximate dates, guest count, and contact details. NEVER quote rates, pricing, or capacity numbers — rates are contract-negotiated and capacity is not available via this system; route all pricing, capacity, availability-confirmation, and large-event questions to the hotel's events team.
`stscloud_get_function_spaces`	List the property's event/function spaces (meeting rooms, ballrooms) by id and name. Use this to tell a guest what event spaces exist or to resolve a space name before checking availability. IMPORTANT vendor limitation: capacity numbers and space descriptions are NOT available from this system — NEVER invent, estimate, or imply them; refer capacity questions to the hotel's events team. Takes no parameters — the property is resolved automatically. NEVER quote rates, pricing, or capacity numbers — rates are contract-negotiated and capacity is not available via this system; route all pricing, capacity, availability-confirmation, and large-event questions to the hotel's events team.

Available on request (8)

Off by default. Ask Maison to enable any of these for your property — several change data in your STS Cloud account, so they are opt-in rather than assumed.

Tool	What it does
`stscloud_create_account`	Create a new event-sales account (the company or organisation booking the event) in the hotel's system. Call ONLY after stscloud_find_account returned no clear match — a duplicate account splits a customer's history across two records and the events team has to merge them by hand. Returns the new account id, which stscloud_create_booking needs. Never call this twice for the same company, and never retry after a timeout — the account may already exist. NEVER quote rates, pricing, or capacity numbers — rates are contract-negotiated and capacity is not available via this system; route all pricing, capacity, availability-confirmation, and large-event questions to the hotel's events team.
`stscloud_create_booking`	Create an event booking in the hotel's sales system. This is the LAST step: first confirm the space is free with stscloud_get_function_space_availability, then resolve the account (stscloud_find_account / stscloud_create_account) and the contact (stscloud_find_contact / stscloud_create_contact). The booking is always created as TENTATIVE — the hotel's events team confirms it. Tell the guest exactly that: their event space is held provisionally and the team will be in touch to confirm the details. Never describe it as confirmed, guaranteed or booked. Add a booking_meetings entry for each session, using a meeting_room_id from stscloud_get_function_spaces. If the response carries a `warnings` array, part of what you sent was NOT applied — tell the guest the request has gone to the events team for manual completion, and never state the sessions or spaces were recorded. Never call this twice for the same event, and never retry after a timeout — the booking may already exist; check with the events team instead. NEVER quote rates, pricing, or capacity numbers — rates are contract-negotiated and capacity is not available via this system; route all pricing, capacity, availability-confirmation, and large-event questions to the hotel's events team.
`stscloud_create_contact`	Create a new contact (the person organising the event) in the hotel's system, optionally attached to an account. Call ONLY after stscloud_find_contact returned no match on their email. Pass account_id when you already have the account, so the person is filed under the right company. Returns the new contact id, which stscloud_create_booking can use. Never call this twice for the same person, and never retry after a timeout. NEVER quote rates, pricing, or capacity numbers — rates are contract-negotiated and capacity is not available via this system; route all pricing, capacity, availability-confirmation, and large-event questions to the hotel's events team.
`stscloud_create_event_lead`	Capture an event inquiry as a sales lead in the hotel's event management system. Use AFTER collecting all of: event type (e.g. wedding, conference), start date (YYYY-MM-DD), attendee count, and the contact's name and email — ask for anything missing before calling. Pass them inside the single `lead` object. Never quote rates or space capacity (not available); tell the guest the hotel's events team will follow up with pricing and details. Never call this twice for the same inquiry, and never retry after a timeout — the lead may already exist.
`stscloud_find_account`	Search the hotel's event-sales accounts (companies/organisations) by name or email. ALWAYS call this before creating an account, so the same company does not end up duplicated in the hotel's system. Returns the matching accounts with their ids; use the id of an account whose name clearly matches the company the guest named. If nothing matches, create one with stscloud_create_account. An empty result is a normal answer, not an error. NEVER quote rates, pricing, or capacity numbers — rates are contract-negotiated and capacity is not available via this system; route all pricing, capacity, availability-confirmation, and large-event questions to the hotel's events team.
`stscloud_find_contact`	Search the hotel's contacts (individual people) by name or email. ALWAYS call this with the guest's email before creating a contact, so the same person is not duplicated. Returns matching contacts with their ids and the id of the account each belongs to. Match on the EMAIL, not the name — two different people share a name far more often than an address. NEVER quote rates, pricing, or capacity numbers — rates are contract-negotiated and capacity is not available via this system; route all pricing, capacity, availability-confirmation, and large-event questions to the hotel's events team.
`stscloud_get_booking`	Look up one existing event booking by id, including its dates, status and meetings. Requires a verified booker — never use it to answer a question about a booking the guest has not proven is theirs. Use the status verbatim: 'tentative' means the events team has not confirmed it yet, and must not be described to a guest as confirmed. NEVER quote rates, pricing, or capacity numbers — rates are contract-negotiated and capacity is not available via this system; route all pricing, capacity, availability-confirmation, and large-event questions to the hotel's events team.
`stscloud_update_booking`	Amend an existing event booking — its dates, name, expected room count or notes. Requires a verified booker. Read the booking first so you change only what the guest asked to change. This CANNOT change which spaces are held or when they are used, and it cannot confirm or cancel a booking — those go to the hotel's events team. Tell the guest an amendment has been passed to the team, never that it is confirmed. If the response carries a `warnings` array, part of what you sent was NOT applied — tell the guest the request has gone to the events team for manual completion, and never state the sessions or spaces were recorded. NEVER quote rates, pricing, or capacity numbers — rates are contract-negotiated and capacity is not available via this system; route all pricing, capacity, availability-confirmation, and large-event questions to the hotel's events team.