What Crispy limits when you automate LinkedIn

LinkedIn's User Agreement section 8.2 prohibits bots and other unauthorized automated methods. You can read it at https://www.linkedin.com/legal/user-agreement. Crispy's caps do not change that rule.

Crispy's default invitation cap is 15 per day. Crispy rejects an invitation cap above 50 per day. The default message cap is 150 per day. The default profile-view cap is 250 per day. The default search cap is 300 per day. The default engagement cap is 100 per day. The default post cap is 10 per day. The detail is on the LinkedIn safety page and in how many connection requests Crispy caps.

You can set a lower cap. For messages, profile views, searches, engagement, and posts, Crispy does not enforce a maximum cap. Crispy blocks the action when the cap in force is reached. It does not save the action for later.

Warm-up is optional. Crispy does not start it when you connect an account. It runs when you enable it. The auto preset ramps for 14 days and only lowers the cap. The steps are in how warm-up works.

Crispy does not require a Chrome extension. That fact does not make the activity authorized, and it does not make the activity undetectable.

If LinkedIn restricts the account, pause sending and follow the steps LinkedIn shows you. This post does not state how long a restriction lasts. See what to do if the account is restricted.

The caps and the warm-up reduce how much Crispy sends. They do not authorize the activity. They do not guarantee LinkedIn will not restrict the account. The same point is in is Crispy safe for my LinkedIn account.