How do I follow up without causing lead fatigue?

Choose the next contact based on context, availability and stop signals.

Updated Open this screen
Where it happensLeadsSales coaching

There is no universal number of attempts that guarantees a sale. A fresh request does not prove immediate availability. Prioritize explicitly requested callbacks. Review the last interaction, reason for waiting, owner and next agreed step before calling again.

Use a contextual first contact when permitted, then space any follow-up according to the person's reaction and applicable rules. Agree a review time for a pending quote. For an old lead, find a current reason to reconnect. A marketing cadence is not legal permission.

Stop the relevant prospecting after an explicit objection or refusal. Respect requests for a later callback. If someone does not recognize the request, verify the context instead of insisting. Repeated silence calls for less pressure; it is neither consent nor definite proof of refusal. Coordinate colleagues and channels. Recorded call counters may omit external contacts; cumulative averages cannot establish compliance with a rolling-window limit.

Draft only, if the channel is permitted: “Hello, this is [name] from [company], about your request concerning [product]. What time would suit you? Please let us know if you no longer wish to be contacted.” Use a real identity and a functioning opt-out mechanism, not a promised STOP workflow that does not exist.

French consumer electronic marketing generally requires prior consent, subject to applicable exceptions, clear sender identification and an easy objection route. WhatsApp is not a workaround. CNIL guidance.

Where recorded, measure useful conversations by attempt number, time between contacts, objections and requested callback times. Test contextual messages on comparable groups. Do not invent read receipts or intent when events are missing.

Read next

Still missing an answer?

Support can see your account and your deliveries. Asking them is faster than searching any longer.

Contact support