// inbox — every conversation, one thread
in production inside MiiraOne thread per client — wherever the conversation happens.
Every WhatsApp message a lead sends already lands in a single thread — text, photos, audio, documents and video. That engine runs in production today, inside Miira's chats. The standalone inbox, with email in the same tray, is designed and next in line.
// It's the threading engine behind Miira's chats — running on niiko's own WhatsApp number, today.
running today
The parts already in production.
// Not a roadmap — this is what processes real conversations right now.
Inbound threading
Every message a lead sends is materialized into one conversation — no duplicates, no lost context, processed exactly once.
Hot handoff
“Take over the chat” and the AI agent goes silent immediately — mid-conversation, verified twice before anything is sent.
Inbound media
Photos, audio, documents and video arrive into the thread — stored on our own infrastructure, with GDPR erasure built in from day one.
Notes and ownership
Internal notes that never leave through the channel, and a conversation that can change hands — both already in use inside Miira’s chats.
designed — build follows
What the full Inbox becomes.
// Specified down to edge cases and audited adversarially before a line of UI gets written.
- WhatsApp and email from the same contact, in one timeline
- Those internal notes and handoffs, in a tray of their own — not only inside a module’s chats
- A composer that respects WhatsApp’s 24-hour window: outside it, only Meta-approved templates
- Assignment history and open/pending/closed states — closing never deletes, an inbound reply reopens
- Bot and human sharing mailboxes, with the general inbox always human
see it
The thread, as it looks inside.
// Sample data, marked demo — same tri-panel the workspace uses.
What it does NOT do yet
The engine is live; the standalone tray isn't. Here's the honest split:
- A unified WhatsApp + email tray. The email channel isn't started yet, and the tray has no home of its own — today the conversation lives inside Miira.
- First-response and resolution metrics. Fully specified, not built.
- A composer that enforces WhatsApp's 24-hour window. Designed as a hard rule at the API level — not built yet.
- AI auto-categorization and suggested replies. A later phase, spec only.
- Customer logos or volume numbers. We don't publish any — the dogfood above is the only proof we show.
// see the engine working
Watch it run inside Miira.
The same threading you just read about is answering real WhatsApp conversations right now — inside the module that's already live.
See Miira live →