Twenty-five connection requests, then stop
Accounts that fire connection requests like a script get restricted. The people who hit that wall are often not running anything exotic. They bought a tool that clicks Connect a few hundred times a week and calls the result a sequence.
Nurturi keeps a smaller rule in the product, so a busy afternoon cannot raise it.
The cap
| Rule | Limit |
|---|---|
| Connection requests, per person, per day. New business and existing clients share it. | 25 |
| A pending request is withdrawn after | 21 days |
| Silence before another machine may take the queue | 2 hours |
25 is a ceiling. It is not a target. You split it across the two books. You do not get a second allowance for the other one.
The day's list is approved before anything goes out. If today's batch was not approved, nothing sends.
The request goes out blank. No note. A generic note is the thing we will not send. Blank stays the default.
One queue, however many machines
The queue lives on the server. The browser extension or the desktop app clicks the next approved name and reports what the button actually did. It does not choose who is next. A second laptop does not get its own allowance. Whichever install sent last keeps the work. Another takes over only after the silence in the table.
A request still pending when that withdrawal date arrives is withdrawn. A pile of unanswered invites clogs the account.
One first message, after you have read it
When someone accepts, Nurturi prepares one first message. Their first name, from that campaign's template. It does not go anywhere until you have read the wording. You can edit it, send it, or stop it. A campaign with no wording prepares nothing.
After that first message the thread is a conversation. Nurturi will draft the next one. You send it. That line is the whole of the person sends it.
25 is a number you can still read. If the list is too long to look at, it is too long to send. The account side of the same idea is in an account book is not a list of companies.