Check a message before it goes out.
Paste a connection note, first message or follow-up. The checker flags missing fallbacks, links, hype, bump lines and extra questions.
{first_name}, with a fallback after a bar: {first_name|there}.
Runs in your browser. Nothing you type here is stored or sent anywhere.
Spammy templates get accounts reported, and a reported account is the sender’s problem, not just the message’s. This checker runs a short list of rules on a template before you send it, and says what it found and why it matters.
Choose what the message is, a connection note, a first message or a follow-up, because the rules differ. A note should stay under 200 characters. A first message should be one line of context and one question, and under 600 characters. A follow-up should give one new reason to reply, or offer to stop.
The checker looks for seven things. A variable with no fallback, which would print as raw text for a lead missing that field. A link in a note or first message, which reads as a pitch. Hype words such as “guaranteed”. Bump phrases such as “just circling back”, which say nothing new. More than two questions. Several exclamation marks. A first message with no question at all.
The count at the top is the number of things to fix. Zero means the template passes these rules, nothing more. It can’t tell you whether the message is relevant to the person who gets it, and it can’t predict replies.
The rules are ours. They describe messages people don’t mind receiving, and they match what the app enforces: every variable in a message needs a fallback before launch.
How to use it
Say what the message is
Choose connection note, first message or follow-up. The rules and limits change with the choice.
Paste your template
Replace the example text with your own. Use single braces for variables, and a bar for the fallback, as in {first_name|there}.
Fix what it flags
Each finding says what it saw and why it matters. Edit the message until the count of things to fix is zero, then read it aloud once.
More free tools
All tools →LinkedIn connection request character limit counter
The LinkedIn connection request character limit is 200 characters per LinkedIn’s current help page. Paste a note and see its length as it would be sen
Use the tool →Daily limit planner
Enter your accounts, daily requests and leads. See how many connection requests go out each week and how many weeks the list takes.
Use the tool →What does the checker count as a problem?
Missing fallbacks, links in a note or first message, hype words, bump phrases, more than two questions, several exclamation marks, a first message with no question, and messages over the length for their kind.
Does a clean result mean I will get a reply?
No. It checks a message against our rules for short, specific, polite templates. It can’t predict replies, and we don’t promise any.
Are these LinkedIn’s rules?
No. They are our own, written for messages people don’t mind receiving. LinkedIn doesn’t publish rules for message wording.