Following up with prospects without annoying them
How many follow-ups, how far apart, at what hour and with what new reason: a polite rhythm for prospecting, and how to make an AI employee keep it for you.
A follow-up stops being annoying when it is rare, well timed and brings something new. In practice that means no more than two after the first message, several working days apart, sent in the other person's working hours, and stopping the moment they answer. Each one should give a fresh reason to reply rather than asking whether they saw the last one. An AI employee can keep that rhythm for every prospect at once, which is exactly where people usually slip.
This article is for sellers and founders who write to local businesses. It sets out the rules of a polite rhythm, shows a made-up sequence day by day, lists the habits that make people mark you as spam, and then shows which settings in xMap Flows enforce each rule so you do not have to remember them.
Five rules of a polite rhythm
- Space them out. Give people time to be busy. Several days between messages, longer before the last one.
- Stop at three. A first message and two follow-ups. Someone who has not answered three short, useful notes is telling you something.
- Write in their working hours. A message at 11pm in their city looks automated, because it is.
- Stop the moment they reply. Even a reply that says not now ends the sequence. Nothing is worse than a scheduled nudge arriving after someone has answered.
- Never start again from zero. A person you already wrote to should not get the same first message next month because they appeared in a new list.
A made-up sequence, day by day
Say Olivia sells corporate wellness classes from three studios in Melbourne and writes to offices that opened nearby. Her sequence for one office manager looks like this:
| Day | Message | The new reason it gives |
|---|---|---|
| Monday, day 1, 10:00 their time | First message | You have just moved in two streets from our studio; we run lunchtime classes for teams |
| Friday, day 5 | Follow-up one | A short schedule of the classes that fit a lunch hour, with nothing to sign |
| Wednesday of the following week, day 10 | Follow-up two | An offer to run one class at their office for the team to try; and that this is the last note |
| Any day they reply | Sequence stops | Their answer is forwarded to Olivia, who writes back herself |
A made-up example. The days fall on weekdays because messages wait for working hours.
Notice what the follow-ups do not say: just checking in, bumping this to the top, did you get my email? Each one would make sense to someone reading it first.
Habits that get you ignored or blocked
- The same text three times. If the follow-up could be pasted over the first message, it adds nothing.
- A long list in one go. Two hundred first messages on a Monday morning from a new sender look like a campaign to every filter that reads them. Spread them over days.
- Guilt in the last message. I guess you are not interested leaves a bad memory. A plain this is the last note from me is enough.
- Ignoring an unsubscribe. Someone who asked you to stop must never hear from you again, from any list.
- Following up a business that closed. Check the place is still open before the second message.
Making an AI employee keep the rhythm
The Outreach block turns each result into exactly this kind of short sequence. Here is how each rule maps to a setting:
| Rule | Where it is kept |
|---|---|
| Space them out | First follow-up after and Second follow-up after: 2, 3, 5, 7 or 14 days each |
| Stop at three | At most two follow-ups; choose Never to send only the first |
| Their working hours | Send: 08:00 to 18:00 their time, Monday to Friday, worked out from their city |
| Stop on reply | A reply ends the sequence and is forwarded to the flow's owner |
| Never start again | One sequence per person per block; Only new before it keeps old results out |
| Not too many at once | At most a day: 10, 25, 50 or 100; the rest wait for the next day |
Unsubscribed addresses and results without an address are left out, and the step says how many.
A typical flow: Nearby places finds offices opened in the last year near each studio, Only new removes those already found, xMap LLM scores each one and drafts the first message (and, if you ask it, a line for each follow-up that you place in the follow-up boxes as {{fields}}), a Filter keeps the strong fits, and Outreach sends. With Approve each first switched on, every first message waits for your OK, and you can rewrite it before it goes; follow-ups then go by themselves until the person answers.
Following up on your own conversations
Outreach handles first contact. For people you are already talking to yourself, results in xMap Flows do not carry reminders. Ask xMap, the assistant, can keep personal reminders for you instead, including one that is sent only if a person has not replied by then, when your own Outlook is connected so it can check. That keeps your own follow-ups to the same standard as the employee's: a nudge only when it is still needed.
Questions
How many follow-ups should I send?
Two at most after the first message. Outreach in xMap Flows will not send more than two, and you can choose to send none.
Does Outreach know their time zone?
It works out the receiver's time zone from their city, and sends between 08:00 and 18:00 on weekdays there unless you choose Any time.
What happens when someone replies?
The sequence stops, nothing more is sent to them from that block, and their reply is forwarded to the flow's owner.
Can I check every message before it goes?
Yes. Approve each first is on by default: every first message waits for your OK and can be rewritten. Follow-ups go on their own unless the person replies.