The product direction
Write like a conversation. Deliver as email.
The intended product would turn a message written in the conversation view into email and bring replies back into the same thread.
Product goals — not available features
What a live version must get right
Four promises email cannot break.
These are requirements we want to test against your real workflow — not features you can use today.
Preserve the right recipients and subject.
Whoever you meant to reach, and only them — with a subject they would recognise.
Keep replies connected to the conversation.
A reply by email should land back in the thread it belongs to.
Distinguish draft, sent and failed states.
Make “draft” and “sent” impossible to confuse — and show failures plainly.
Make it clear what the recipient will receive.
The person you write to sees a proper email. You should see exactly that email before it leaves.
One system picture
Clear edges between what exists and what is planned.
A separate Business OS transactional-mail foundation can send platform notifications through SMTP. It is not connected to these drafts.
Working now · this device
- Chat-style conversation viewChannels, groups and direct-message drafts
- Email composer and previewRecipients, subject and body together
- Local drafts and quick repliesSaved in this browser only
Everything above this line works in the local preview today. Everything below it is product direction and is not built.
Below the line · not built yet
- The bridge: chat message → real emailSend is disabled in the preview
- Mailbox connectionNo Gmail, Outlook or other mailbox is connected
- Replies back into the chatInbound handling and thread matching still to be built
Where this helps
For people evaluating the idea and its future requirements. Bring the message you would most want to send this way, and we will work through what the bridge must preserve for it.
What to check in a walkthrough
Ask to see the starting record, the action taken and the resulting state. Check what is saved, what uses sample data and what depends on another service.
Tell us what would make this useful to you.
Describe one message you write every week. We can use that starting point to assess fit, show the relevant interface and make the remaining work clear.
Start with a question, not a commitment. Use sample or anonymised information.
