How Harp answers a reply within minutes
The Harp team ·
The most expensive moment in outbound is the reply nobody sees for a day. We built Harp’s reply loop so that never happens, without handing an agent the keys to your inbox.
1. Stop first
Harp watches the mailbox that sent the sequence. The moment a reply, bounce or unsubscribe arrives, that person’s sequence stops. That happens before any AI is involved, so a follow-up never goes to someone who already answered.
2. Wake the agent
The reply becomes an event, and Harp wakes your agent during your working hours. The agent claims the event and gets the context with it: the thread, the account, the research answers and the sequence.
3. Answer inside guardrails
- The recipient, the thread and the mailbox are fixed by Harp. The agent cannot send the reply anywhere else.
- One reply per inbound message.
- If a person on your team has already answered in the thread, the agent stays out of it.
- The agent may only state product facts you have written down. Anything else goes to a person.
4. Book the meeting
If the prospect wants to talk, the agent offers free times from the receiving mailbox’s own calendar and books the one they pick, with a Meet link and an invite, inside your working hours and once per contact.
The one thing a person always decides
LinkedIn replies. The agent drafts them, but nothing is sent until you say yes in Slack. A LinkedIn message is more personal and harder to take back, so it gets a human every time.