About Mailtwine · A note from the founder

Let AI do the work.
You stay in charge.

I’m Nitai. I built Mailtwine because email should ask less of your time without asking you to give up control. AI can prepare replies, help fulfill requests, and keep work moving. You decide how far it goes.

Start free beta Read the story ↓
Why I built it

The inbox has had enough of our time.

I built Helpmonks and have spent years helping teams manage customer conversations. Again and again, I saw capable people spending their day sorting messages, finding context, writing familiar replies, and remembering who needed a follow-up.

The work matters. A customer needs an answer. A request needs an owner. A promise needs to be kept. But so much of the effort is getting ready to do the work, rather than actually doing it.

AI made me ask a fairly obvious question: why are we still doing all of that preparation ourselves? If software can understand what an email is asking for, it should be able to help move it forward.

Help with the request, not just the wording.

A polished draft is useful. So is knowing which message needs attention, routing a request to the right person, preparing a routine response, and following up when a conversation goes quiet. Those are the everyday jobs I want Mailtwine to take off your plate.

Sometimes helping fulfill a request means getting an answer ready. Sometimes it means handing the work to someone who can act. Sometimes an approved rule can handle the routine reply automatically. The point is to move the work forward with the authority you have given it.

Automation should earn your trust.

I would not want an assistant making commitments on my behalf just because it could. Your relationships, your promises, your reputation: you are the one who has to live with the answer.

Mailtwine starts review-first. You can review and edit a draft before sending it. Automatic sending requires an admin to approve the specific rule version; material changes to that rule revoke its authority. The thread keeps an audit trail so you can see what happened.

That is what human control means to me. You choose what to delegate and what still needs your judgment. The goal is less repetitive work, with clear boundaries around the decisions that matter.

Useful on its own. Built around your email.

You do not need another product to start using Mailtwine. Keep your existing email accounts, connect them, and use Mailtwine to prioritize messages, prepare replies, track follow-ups, and organize the work in front of you.

Start with one workflow you want help with. Review the results. Decide what you are comfortable delegating. You can explore the email workflows and approval controls or find the apps that fit the way you work.

Pencil portrait of Nitai, founder of Mailtwine

Nitai Aventaggiato
Founder of Mailtwine and Helpmonks
Find me online ↗

Mailtwine + Streamient

Now give it the knowledge your company already has.

This is where I get particularly excited. Mailtwine can work independently. Connect Streamient, and it can also draw on the shared knowledge your company has already collected: product details, procedures, policies, decisions and lessons from earlier work.

Think about a customer asking how to get started. The useful answer is in your onboarding notes. A question about a policy? Your team has already written it down. A recurring support issue? There is a known solution. Connected knowledge gives Mailtwine something specific to work from when preparing the reply.

Mailtwine handles the email workflow. Streamient supplies the maintained company knowledge. Together, they can turn a repeated cycle of searching and explaining into a reply that already has the relevant context behind it.

That is the combination I see becoming a powerhouse for a company: the inbox connected to what the team knows, with people still deciding what should happen. Adding knowledge does not expand Mailtwine’s permission to send. Your approval rules still apply.

Streamient is optional. Add it when shared company knowledge is the missing piece, and keep that knowledge useful for your people and other connected AI tools too.

The story behind Streamient ↗
The people behind it

One team. A few familiar problems.

I’m building Mailtwine with the Helpmonks Labs team. Our other projects tackle the work around it: Helpmonks for shared customer email, Streamient for shared knowledge, Razuna for digital assets, Managani for product feedback and updates, and Typerelay for reusable snippets and text expansion.

What would you trust an email assistant to handle?

Tell me which part of email takes too much of your day, and which decisions you would always want to keep. Both answers help shape Mailtwine.

Say hello ↗