How do ProspectIn’s delays and quotas work?

Published by Karine on

At ProspectIn, we have implemented quotas but also delays between actions. This is due to the limit imposed by LinkedIn. We detail everything in this article so that you can understand how our tool works. 😊

ProspectIn quotas

When you use ProspectIn, whatever your plan, you have daily quotas. In the free plan, your quotas are set to 10 to 15 actions per type of action/day. But on the other formulas, the quotas are said to be “unlimited” within the limit imposed by LinkedIn. Indeed, LinkedIn limits the number of message/invitation/visit/follow that you can send per day, in order to avoid spam behavior. We have therefore implemented this limit to protect and guarantee the security of your account. You don’t want to have your account restricted, and neither do we. This is what sets us apart from tools like Linked Helper.

This daily limit is set between 80 and 100 connection request actions and profile follow, between 120 and 150 messages and between 160 and 200 visits, randomly, to best simulate human behavior.

Once these quotas are reached, your actions are no longer sent, until you get your quotas the next day (the quotas are updated overnight, at 2:00 UTC +1). When you get your quotas, your actions start on their own (provided you have a LinkedIn tab open).

You find your quotas in your queue:

Delays between actions and queue

To perfectly simulate human behavior and be undetectable by LinkedIn, we have set up delays between the execution of the various actions. These delays vary according to the type of action:

  • Visit: +/- 30 seconds
  • Follow-up: +/- 1 minute
  • Connection request: +/- 2 min 30
  • Message: +/- 2 min 30

You can view the delays between actions from the queue.

In your queue, the actions appear in the order in which they will be executed.

Scenarios’ actions have priority in your queue, these actions will take place before the others. For example, if you currently have “connection” actions (except scenario) in your queue, and that you launch a scenario comprising a connection request, the connection request linked to your scenario will be sent in priority.

How scenario delays work

To understand how scenario delays work, let’s take an example. When you launch a classic “visit/connection/message” scenario with a delay of 1 day between actions, a script that runs twice a day (1 p.m. UTC+1 and 1 a.m. UTC+1) analyzes when the last action was performed in order to determine whether the prospect must go to the next step or not.

If at the time of the script, the last action was carried out less than 24 hours ago, then the prospect does not go to the next step.

So if the action was performed at 11 p.m.,at the time of the script, the prospect will not go to the next step 1 hour after the script has been played, but 13h after, when the second script of the day is performed.

“first in first out”

Apart from the scenarios, for classic actions, we have implemented a “first in first out” mode. That is, the first action added = the first action performed. Actions will be performed in the order of addition if they can. For example, if you have no more quotas for an invitation action, then this will be placed at the end of your queue, and it will be performed as soon as you get your quotas back.

And if you still have questions, don’t hesitate to contact Margot on the chat, she will answer you very quickly! 😁


Amandine

Chief (Positive) Marketing Officer @ ProspectIn 😎