Example scenario: manor
A wedding request at 11 pm: from enquiry to run sheet
A made-up venue, Hallikivi Manor, receives a wedding request late in the evening. Here is what happens in Saalo, step by step.
Example scenario, not a customer story. The venue, people and prices are made up to show how Saalo works.
In the evening: the request arrives
A couple fills in the request form on Hallikivi Manor's website: date, guest count, how many guests stay overnight, catering and where the ceremony takes place. The form shows only free dates. The request lands in the manor's single inbox as fields, not as a long e-mail.
In the morning: a draft quote
A team member opens the inbox. A draft quote is already there: the AI has written the text in the customer's language, but the amounts come from the manor's own price rules (room hire, accommodation, extras). The team member checks the lines, corrects them if needed and sends. By default nothing reaches the customer until an authorised person has approved it.
The couple accepts and pays a deposit
The couple receives a link to the quote page, reviews it, accepts it and can pay a deposit to the manor's own Montonio account (live payments are in pilot). The booking is confirmed only after the payment is confirmed. The quote amount is a snapshot, so it does not change if the manor later updates its price list.
Before the event
The confirmed booking produces a run sheet and a kitchen sheet: menu choices, diets and guest numbers. On the day the team looks at one page, not three e-mail threads.
What this example does not claim
It is not a real customer or a result. We do not say that a manor will get more bookings or save a set amount of time; it only describes the workflow.