Prospecting#
Build a file of businesses to approach, write to them by email or SMS, know what became of each message, and follow up on those who never replied — without ever writing again to an address that said no.
AI search queries public directories from a trade and a city, then visits the sites it finds to extract a way to get in touch. Every record keeps its source URL and collection date, so the provenance of each contact stays verifiable. You can also add a record by hand, or export the whole file as CSV.
A prospect reachable only by phone is a full prospect: the email address is optional. This is the most common case for local businesses, and SMS sequences serve exactly that case.
New
newNever approached. This is the only status a first-contact sequence recruits.
Contacted
contactedA message ACTUALLY went out. The status advances on confirmed send, never on drafting or queuing: an email refused by the provider contacted nobody. The send counter and the date of the last message advance at the same time.
Replied
repliedA message came back from them into the inbox — email, website chat, DM. A reply immediately stops every follow-up: insisting after a yes is the surest way to lose them. The “View reply” button opens the conversation.
Excluded
excludedAn explicit human decision. No automatic send ever undoes it.
Every record shows the state of the LAST email sent to it: Sent, Delivered, Opened, Clicked, Bounced, Marked as spam, or Send failed. The last one, not the best of the history: the question this state answers is “should I follow up now?”.
“Opened” is a hint, not proof. An open is measured by an image load: a mail client that preloads produces one without anyone having read anything, and someone reading without loading images produces none. That is why the app never shows “Unread”. “Delivered” and “Bounced”, on the other hand, are facts: the receiving server accepted or refused.
A bounce or a spam complaint CLOSES the address: it is removed from every later send, automatically. A bounce reopens if the address becomes valid again; a complaint never does. This is what protects your sending domain's reputation.
A sequence is a series of spaced messages, each conditioned on what the previous one did (not opened, not clicked, no reply). It runs on its own, by email or SMS, and stops by itself on a reply, a bounce or an unsubscribe. What changes between the three audiences is only WHO it recruits.
A list I provide
For a one-off announcement. Contacts are typed in by hand and linked to no record: no status advances.
My prospects
Prospects still to be contacted. The sequence keeps feeding itself: records found after it was created join automatically, with no need to recreate one after each search.
Follow up on no-replies
Prospects already contacted who never replied. See the next section.
A prospect belongs to only ONE prospecting sequence at a time. Two active sequences on the same project cannot write to the same person in parallel.
Create a sequence with the “Follow up on prospects who never replied” audience, write a DIFFERENT message in it, and set two bounds: after how many days to follow up, and past how many received messages to stop insisting. By default: 14 days and 3 messages in total, that is at most two follow-ups after the first contact.
The decision is yours, the execution is automatic: once the sequence is created, prospects join it on their own as they pass the delay. It may therefore start out empty, which is normal. Excluded outright: those who replied, those you excluded, those whose address bounced or who unsubscribed, and those already receiving messages from another sequence.
By default, emails go out from a shared platform domain. In Settings → Email domain, declare your own: the platform gives you the DNS records to create at your host (SPF, DKIM and domain verification). Once those records propagate, the domain turns verified and your campaigns go out from your address.
A domain of your own markedly improves deliverability, and it is the one that carries the reputation your sends build. That is also why automatically closing bouncing addresses matters: it protects an asset that is yours.
Was this documentation helpful?