operational.email

Support email, together

Many projects.
One clear inbox.

Keep your projects’ support conversations in one place.
Prepare replies yourself or with your own agent.

Try demo
operational.emailExample inbox
studio.exampleNew10:42

A quick question about my plan

Alex · Can I use this for a second project?

acme.exampleYesterday

Thanks for the help!

Sam · Everything is working now.

studio.exampleMonday

Getting started with my team

Jordan · Where should I start?

studio.example

A quick question about my plan

Alexalex@example.com
10:42

Hi there,

I’m starting a second project. Can I keep its support conversations separate from my first one?

Thanks,
Alex

Reply draftSaved · Not sent

Hi Alex, you can give each project its own support address and view both in one inbox.

A focused workflow

Less switching. More context.

01

Start with your domain

Enter a domain, choose how email arrives and verify ownership.

02

See the whole conversation

Search across projects, find new messages and keep the relevant context together.

03

Work your way

Write a reply draft yourself, or give your own agent scoped access to help.

Before you start

A few useful details.

Will this change my existing email?

Forwarding keeps your current provider and MX. Direct MX moves receiving for the whole domain. You choose the method; saving your choice does not change your email settings.

How do I verify my domain?

Add a TXT record through your DNS service, then check it in Settings. Verification does not change where your email arrives.

Can I use my own agent?

Yes. Give your agent access to selected domains to read conversations and prepare reply drafts.