Hospitality messaging
GuestConnect
A shared inbox that helps hotel staff review guest messages, draft and translate replies, and take over conversations that need a person.
Guest messages enter through the documented external channels. The teal arrows show inbound webhooks going to the API.
The Fastify API verifies the webhook and routes the event to the appropriate tenant before writing the message.
PostgreSQL is the system of record. Row-level security enforces the tenant boundary described in the topology.
The console receives live updates over server-sent events. The dashed green arrow traces that update back to the operator UI.
Inside the operator console
Shared inbox
The three-pane workspace brings guest conversations into a single list so staff can select a thread and read it in context.
Reply drafting and translation
Operators can draft a response and use translation tools while reviewing the conversation.
Human handoff
Staff can take over when a conversation needs an operator to respond directly.
My contributions
I fixed Linux runtime and continuous integration issues. I also contributed to a team delivery that included a guest-facing webchat demo and refinements to the operator console.
How messages reach the inbox
The documented design uses Fastify to validate inbound events and PostgreSQL to record messages in the right tenant. Server-sent events update the Next.js and TypeScript console. Background workers handle queued jobs separately from the web interface.
When staff take over
The documented handoff pauses automated replies and prepares a summary for staff. After an operator accepts, the AI suggests drafts and the operator decides what to send.