Your mailbox, same window.
Point Hepo at the support address printed on your invoices. Mail arrives in the same merged inbox, threads stay intact, and the answer leaves from your own server.
The customers who write email are the angry ones
People open a chat widget when they have a question. They open their mail client when something went properly wrong, which makes this the channel worth doing carefully.
Threads that hold
Correct reply headers on every message. Their mail client shows one conversation, not eleven.
Clean text for the agent
Quoted history and signatures removed before the model sees anything, so the context is the message and not the archive.
Sent from you
Your domain, your SMTP, your deliverability record. Nothing routes through a shared sender.
Connecting it
- Your mailbox, your domain
- IMAP in, SMTP out, through the provider you already pay. Mail leaves from your server under your own SPF and DKIM.
- App passwords today
- Tencent Exmail, Aliyun Mail, Zoho, Fastmail and any host that still issues an app password work now.
- OAuth as it clears
- Google and Microsoft require OAuth with a security assessment for mailbox reading. That review is underway and each provider switches on as it completes.
Keeping it tidy
- Real threading
- Replies carry In-Reply-To and References, so the customer sees one conversation instead of a pile of loose mail.
- Written back to Sent
- Anything sent from Hepo appears in your mailbox Sent folder, with read state synced both ways.
- Quotes stripped
- Signatures, quoted history and mobile footers are removed before the agent reads it, because a badly parsed thread makes a badly reasoned answer.
- Loop protection
- Auto-Submitted and X-Autoreply headers are dropped rather than answered, so two robots never talk to each other overnight.
Once it is in
- Same inbox
- Mail sits in the merged stream next to chat, tagged by site, with the same unread behaviour.
- Same translation
- A German complaint arrives readable and your answer goes back in German.
- Same assistant
- The handbook, the functions and the automatic-handling switch apply to mail exactly as they apply to chat.
Where this is honestly still landing
Gmail and Microsoft 365 mailboxes need OAuth with a completed security assessment before anyone may read mail programmatically. That is a review process, not a feature, and it takes as long as it takes. Providers that still issue app passwords work today, and each of the big two switches on the moment its review clears.
We would rather write that here than have you find out at the connect screen.
The three things people ask
Why not just give me an address on your domain?
Because deliverability would then be our problem and your reputation. Sending through your own server means your existing SPF, DKIM and domain history do the work, and moving away later changes nothing for your customers.
My team still has the mailbox open in Outlook. Will we double-reply?
Sent mail is written back to IMAP and read state syncs, so a thread someone answered in Outlook shows as handled here. It is not a lock, but it is enough that two people rarely collide.
Does an email visitor get linked to their web session?
When the address matches a visitor who identified themselves on the site, yes: the mail joins that record and the replay comes with it. Otherwise it stays a standalone contact until an address links them.
Connect the mailbox you already read.
If your provider issues app passwords it takes about two minutes. Everything else about the channel is already built.
Free plan stays free. The AI is the only thing that ever costs you anything.