Inbox and replies

The Inbox is where outreach becomes conversation: drafts waiting for review pinned on top, then one conversation per contact with unread counts. Templates and the sender profile live in its settings.

How reply detection works

leadrack has no inbox of its own and doesn't receive mail. Instead, if your connected mailbox includes IMAP details, leadrack polls that inbox every ten minutes and matches what it finds against mail it sent. It matches by the reply's threading headers first, with a careful fallback for "Re:" subjects from known contacts. Bounce reports are recognized too, including the machine-generated kind.

Two consequences worth knowing. No IMAP means no reply detection (a Resend-only setup sends fine but can't see answers). And anything in your inbox that doesn't match leadrack's own sent mail is ignored entirely, with no record and no trace. Your unrelated mail is none of leadrack's business.

What a reply does

A detected reply threads into the contact's conversation, logs on the lead's timeline, bumps the inbox unread count, and puts a "Replied" badge on the board card. It does not move the card to another stage. A reply might be "yes please" or "never contact me again", and only you know which column that is.

A detected bounce does more: the email is marked bounced and the contact's address is suppressed from all future sending.

Replying from the inbox threads properly, with correct headers and a "Re:" subject, so the conversation stays intact on both ends.

The guardrails

Every send, human or agent, passes the same checks:

• Suppression: a contact who bounced, complained, or unsubscribed is never emailed again, on any path.
• Unsubscribe: every sent email carries a one-click unsubscribe link and your postal address, rendered at send time. The link works without login, repeat clicks are harmless, and the flip is logged on the timeline.
• Verified sending only: the Resend path requires a verified domain. A connected mailbox is its own proof.
• Daily send cap: a per-plan ceiling on outreach per rolling day. Drafts don't consume it, and neither do failed sends.
• Delivery events: bounces and spam complaints reported by the provider suppress the contact just like IMAP-detected ones.

The escape hatch

No sending setup yet? A draft can be handed off to Gmail as a prefilled compose window in your own account. leadrack logs the export on the timeline and steps back. Mail sent from your own mailbox is yours, compliance included.