8.2 Smart Throttling & Delay Logic
ReactIn doesn’t just queue messages and invitations — it uses a controlled execution system to spread actions out over time and reduce the risk of LinkedIn detection.a
Written By Theo Remola
Last updated 11 months ago
⏱️ How timing is managed
When a campaign is running, ReactIn spaces out actions automatically throughout the day. That means:
No bulk sending at once
No burst of 30 messages in 5 minutes
No “bot-like” patterns detectable by LinkedIn
Instead, messages and invitations are sent one by one, with:
A short random delay between each action
A natural rhythm, similar to how a real person would behave
Built-in pauses to avoid triggering suspicion
🔄 What does this look like in practice?
Let’s say you’ve set a daily message limit of 40:
ReactIn won’t send all 40 in one go
It will spread those messages over multiple hours
Each action is delayed slightly from the last — e.g. 90s, then 115s, then 80s…
⚙️ These intervals are fixed in the backend and cannot be customized, to guarantee safe pacing for all users.
✅ Why this matters
This throttling logic helps:
Avoid LinkedIn flags and detection
Protect your account reputation
Deliver a consistent outreach flow across the day
Maintain human-like behavior without needing AI or complexity
💡 Pro tip: Balance your delays naturally—short delays can seem robotic, while overly long delays might slow your pipeline.
Ready to move on?
👉 Next Step: Shadowban Prevention →