The Connection Queue
SDRPilot never fires connection requests the moment it finds somebody. A lead that qualifies joins a queue, and the queue is drained inside your daily limit and your active hours. The Queue tab on the Connections page is where you see that backlog and steer it.
What “waiting” means
A row in the queue is a connection request that has been approved by your rules but not sent yet. It is waiting for one of three things: today’s sending budget, your active hours window, or its turn behind higher priority sources. Nothing in the queue has touched LinkedIn yet, so anything here can still be pulled back without the other person ever knowing.
Requests that have already gone out are not in this tab. They are pending invitations, and they follow the rules further down this page.
What the tab shows
Each row carries the lead’s name and headline, their country, their follower count, the AI score they were given, the source they came from and when they joined the queue. You can switch between Queued and Needs approval, and filter by country and by minimum score, which is usually enough to find the group you want to remove.
Withdrawing
Select the rows you do not want and press Withdraw selected. They are marked as withdrawn by you and the sender skips them for good. Requests that were already sent are never touched by this.
Needs approval
An agent set to semi-auto or assist does not send on its own. It still finds and scores people, and it still writes the connection note, but every request it prepares stops in the Needs approval view of this tab with the drafted note next to the name. Nothing goes out until you act on it.
Tick the rows you want and press Approve selected. Approved requests move back into the queue and are sent right away inside today’s budget and your active hours; whatever does not fit today goes out on the next hourly run. The note that is sent is the one you read and approved, word for word. Press Reject selected to drop a request instead; that works like withdrawing, and the person is never contacted.
An agent set to full auto skips this view entirely: its requests go straight into the queue and out inside your limits.
Re-check against ICP
Changing your ICP changes who gets queued from now on. It deliberately does not touch rows that are already queued, because those were approved under the rules that were in force at the time and silently deleting them would be a surprise.
Re-check against ICP is how you apply the new rules to the backlog. It runs your current hard gates over every waiting row, and it runs in two steps.
- First it shows you what it would do: how many rows it examined, how many it would withdraw, and which gate each group failed.
- If you are happy with that, apply it and the withdrawals happen.
This uses the hard gates only, so it is fast, it is free, and it is predictable. It is the right tool after you add a country rule, a language rule or a minimum follower count.
Re-score with AI
Re-score with AI goes further. It asks the AI to judge every waiting lead again against your current profile, not just against the gates, and withdraws the ones that no longer clear your score threshold. Use it after you have rewritten the written half of your ICP, or after a rebuild from new customers has changed what a good fit looks like.
The queue only holds leads that already passed. To re-judge the ones the old profile rejected before they got here, use Re-score with AI on the Leads page.
Re-scoring asks the AI a question per lead and is included in your plan. It is slower than a re-check, so trim the obvious rejects with a re-check first.
Invitations that were already sent
An invitation that goes unanswered still counts against you. LinkedIn limits how many invitations can sit pending, and a pile of old ones slowly starves your new sending.
SDRPilot handles that for you. Sending pauses while too many invitations are still unanswered, and by default that ceiling is a month of your own sending, which is your daily limit multiplied by 30. Invitations older than 30 days are withdrawn for you automatically, a few at a time rather than in one sweep, so the backlog clears without a burst of activity on the account. You can set your own ceiling on the seat, or leave the field empty to keep it automatic. See Daily Limits and Active Hours.
Why the queue does not shrink by itself when you tighten the ICP
This catches people out, so it is worth stating plainly. Tightening a gate affects the next lead that gets scored. It does not reach back into the queue. If you have just added a country rule and you want the Nigerian and Pakistani profiles that are already queued gone, run Re-check against ICP and apply it. Until you do, they will be sent.
Everything on this page is available through the API and through the MCP tools as well, so a Claude session can list your queue, withdraw from it and re-check it for you. See Using the API and MCP Tools.