Email for teams that handle clients’ matters

Email looks clearer from up here.

MailGiraffe gathers every mailbox your team uses into one view, sorted by client and matter. You can finally see who’s on what, what’s due and what nobody has picked up. AI agents you set up yourself prepare the replies, and a person always sends them.

Free to start.

The MailGiraffe dashboard: conversations from all mailboxes, grouped by client and matter, each with a deadline, the person responsible and a status. Three new messages that match no client are listed first.

Giraffe fact: A giraffe’s neck has seven vertebrae, the same number as yours.

Same mail. Longer neck.

Nothing moves in your mailboxes. You just get to see all of them at once. Stretch up and look down.

Drag me up

Three inboxes, each its own little world.

13 messages in 3 mailboxes

office@olga@filings@

Tereza Králová3:42 PM

Consultation: notice on my lease

Klára Nováková2:48 PM

Re: Lease agreement, comments

Klára Nováková2:48 PM

Re: Lease agreement, comments

District Court Vzorov10:21 AM

Ref. 2026/041: summons to hearing

District Court Vzorov10:21 AM

Ref. 2026/041: summons to hearing

Klára Nováková9:05 AM

2026/017: handover protocol

Marek Horák8:15 AM

Complaint: facade defects

Daniel ČernýOct 30

Enquiry: setting up a company

Petr BeránekOct 30

Delta acquisition: due diligence

Petr BeránekOct 30

Delta acquisition: due diligence

Jana MaláOct 30

Inheritance: documents

District Court VzorovOct 29

Ref. 2026/063: complete the filing

Petr BeránekOct 28

Delta acquisition: draft SPA

Who’s answering Klára?

When’s that hearing?

Didn’t we reply to this?

Who's on what?: Someone, surely.
What's due first?: Good question.
What could slip?: Hopefully nothing.

Giraffe fact: Wild giraffes sleep two hours a day at most, in short naps.

Every mailbox, checked about once a minute.

Connect the Gmail and IMAP accounts your team already uses. When a thread lands in two of them, it’s one conversation here, with one person responsible, one status and one deadline.

Reading changes nothing: no message is marked as read, moved or sent.
You decide who can see each mailbox, and which agent it opens with.
In Gmail, the state can show up as labels too, if you’d like that.

MG/Status/Awaiting reviewMG/Responsible/Olga NovákováMG/Client/ACME Reality

The message sources page: two connected mailboxes, one over Gmail and one over IMAP, each with the managers and readers who can see it, its primary agent, the addresses it sends as and its signature, and a switch to show the state as labels in Gmail.

The dialog for connecting a mailbox, saying that reading it changes nothing in it: nothing is marked as read, moved or sent. It also says that MailGiraffe sends only when a person presses Send, and that agents can't.

The clients and matters page: each client with its domain, and under it the matters with their reference numbers and how many conversations each holds.

Giraffe fact: No two giraffes have the same spots.

Every client has a pattern too.

Give a client its addresses or domain, and a matter its reference. Conversations then find their own place. What no rule can place waits at the top of the dashboard, so it can’t quietly go missing.

Subject reference
Body reference
Address
Domain

These are plain rules, and a choice made by a person is never overwritten. Sorting sends nothing to any AI provider.

Giraffe fact: A giraffe can spot movement up to a mile away.

See deadlines from just as far.

Every conversation carries a status, a person responsible and a deadline. So “did anyone deal with this?” has one answer, and everyone can see it. Group it all by client, status or person, whichever question you have today.

New
Pending
Awaiting review
Completed

A new message from outside reopens a completed conversation by itself. And older mail comes in as completed, so connecting a mailbox doesn’t bury the dashboard.

A conversation opened from the dashboard, with its status, person responsible, deadline, client and matter at the top, its messages below, and an assistant beside it.

Giraffe fact: A group of giraffes is called a tower.

Build a tower of your own.

Set up one AI agent or a whole team of them. Each has its own name, model and instructions, and sits right beside the conversation you’re reading. Ask it to prepare a reply, sum up a thread, or tell you what’s burning.

The Trainee

Prepares first replies to clients and sums up long threads.

On your Anthropic key

The Researcher

Looks up case law through your own MCP tools.

On your OpenAI key

The Lookout

Tells you what’s most urgent this week, and what nobody has picked up.

On your Anthropic key

Your next one

A name, a model and instructions. They decide what it’s for and how it writes.

They run when someone asks.

Nothing starts an agent because mail arrived. Your mail reaches the AI provider only when a person asks an agent about it.

They reach what you reach.

A giraffe’s tongue is about half a meter long. An agent’s reach is exactly that of the person asking, through the same access rules.

They run on your own key.

Anthropic or OpenAI, with your API key, stored encrypted. You choose who on the team may use which agent.

They use the tools you pick.

Connect your own MCP servers, and hand each agent only the tools it should have.

The agents page: two agents, each with its provider, model and purpose, the readers who can use it and its MCP tools.

The dialog for a new agent, with its name, purpose, AI connection, model and instructions. It notes that whatever the agent is told, it can't send anything, and it reaches only what the person asking can reach.

The assistant panel, in Czech: asked what is most urgent this week, an agent lists three conversations with their deadlines, and adds that a summons has nobody responsible yet. — Asked in Czech, answered in Czech: “What’s most urgent this week?” It lists three deadlines, then adds: “The summons in 2026/041 has nobody responsible yet.”

Giraffe fact: Giraffes barely make a sound. Their night-time hum wasn’t documented until 2015.

Your agents can’t send a thing.

They read, prepare drafts and, when you ask, file conversations under clients and matters, new or existing. There they stop: there’s no tool for an agent to send with. A reply goes out only when a person has read it and pressed Send, in MailGiraffe or from the mailbox’s own Drafts folder.

A draft reply prepared by an agent, in an editor with buttons for bold, italic, underline, lists, links and removing formatting. Below the message are the mailbox’s signature, filled in for the person sending, a button to attach files with one file attached, and the buttons Send and Place in the mailbox, and a note says: Nothing goes out until you press Send, and agents have no way to press it.

Reading leaves no trace.

Nothing in your mailboxes changes when it’s read. The only additions are what you send or place there, and labels if you turn them on.

Everyone sees what’s theirs.

Readers get the mailboxes assigned to them, message by message: in lists, in search and through an agent alike.

Keys stay locked up.

Mailbox credentials and API keys are stored encrypted, and aren’t shown again.

Senders stay in the dark.

Remote images stay off until someone asks for them, because they’re how a sender learns a message was opened.

One thing only you could add: if you give an agent a tool from your own MCP server, and that tool can send mail, then it can send mail. That’s why tools are picked one at a time, per agent.

Giraffe fact: A giraffe calf is usually on its feet within an hour of being born.

We’re starting from the hooves up.

MailGiraffe is new and still growing, one hoof at a time. Connect a mailbox and see what your mail looks like from up here. It’s free to start.

Back up the neck