Charged twice; one refund confirmed. The cancellation still needs your approval.
Reply to the customer…Send
Mimi caught you up
Third email about the same invoice. The refund went out Tuesday; the customer hasn't seen it yet.
Draft reply — waiting for you
Approve & sendEdit first
Nothing sends without a person.
3 people on this conversation
Internal note — customer never sees this
@Amira — this is the account from Thursday's call. Can you take the reply?
Customer
Timeline — logged itself
Email conversation — resolved
Reply drafted by Mimi, approved
Email conversation — refund
Details
Company
Owner
Last heard from
Nobody typed this in — the desk keeps the record as the conversation happens.
Conversations this week
Median first reply
Resolved per day
To do
In progress
Done
Search the help centre…
Articles grown from answers your team already gave.
The Desk — shared inboxes beside a private mailbox — stylised illustration.Mimi in the thread — she drafts and catches you up; you decide what sends — stylised illustration.Internal notes and mentions, right on the conversation — stylised illustration.The record fills itself from the conversation — stylised illustration.How the desk is doing, at a glance — stylised illustration.Projects beside the conversations — as planned, stylised illustration.Articles grown from real answers — as planned, stylised illustration.
Your customer story is scattered across tools.AI can't help with what it can't see.
Inbox here, chat there, deals in a database, tasks on a board — and a CRM that waits for someone to type it all in.
Microsoft 365
WhatsApp
Instagram
Messenger
Telegram
X
Google Business
Calls
support@
Live chat
SMS
Matters
One desk. The whole story.
Too many tools
The working day hops between inbox, chat, board and CRM — and every hop drops context on the floor.
No single thread
A customer's history is split across channels and mailboxes. Nobody sees it end to end.
A CRM gone stale
A database CRM is only as true as its last manual update — and busy weeks are exactly when those stop.
MimiDesk puts conversations, CRM and work on one desk, and connects to the tools you already use — starting with email, more channels on the way. Mimi works with the whole story, and so do you. See the desk
Every channel. One desk.Every conversation, in one place, in order.
Every channel lands on one desk. Email, WhatsApp, Instagram, Messenger, Telegram, X, Google Business, calls, live chat and SMS become one conversation per customer — read in order, answered by a person, with the customer's record filling itself in from what was actually said. No tabs to switch. No story to reassemble.
Stylised illustration — the conversations are invented.
Six products. One desk.
Each one built where the conversation already is — scroll, and meet them one by one.
Inbox
Assigned to me
Mentions
Snoozed
Shared
Support
Sales
Finance
Your mailbox
JLRe: renewal — annual billing from March?Email
AMIs the blue one back in stock?WhatsApp
PNInvoice 2291 shows the old addresssupport@
TBPhotos of the damaged boxTelegram
Desk — stylised illustration
Desk
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.
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. Inside any conversation, notes, @mentions and side conversations keep the discussion attached to its subject.
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.
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.
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.
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.
Already in the conversation you are in. Mimi catches you up and stays out of the way — easy to reach, hard to find annoying.
Human control
Off by default
People send
Audit log
Works without her
Context
Mimi reads the conversation you are in and catches you up: what happened, why it matters, what you can do. No brief needed.
Mimi caught you up
The customer was charged twice. Finance confirmed one charge will be refunded — the cancellation still needs your approval.
Control
Off by default for your workspace. You decide if conversation content ever reaches a model, the audit log shows exactly what was sent, and nothing she drafts goes out without a person sending it.
Mimi for this workspace
Off until an admin turns it on
Exactly what is sent, and where it goes — stated on the switch, recorded in the audit log.
Character
Never annoying, honest when uncertain, no fake intelligence. When Mimi is not sure, she says so plainly — and she never claims analysis that did not happen.
confidence"earned by accuracy"
popups"none"
when unsure"says so plainly"
system events"never dressed up as Mimi"
The rules came first
Every part of Mimi ships under the same rules. More of her lands the same way.
One shape, every catch-up
What happened, why it matters, what needs doing. Every summary follows that pattern instead of a wall of text, so a thread that ran for weeks takes a moment to pick up.
Mimi caught you up
What happened
Charged twice on the 3rd.
Why it matters
Renewal is due Friday.
What to do
Approve the refund.
The switch is yours
AI is off for every workspace until an admin turns it on — and the settings page says exactly what is sent, and where, before anyone flips it.
Mimi for this workspace
Off · admins only
Before you turn it on: what is sent, and where it goes — stated here, on the switch.
Every send on the record
The audit log records every send to a model. It records every refusal too.
09:12sent · catch-up · one conversation
09:40sent · draft reply · one conversation
10:05refused · Mimi is off here
People press send
Mimi prepares; a person sends. Nothing she drafts leaves the workspace without someone choosing to send it.
Draft · by Mimi
Hi Lena — 10:10 works. I've moved the slot; see you then.
Sends only when you doSend
Honest when unsure
Confidence is earned by accuracy, not performed. When Mimi is not sure, she says so plainly — and she never claims analysis that did not happen.
Mimi
I'm not sure whether the refund went through — finance hasn't replied in this conversation yet.
Works without her
Every part of MimiDesk works with Mimi switched off. She adds to the workflow; she never gates it.
MimiOff
Shared inboxes
Conversations
Customer timelines
Assignments
DoneOn the record
Amira
Mimi, catch me up on Nordwind — I've been out two days.
Mimi
14 messages, 3 people. Jonas was charged twice on the 3rd and finance confirmed one refund. Renewal is due Friday.
Tagged BillingAssigned to youRenewal date updated
Amira
Approve the refund and let Jonas know.
Mimi
Done. €84.50 refunded and Jonas has the confirmation — that's inside your billing rule.
Refund approved · recordedReply sent to Jonas
Acts within your permissionsEvery step logged
The intelligence that already knows the conversation