Real email, from your own domain.
Replies from your inbox go out as ordinary email — from your domain once you verify it, or ours to start. Customers just hit reply, and it threads back into the same conversation. No portal, no shared Gmail chaos.
They just hit reply.
You answer from the inbox; it arrives as normal email. When they reply, it threads right back — one continuous conversation with a real person.
The monthly export just spins forever. Any idea what's up?
Hey Maya — fixed a stuck job on our end, your export should run now. Sorry for the wait!
from [email protected]
That did it — thank you! 🙏
The customer never leaves their inbox. It all lands back in yours.
Your domain, or ours to start.
Send from a shared usepresence domain on day one, and move to your own custom sender domain whenever you're ready.
Shared sending domain
Replies go out from a shared usepresence domain right away — nothing to configure, no DNS to touch. Perfect for getting your first replies out today.
Your own sender domain
Verify a domain by adding a few DNS records, and replies go
out as [email protected].
We show you the exact records and check them for you at
Settings → Email.
Let email-only customers in.
Some people will always just email [email protected].
Turn on receiving, forward that address to the one we give
you, and their mail becomes a conversation in the same inbox —
no widget, no API, no code.
It's opt-in and reversible: flip it off and the forwarding address retires for good. Spam is filtered before it reaches you, and replies keep threading like everything else.
How to set up forwarding-
One forwarding address
Point your support@ at it once. Any provider that can forward works.
-
Spam filtered on the way in
Junk gets dropped before it reaches you, so the inbox stays real.
-
No shared Gmail chaos
No forwarding rules to babysit, no double replies, no lost threads.
Questions, answered.
Do replies come from my own domain?
They can. Verify a custom sender domain — you add a few DNS records and we handle the rest — and replies go out as {you}@yourdomain.com. Not ready to touch DNS? Replies go from a shared usepresence sending domain until you are, so you can start on day one.
How does the customer reply back?
They just hit reply in their normal email client. Their answer threads straight back into the same conversation in your inbox — no portal, no account, no "click here to view this ticket." From their side it is one continuous thread with a real person.
Can email-only customers reach me?
Yes, if you turn on receiving. You get a forwarding address, point your support@ address at it with a forwarding rule at your email provider, and every message customers email lands as a conversation. No widget, no API, no code.
Is this a shared mailbox in Gmail?
No — and that is the point. No forwarding rules to babysit, no one accidentally replying twice, no losing a thread in a personal inbox. Everything lands in one shared inbox with the customer context beside it.
What about spam?
Junk is filtered before it reaches you, so your inbox stays the real conversations. Replies keep threading, and if you ever turn receiving off, that forwarding address retires for good.
Support that sounds like you. By email.
Send from your domain, let customers reply, and keep every thread in one place. Free to start — no card required.