MimiDesk

Product

The workspace for customer conversations

Customers have conversations, not tickets. MimiDesk is built around that — one place where a conversation is opened, worked, discussed and answered.

Desk · Inboxes

Team inboxes beside private mailboxes

Shared inboxes carry the conversations a team is accountable for — support, sales, finance — with assignment, snooze, tags and a clear answer to who owns what.

Beside them, every person keeps their own named business mailbox, private by default. A colleague joins a single conversation when you pull them in — not by CC, not by forward, and never by opening the whole mailbox.

Shared inboxes and a private mailbox in one rail — stylised illustration.

Desk · Collaboration

Discuss the conversation inside it

Internal notes and @mentions live inside the conversation they are about, in a space structurally separate from the reply box — a private remark about a customer cannot be sent to that customer, because the send path cannot reach it.

Side conversations and tasks let a thread carry its own work without spawning a parallel tool.

A mention pulls one colleague into one conversation — stylised illustration.

Desk · Time

Measured honestly, disclosed honestly

Response goals run against your business hours and holidays, so nobody is measured against a clock that ticked overnight.

Reports show volumes, response times, what is waiting and who is carrying the load — computed from metadata, honouring each person's analytics consent, and never reading message bodies.

Response goals run on business hours; reports read metadata only — stylised illustration.

Desk · Channels

Email first, done properly

Microsoft 365, Google Workspace and IMAP mailboxes connect as channels. Threading, sending from your real addresses and deliverability ride on your provider — the workspace adds the collaboration, not another mail server.

Connect the mailboxes your company already has — stylised illustration.

Team

Talk inside, right next to outside

The conversation about the work lives next to the work: direct messages with teammates sit in the same workspace as the customer conversations they are about — no copy-pasting a thread into a chat tool to discuss it.

And inside any customer conversation, notes, @mentions and side conversations keep the discussion attached to its subject.

Direct messages live beside the customer conversations they are about — stylised illustration.

CRM

The CRM that keeps itself

This is the heart of the difference. Database CRMs ask your revenue people to stop working and go type updates into a system. MimiDesk's CRM is built where the work already happens: contacts and companies are created from real correspondence, and the customer's whole history sits beside every conversation — no switching, no data entry, no stale records.

Deals and pipelines are rolling out on the same principle: updated by the conversation, not beside it.

The record builds itself from real correspondence — nobody typed this in — stylised illustration.

Knowledge

Answers that become reusable

Your team answers the same good questions every week — today those answers live in your conversations, and search finds them when you need them again.

The Knowledge app makes them reusable on purpose: articles written from real answers, and a help centre your customers can read — it is on its way, and this page will say more only when it ships.

The Knowledge app, as planned — stylised illustration of what is coming — stylised illustration.

Projects

The thread carries its own work

Work that comes out of a conversation stays attached to it: tasks live on the thread that created them, so "what did we promise, and is it done?" is answered where the promise was made.

A full Projects app for the whole hub is part of the MimiDesk direction — it will appear here when it ships, not before.

Tasks attach to the conversation they came from — stylised illustration.

Insights

See what matters, without reading anyone's mail

Volumes, response times against business hours, what is waiting and who is carrying the load — computed from metadata, honouring each person's analytics consent, and never reading message bodies. Leaders see the shape of the work; the mail stays where it belongs.

Volumes, response times and waiting — computed from metadata only — stylised illustration.

Work your conversations in one place