1pm
Start free trial
← All help articles

How lead reply emails work

leadstroubleshooting
How lead reply emails work

When you reply to a lead from the inbox, the email goes out, the lead answers, and their answer lands straight back under the same conversation. None of that needs you to set up a mailbox, copy an address, or forward anything. This article opens up what's happening behind that: which address your reply is sent from, which address the lead's reply comes back to, and why it's built the way it is. It's the kind of thing that looks slightly odd the first time you spot it in an email header, so it's worth understanding once.

If you just want to send replies and get on with your day, you don't need any of this. The short version: it works, it threads, and the lead sees your venue's name, not ours.

The short version

  • Your reply is sent from your venue's name, on a verified 1pm sending address ([email protected] by default), or from your own domain if you've set that up.
  • The lead's reply comes back to a private, per-lead address on reply.1pm.app. That address is unique to that one conversation.
  • When the lead replies to it, 1pm catches the message, matches it to the right lead by that private address, and drops it into the thread. You get an unread badge and, if you're looking at the inbox, it appears live.

Everything below is the detail behind those three lines.

Who the email looks like it's from

When a lead reads your reply, the sender shows your venue's name, taken from your display name in 1pm. The lead enquired with you, not with 1pm, so the email should read as yours. That's deliberate.

The address behind that name is, by default, [email protected]. A few things about that address:

  • mail.1pm.app is a dedicated sending domain. It's set up (with the technical records mail providers check, like SPF and DKIM) so that mail from it is trusted and lands in inboxes rather than spam folders. This is the single biggest reason replies go out from our domain by default rather than yours: your own domain may not be set up to send mail this way, and getting that wrong sends your replies to junk.
  • It's a send-only address. There's no inbox sitting behind [email protected]. If a lead were to reply to the From address directly (most won't, see the next section), nothing would be listening there. That's on purpose, and it's why the reply address is separate.

If you'd rather your replies come from your own domain (so they read as [email protected]), you can. See "Sending from your own domain" below.

Where the lead's reply goes

Here's the part that does the clever work. Every lead gets their own unique reply address, and your reply carries it as a hidden "reply to this" instruction. When the lead hits Reply in their email app, their message is addressed to that private address rather than to the From address.

The address looks something like:

[email protected]

Two pieces matter there:

  • your-venue is a readable tag made from your venue name. It's purely cosmetic, so the address reads as yours at a glance. It carries no meaning and nothing depends on it.
  • 7f3a9c2e8b14 (the part after the dot) is a long, random, unguessable token. This is the bit that does the routing. It's unique to this one lead's conversation, and it's how 1pm knows which lead a reply belongs to.

reply.1pm.app is a separate inbound subdomain, set up only to receive mail and hand it to 1pm. It's kept deliberately apart from everything else: it is not our real [email protected] inbox, and it is not your venue's mailbox. Nothing lands in a human's inbox here. Mail to it flows straight into the routing described next.

So a lead's reply doesn't go to a shared mailbox that you'd then have to sort through. It goes to an address that belongs to that conversation and no other.

How the reply finds its way back into the thread

When the lead sends their reply:

  1. It arrives at their personal [email protected] address.
  2. 1pm reads the token out of that address and matches it to the exact lead it belongs to.
  3. We pull in the message, trim off the quoted "On [date] you wrote..." history so the thread stays readable, and append it as a new bubble in that lead's conversation.
  4. The lead's row picks up an unread badge, and if you have the inbox open, the new reply shows up live without a refresh. You're also notified.

A nice side effect of routing on the address rather than the sender: it still works even if the lead replies from a different email address than the one they enquired with. Plenty of people enquire from a phone, then reply later from a work account. Because the private token rides in the address they're replying to, not in who they are, their answer still lands in the right place.

There's also some quiet plumbing that keeps the conversation grouped together in the lead's own email app, so your back-and-forth shows up as one thread on their side, not a pile of unrelated messages. You don't have to do anything for that; it's automatic.

Sending from your own domain

By default everything goes from [email protected]. If you'd prefer your replies came from your own domain, set an Enquiry sender address on your Profile page (for example [email protected]).

One important condition: sending from your own domain only works once that domain has been verified with us. This is the same trust setup (SPF, DKIM) that makes our default address deliver reliably. Without it, mail providers can't confirm you authorized 1pm to send on your behalf, and your replies get treated as suspicious and sent to spam. So:

  • Leave the field blank until your domain is verified. Your replies keep sending reliably from our address in the meantime.
  • To set it up, contact support and we'll walk you through verifying the domain, then switch it on.

Whichever From address you use, the reply routing doesn't change. The lead's reply still comes back to a private reply.1pm.app address and threads into the inbox exactly the same way. The From address is about how the sender reads; the reply address is about where answers go, and those two jobs are kept separate on purpose.

Why it's built this way

A few decisions worth spelling out, because each one is solving a real problem:

  • Your name on the email, not ours. The lead is talking to your venue. Showing your venue as the sender keeps the relationship yours and makes the email feel like a normal reply from you, not a notification from some tool.
  • A private address per lead, instead of one shared mailbox. This is what lets a reply thread itself automatically. There's no inbox for you to monitor, no rules to set up, no risk of two leads' messages getting crossed. The address itself tells 1pm which conversation a reply belongs to.
  • A separate domain just for receiving. Keeping the inbound reply.1pm.app apart from the sending domain (and from any real inbox) means receiving a lead's reply never touches a mailbox a person reads. It's a clean, dedicated path.
  • An unguessable token, not your name or the lead's. The readable tag in the address is only decoration. All of the actual routing rides on the random token, so the address can be shown openly without anyone being able to guess another lead's address from it.
  • A verified sending domain by default. Deliverability is the whole game with this kind of email. A reply that lands in the lead's spam folder may as well not have been sent. Defaulting to our verified domain (and requiring verification before you use your own) is what keeps replies actually arriving.

What this means in practice

  • Is the reply.1pm.app address a problem? No. Most leads never see it. It sits in the technical "reply to" field, and their email app just uses it when they hit Reply. If a curious lead does look, it reads with your venue name in front of it.
  • Can I just use my normal email instead? You can run the whole conversation from the 1pm inbox and never touch your mail client, which is the point. If you'd rather the sender read as your own domain, set up a verified Enquiry sender address (above). The reply routing stays the same either way.
  • What if I mark a lead as spam? 1pm never emails a lead you've marked as spam, and you can't reply to one. Marking spam takes that sender out of your working conversation entirely.
  • The acknowledgement a lead gets when they first enquire comes from the same sending address, so it reads from your venue too. It's part of the same setup.

Related articles