Guest lifecycle for a private residence group, automated end to end.
A drawing of the interface, not a screenshot — this concept has not been built for a client.
A small group of private residences sends roughly the same twenty messages to every guest: confirmation, directions, arrival window, preferences, the note before departure, the follow-up a week later.
A person sends them by hand. Which means the quality varies with the day, some are sent at two in the morning, and occasionally one is missed entirely — always for the guest who was going to notice.
The guest lifecycle runs itself: booking, pre-arrival preferences, arrival, in-stay, departure, follow-up. Each step fires from the state of the booking rather than from someone remembering, and each is written once, properly, in both languages.
The preferences collected before arrival flow into the residence rather than into a spreadsheet — so the room is already right, and nobody is asked twice.
Every step has an explicit human handoff condition. Anything unusual, any complaint, any special request, and the process stops and hands the guest to a person immediately, with the full context attached.
No automated reply to anything a guest writes freely. The system handles what is predictable and refuses to guess at what is not.
Nothing is sent that reads as automated. If a message cannot be written well enough to pass for one a person wrote, it does not get sent at all.
The automation is deliberately visible to the staff — they can see what will be sent, when, and to whom, and stop it. A process that runs invisibly is one nobody trusts and everybody works around.