Guest–Host Messaging · Documentation
User Journey
The end-to-end path through Guest–Host Messaging, from trigger to outcome.
← Guest–Host Messaging- 1
Guest message → host reply (or escalation)
A guest messages their host about a late arrival. On the host side the agent runs a smart-reply draft, optionally translates the guest's message to read it, edits, and sends. If the issue needs the wider support team, one "Convert to ticket" turns the thread into a categorized #16 ticket without leaving the conversation.
- 2
How it ripples outward
Sends emit `message.sent`; a convert emits `ticket.created` + `ticket.routed` on the shared bus. The escalated thread becomes a ticket #16 owns and lists with the messaging source recorded — the same conversation, read from two apps, never copied. The app reads shared-core booking / guest / host (partner) for thread context.