Multi-Channel Support Inbox · Documentation

Business Problem & Solution

The problem Multi-Channel Support Inbox solves in the hospitality ecosystem and how this downscaled demo proves it.

Multi-Channel Support Inbox
every channelthe systemone deskemail · chat · socialphone · web#03 / #38 escalationsunified inboxthread · SLA · statusone conversationassigned + SLAresolved ticketone inbox for every channel
Live diagram — the cluster shares one conversation model; a route-to-ticket elsewhere becomes an inbox item here.

One inbox for every channel

Guests reach support across email, chat, social, phone, and web, and an agent shouldn't need five tools to keep up. The Multi-Channel Support Inbox is the unified omnichannel desk: every channel becomes one threaded conversation with assignment, SLA timers, and a status workflow — and it's where escalations from email triage (#03), the concierge assistant (#02), and guest–host messaging (#38) land as tickets.

What the demo proves — and simplifies

It proves the cluster shares one conversation model: this inbox owns the `ticket` / `conversation` / `message` entities that #03 and #38 escalate into, so a route-to-ticket in email becomes an inbox item here with its source recorded. It simplifies the externals and labels them — channels are simulated (no real email/chat/social connectors), the AI draft is deterministic, and SLA timers run off synthetic due-times. Representative figures only.

Business Problem & Solution · Multi-Channel Support Inbox · Abhishek Saxena