Built around unfinished work
Magpie tracks Magpie Loops — tasks, watches, milestones and goals — across the channels your ops team already uses. Start with Outlook; expand from there.
Magpie Loops
Unfinished work with an owner and a next step
A Magpie Loop is one piece of team work — a task, a watch, a milestone or a goal — tied to the conversation that moves it. Magpie spots what needs attention; people decide what becomes a Loop and when it closes.
Learn moreOutlook
Built on the mail your ops team already lives in
Magpie works on top of Microsoft Outlook for UK Microsoft 365 teams. It reads your mailbox to suggest Loops — private to you until you share a thread. Names, addresses and IDs are never sent to the AI model.
Learn moreOwner-private until shared
No shared inbox reading everyone's mail
Magpie is not a CRM or a team queue. Mail stays owner-private until someone discloses a thread into a Loop. That is the wedge for ops teams who need accountability without opening every mailbox to everyone.
Learn moreRolling out for the conversations that already run there
Ops work often starts on WhatsApp with distributors, hauliers or site contacts, then jumps to email. Magpie is expanding WhatsApp context into Magpie Loops so handoffs do not die when the channel changes.
Learn moreApps
Mac, Windows and iPhone
Magpie runs where ops leads already work — desktop on Mac and Windows, and iPhone for when you are away from the desk. Chat in Magpie is available; Teams can stay for the chat your company already standardized on.
Learn moreFewer dropped handoffs
The point isn't another inbox. It's a clear next step on every piece of work that still matters.
Every Loop has someone responsible — not a shared pile.
Open, waiting or blocked stays visible until a person closes it.
Messages and attachments stay with the work they belong to.
We're looking for a few more pilot teams
Best for teams of 5 to 50 on Microsoft 365 who coordinate clients, suppliers or field staff.
Apply for the pilot