A queue that plans your week.
Every connection request, message and email in one list, each with the time it will go. Over the limit? It moves to the next working day. Nothing dropped. Nothing doubled.
14 days on us. No card needed.
See the day before it happens.
Bulk actions and Autopilot share one queue, so one list tells you everything that is about to go out.
A time on every action
Scheduled, planned for a later day, delayed, waiting or paused. Each row says which, and why.
A hand on every row
Send now, pause, delay by fifteen minutes up to a week, or cancel. One lead or a whole selection.
The people, companies and numbers in these examples are invented.
Daily ceilings you cannot raise past.
The defaults are cautious. The ceilings are the wall.
One budget per kind of action
Connection requests, messages, emails and profile reads each have a daily limit. Bulk actions and Autopilot spend from the same pool.
Defaults you can lower
25 connection requests, 50 messages, 30 emails and 50 profile reads a day. Set them lower any time.
Ceilings you cannot raise
40 connection requests, 70 messages, 30 emails and 150 profile reads a day. Opusend can tighten a ceiling for everyone. It never loosens one without a release.
A weekly budget behind it
LinkedIn rations invitations by the week too. Opusend keeps a weekly budget of your daily limit times your working days.
Gaps that look like you.
A person takes time over each action. So does the queue.
A connection request
20 to 60 seconds before the next one, or 45 to 120 when it carries a note.
A message or an email
90 to 240 seconds. It takes a person that long to read a thread and type.
A profile read
30 to 90 seconds when you queue many. A single read is instant.
Working hours only
Nine to five on weekdays in your own timezone, unless you set otherwise.
The queue says no so you do not have to.
Checks run when an action is queued and again right before it goes.
One action per lead
The same lead is not queued twice for the same step, and nobody is contacted twice in 24 hours.
Space between messages
A follow-up waits at least two days after the first message and three after the last follow-up. A message right after an accepted connection is fine.
It reads the thread first
Before it writes to someone, it checks the conversation. If they already replied, it does not send.
Skips are not failures
A step that was correctly skipped is told apart from one that broke. Failed ones can be retried in one click.
Completed work, for the whole team.
See what happened, not just what is planned.
Show completed
Reveal what already went out over the last 30 days, Autopilot's actions included.
The whole team
A team admin sees completed work across seats, with a filter by member. A queue about to run stays with its owner.