Trust & availability
Clear about the product. Clear about the limits.
Choosing software should not require guessing what happens behind a demo. Here is the current boundary for MailCircle.
Concept + draft preview
The current boundary
The draft is real. The delivery is not connected.
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
What the review established
Two separate foundations. No invented bridge.
The parent platform’s transactional email foundation was tested separately. That result must not be used to claim that MailCircle sends conversation messages. The disabled send state is visible in the actual preview.
Six email integration tests passed against local database, cache and mail-catcher services. They validate the parent platform’s transactional mail path, including policy and retry behaviour. They do not validate MailCircle chat-to-email delivery or Internet inbox acceptance. No customer results, production-scale performance or independent certification are implied.
What the demo means
Concept preview — not a live email service.
The current interface saves local drafts. It does not send chat messages as email, connect your mailbox or bring replies back into the chat.
The screenshots retain Business OS branding because MailCircle is not yet a separately shipped product.
Capability by capability
The review status of every surface.
Plain labels: interface preview means you can see and use the screen locally; disabled means the control is present but switched off; not built means it does not exist yet.
| Capability | Status | What that means for you |
|---|---|---|
| Channels, groups and direct-message drafts | Interface preview | Explore the layout; nothing is delivered. |
| Message threads and mentions | Interface preview | Inspect how conversations could be organised. |
| Mine / unassigned / all inbox | Interface preview | Review the surface; no live routing. |
| Email composer and preview | Interface preview | Write and inspect a draft. |
| Save email draft | Browser-local | Stored in this browser only; not synced or backed up. |
| Quick replies | Browser-local | Reusable wording, saved locally. |
| Send drafted email | Disabled in preview | The button is visible and switched off. |
| Connected mailbox settings | Disabled in preview | No Gmail, Outlook or other mailbox connection. |
| Channel, routing, labels and SLA configuration | Interface preview | Screens only; no live behaviour. |
| Chat messages delivered as real email | Not built yet | The central product direction. |
| Replies returned into the chat | Not built yet | Inbound handling and thread matching still to be built. |
| Attachments | Not built yet | Unsupported mail fields are rejected by the shared foundation. |
| AI writing or rewriting | Not verified | Do not expect AI writing in this preview. |
What to verify before real use
A working local interface is one piece of evidence.
The exact deployment, access controls, data handling, connected services and operating process need review for your use. A working local interface does not settle every live-use requirement.
A straightforward evaluation
- Ask for a demonstration with sample records.
- Follow one record from beginning to end.
- Ask where information is stored, who can access it and which actions are simulated.
- Review open issues before deciding what comes next.
Your data in the preview
Where drafts go, and what not to share.
- Drafts and quick replies are kept in your browser’s local storage on the device you use.
- They are not verified as synchronised, backed up or shared across devices.
- The preview is not a live secure mailbox. Use sample or anonymised text — never passwords, payment details or confidential customer information.
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.
