Start with a conversation you could actually have
An operations contact has accepted a no-note invitation. A public company announcement describes a second office. The IT provider, contract and support arrangements are unknown. The sender is a fictional IT services firm that genuinely covers both locations.
Fictional training examples. People, circumstances and outcomes are invented. These are not client messages or evidence of campaign results.
First substantive DM · after acceptance
Hi [first name], With the second office opening in [area], are you the person who coordinates IT support across both sites? We help teams in that area cover the day-to-day support between offices. I’m asking so I don’t send the wrong person a longer explanation.
Possible reply · not a scheduled step
I coordinate it. We already have a provider—what would you handle?
Answer the question first
Thanks. Our work is the everyday support coverage between the two offices, alongside an existing provider where that division is useful. If your current arrangement already covers that, there may be nothing to change. Is there a part of the two-site coverage you are reviewing?
The sender must replace that explanation with its real scope. A website announcement does not establish dissatisfaction with the current provider. The answer leaves room for the prospect to say that everything is covered.
Alternative later reply · only if the person asks
That is worth discussing. Can you send your calendar?
Requested handoff
Of course—here is our calendar: [approved client calendar link]. I’ll pass on the question about two-site coverage so the person taking the call has the context.
- The first DM has one primary question, supported by an honest explanation of the sender’s work.
- A human reply stops a programmed no-reply reminder. The next message answers what was actually asked.
- A requested calendar link is a handoff. Only a separate calendar record or authorized client confirmation establishes a booking.
If there is no reply instead, review the context and send at most the brief reminder in the timing example when appropriate. Do not schedule the scope answer or calendar handoff as if the prospect had already responded.
Choose the relationship before the wording
Check the actual relationship, available controls and any existing conversation. A public profile is not evidence of frequent inbox use. Relevant recent activity may support LinkedIn as the first channel; a suitable business email may be more appropriate when that activity is absent.
Scroll the table horizontally to read every column.
| Situation | Path to consider | What it does not establish |
|---|---|---|
| A real reason to connect; no current conversation | A connection invitation, with a relevant note if appropriate and available. | Acceptance, interest or permission for a long pitch sequence. |
| Already connected; no reply or refusal to respect | A normal DM with a specific reason and one easy question. | That the person owns the problem or wants a meeting. |
| Not connected; an appropriate InMail option is available | Evaluate the actual product, credits and composer. Use a truthful subject. | That every non-connection can be reached through the same route. |
| Invitation pending | Check the thread and controls. Do not assume a normal DM is available. | That another invitation or sender should be used to force contact. |
| A response arrives before acceptance | Review the actual available conversation and update the state. | That the invitation state alone describes the conversation. |
| No suitable route, or a refusal/stop request | Hold the affected workflow or stop as requested. | A reason to evade a preference through email, calling or another account. |
Before writing, check what the recipient will see: a recognizable sender, a current role and a plain explanation consistent with the offer. When working on a client’s behalf, use the authorized sender identity and scope. Do not pretend to be an independent peer or invent an introduction.
Scroll the table horizontally to read every column.
| Feature | What the primary guidance establishes | Practical check |
|---|---|---|
| Personalized connection note | The fetched LinkedIn invitation help lists up to 200 characters and three personalized invitations per month for Basic members. | Check the allowance and counter shown in the current account. |
| Premium personalization | The help distinguishes unlimited personalized notes from separate limits on invitations themselves. | Premium is not permission for unlimited invitations or unwanted contact. |
| Sales Navigator InMail | The available route, credits and current composer depend on the actual product/account. | Do not copy a Recruiter body limit into Sales Navigator. Check its own current composer. |
| Invitation activity | LinkedIn applies restrictions to Basic and Premium and considers ignored, pending and spam-marked invitations. | There is no universal safe daily quota in the linked guidance. A tool’s pacing settings do not guarantee approval or account safety. |
The private review below counts Unicode code points, not reading quality. A visible note warning uses the documented 200-character guidance; LinkedIn’s own composer remains the final check, especially for emoji and combined characters. InMail has no invented hard cap in this review.
Two more complete paths, with different reasons to write
A genuine shared event: invitation, then a distinct DM
In this fictional situation, both people attended the same public session. The sender genuinely works on the topic. They have not spoken privately, so the note must not say that they met.
Fictional training examples. People, circumstances and outcomes are invented. These are not client messages or evidence of campaign results.
Invitation note
Hi [name], we both attended [session]. Your question about practical manager training stayed with me. I work on that too and would be glad to connect.
After acceptance
Thanks for connecting, [name]. At [session], your question was about helping new managers practise difficult conversations. We run workshops around those situations. Is that something your team is currently looking at, or was it a more general question?
Possible reply
A general question for now. We are not looking for a provider.
Respect the actual answer
Understood—thanks for clarifying. I’ll leave it there.
The note and DM have different jobs. An accepted request does not justify every later message. The last reply closes this commercial sequence; it is not a reason to start an email pitch.
An InMail to a non-connection: a truthful subject and a small request
A fictional design studio has checked a public product release and the relevant product owner. An appropriate InMail route is available. Whether the release created a new user journey remains unknown.
InMail · subject: the new reporting role
Hi [first name], Does the reporting module in [release] introduce a new user role, or is it mainly for the existing dashboard users? We work with product teams on those first-use journeys. That distinction would tell me whether an example of our approach is relevant to share.
Possible reply
It is a new role. Do you have an example?
Fulfil the request
Yes—[example link] shows how we map one role’s first-use journey, with the assumptions marked. The example is illustrative, not a result from your product. If useful, which part of that new role’s journey are you reviewing?
If a permitted DM or InMail remains unanswered, review the timing example before considering one brief reminder. A pending invitation is not a sent DM. A refusal, unavailable route or human reply changes that decision; a resource request calls for the resource, not a scheduled pitch.
Only offer a resource you can actually provide. Use a real, approved example in a live campaign; the placeholder here is a teaching device. Do not label a subject as a reply, introduction or prior conversation unless that is true.
Keep the structure; change the reason for each person
These four examples assume an available normal DM between existing connections. Recheck that route and the actual thread before adapting a message.
These four situations retain the industry examples from the earlier guide. Each now has one primary ask and its own reasoning. The repeated structure helps the writer; the substantive context still changes for each person.
Fictional training examples. People, circumstances and outcomes are invented. These are not client messages or evidence of campaign results.
An IT provider and an operations owner
A public post describes the work of coordinating two sites.
The provider, contract dates and support needs are unassessed.
First substantive message
Hi [first name], For the two sites you mentioned, does IT support sit with you? We provide everyday support across offices in [service region]. I wanted to check the owner before sending a longer explanation.
The geographical service fit is checked before writing; the role question leaves room for correction.
If unanswered and still appropriate: “Hi [first name], just checking whether the question above is relevant to you.” This is not the response to a refusal or a question.
A specialist recruiter and an engineering owner
The person has publicly discussed specialist engineering vacancies.
A vacancy does not establish a hiring failure, outside-agency budget or permission to send candidate details.
First substantive message
Hi [first name], For the [specialism] roles you discussed this week, is your internal team running the whole search? We recruit in that area. I would first want to understand the experience you need rather than send unrelated profiles.
The question concerns the actual hiring process. It does not turn an open role into an assumed need for an agency.
If unanswered and still appropriate: “Hi [first name], just checking whether the question above is relevant to you.” This is not the response to a refusal or a question.
A training provider and a multi-site operator
A public comment raises supervisor onboarding at a new site.
The current training plan, procurement timing and requirements are unknown.
First substantive message
Hello [first name], Is induction for the new supervisors at [site project] already covered by the team? We run practical manager workshops around real team situations. The question is whether that is useful here, rather than adding another programme you do not need.
The offer is concrete without promising productivity, compliance or a training outcome.
If unanswered and still appropriate: “Hi [first name], just checking whether the question above is relevant to you.” This is not the response to a refusal or a question.
A design studio and a product owner
The product owner has shared a reporting-module release.
A release does not establish low activation, usability problems or a redesign budget.
First substantive message
Hi [first name], With [reporting module], is the first report mainly for new users or people already using the dashboard? We work on those first-use journeys. That would help me judge whether a specific example is relevant.
The message names one decision about one journey, without claiming to have found a private product problem.
If unanswered and still appropriate: “Hi [first name], just checking whether the question above is relevant to you.” This is not the response to a refusal or a question.
The reason does not have to be company news
A reason to write may come from a public personal post, a genuine shared interest, a location or an event. It should be professionally appropriate and something you can explain without making the person feel watched. Common ground can start a conversation without proving any buying need.
A shared location, only when it is true
Fictional training examples. People, circumstances and outcomes are invented. These are not client messages or evidence of campaign results.
Fictional connection note
Hi [name], I’m based in [city] as well. Your post about making local professional events more welcoming raised a good point. I’d be glad to connect.
Being in the same city is a genuine connection in this scenario. It does not establish a local office, friendship or need for the sender’s services. Do not use a neighbourhood detail simply to demonstrate how much you found.
A public interest, without forcing a sales angle
Fictional DM · already connected
Your point about keeping beginners involved in [public community activity] made me rethink how we introduce people at our own events. Which part of the format has made the biggest difference for you?
This question is appropriate only if the sender genuinely cares about that answer and the stated experience is true. It can remain a conversation. Do not manufacture a hobby, pretend that a casual exchange is a sales qualification or pivot immediately to a calendar link.
Keep the trust behind an introduction or offer
A shared connection is not an endorsement
A visible shared contact may never have spoken to the prospect. Before using a name as an introduction, ask about the actual relationship and obtain permission. If the person only identifies the right role, describe that accurately.
Fictional request to a genuine contact
Do you know [person] well enough to introduce us? I would like to ask about [specific topic] because we work on [relevant area]. If you are comfortable, I can send two lines you could forward. No problem if you do not know them well.
Only after a real, permitted introduction
Hi [first name], [mutual contact] introduced us about [topic]. We help [relevant type of team] with [specific work]. Is that an area you are reviewing, or have I misunderstood the timing?
If someone asks for the resource, send the resource
Fictional reply to “Send the checklist”
Here is the [specific checklist] I mentioned: [approved resource link]. The section on [specific part] relates to your question. Happy to clarify anything there.
Do not substitute a demo request, a gated form or a general sales deck for the promised item. No further question is compulsory. If the sender does not have a genuine, approved resource, the original offer should change.
Six replies and the decisions they change
The assigned conversation owner records each incoming reply and cancels the pending no-reply reminder. The client confirms unapproved scope and verifies calendar outcomes. The examples do not establish budget, a contract or a booking unless a separate record says so.
A reply changes the job. Stop a pending no-reply sequence and respond to what the person actually said. These branches are alternatives, not six messages to schedule for everyone.
Fictional training examples. People, circumstances and outcomes are invented. These are not client messages or evidence of campaign results.
They ask what you handle
Possible incoming reply
We already have someone doing this. What would your part be?
Response to adapt
We would cover everyday support across the two offices and agree which issues still go to your existing provider. If that coverage already works well, there may be nothing to replace. Is there a part of the site coverage you are currently reviewing?
Pause the programmed reminder. Confirm the scope with the responsible client if it is outside the approved explanation.
They request details or a resource
Possible incoming reply
Can you send the details here?
Response to adapt
Of course. The workshop lets new supervisors practise a difficult management conversation using a situation from their work, with feedback on the approach. It would complement their induction rather than replace the whole programme.
Deliver what was requested. Do not treat the request as permission to send a calendar link instead.
They identify another owner
Possible incoming reply
Another team handles that.
Response to adapt
Thanks for pointing me in the right direction. Is there a role I should look for, or would you prefer I leave it there?
Check the new person’s fit separately. A role correction does not establish their interest or an introduction.
They give a later date
Possible incoming reply
Please come back in the second week of November.
Response to adapt
Understood—I’ll hold this until the second week of November. Thanks for giving me the timing.
Record the requested window and owner. Hold intervening pitches; check the actual thread before the later review.
They decline
Possible incoming reply
Not relevant for us. Please stop contacting me.
Response to adapt
Understood. I’ll stop the outreach.
Apply the stated preference across the relevant workflow. No reminder, new sender or channel switch.
They ask for a calendar
Possible incoming reply
Can you send a link so we can talk?
Response to adapt
Here is [approved client calendar link]. I’ll pass on your question about covering both sites alongside the current provider to the person taking the call.
Record the handoff. Verify a booking separately; do not mark it booked because the link was sent.
Use the actual send and the actual answer
Beespoke typically uses one substantive individual opening and one brief reminder, often about four days later. That is the founder’s described practice, not a universal optimum. A connection invitation and a post-acceptance DM have different starting points.
Scroll the table horizontally to read every column.
| Event | Record | Decision |
|---|---|---|
| Monday October 26, 2026: invitation accepted | No substantive DM has been sent yet. | Review the actual conversation and prepare the appropriate first DM. Acceptance is not a booked meeting. |
| Tuesday October 27, 10:00: first DM sent | America/New_York; agreed working window Monday–Friday, 09:00–17:00. | Four elapsed days points to Saturday October 31. That falls outside the agreed window. |
| Friday October 30: a scope question arrives | A human reply is now present. | Cancel the no-reply reminder and answer the question. Do not wait for Monday to send a programmed pitch. |
| Alternative: still no reply by the next permitted window | Recheck fit, replies and preferences across authorized channels. | Only if still appropriate, review a short reminder for Monday November 2. No automatic send is implied. |
A considered no-reply reminder
Hi [first name], just checking whether the question above is relevant to you.
An absent read indicator is not proof of avoidance. A visible view is not consent to more contact. If the contact is no longer appropriate, stop rather than trying to repair the situation with a longer pitch. The follow-up guide covers more timing and absence situations.
One conversation owner, with a real calendar handoff
Beespoke researches the account and people, proposes the target list and writes individual messages. The client’s judgment approves suitable people and exclusions. Authorized campaign work includes the agreed messaging and reply handling; the client handles the sales conversation, proposals and closing. Calling is a separate, market-dependent quote.
Scroll the table horizontally to read every column.
| Current evidence | Owner | Next permitted action |
|---|---|---|
| An email reminder is planned; a LinkedIn scope question arrives. | The assigned conversation owner. | Hold the email, record the question and answer in the active conversation. |
| A person asks for a calendar link. | The owner coordinating with the client’s sales contact. | Send the client’s existing approved booking link and pass on the real context. |
| A calendar link was sent but no record has been checked. | The owner with authorized CRM/calendar access, or the client confirming the booking. | Keep the booking status unknown. Do not count a click or a link send as a meeting. |
| A booking record is verified, then moved to another time. | The calendar/CRM owner. | Keep the original booking identity and record the reschedule; do not count a second new booking. |
| Record field | Recorded value |
|---|---|
| Approved person and segment | Training contact P-01; operations owner at a two-office business; fit and exclusions approved for this exercise. |
| Active thread and date | LinkedIn DM, October 30, 2026 at 14:00 America/New_York. A question about support scope has arrived. |
| One responsible owner | Assigned campaign owner A reviews both authorized channels; the client confirms any scope outside the approved explanation. |
| Held step and next action | Hold the email reminder planned for November 2. Answer the scope question in the active LinkedIn conversation after review. Record the reply before any other step. |
| Stage | Evidence and status |
|---|---|
| Calendar requested | October 30: the person asks for the client’s calendar in the active conversation. No booking yet. |
| Link sent | October 30: the owner sends the approved client link. The send is a handoff, not a booking. |
| Booking verified | October 30: an authorized calendar record confirms original booking B-01 for November 3. One original booking counted. |
| Rescheduled | October 31: the same B-01 is moved to November 4. Still one original booking. |
| Held | Not yet checked. The planned appointment time does not prove attendance. |
| Qualified | Not yet assessed by the client. Attendance alone would not establish qualification. |
The evidence chain is: interest expressed → calendar requested → link sent → booking verified → held → qualified. Each step needs its own evidence. A meeting can be booked and not held, or held and not qualified. No message template establishes any of those outcomes by itself.
Keep the denominators beside the rates
This fictional cohort illustrates the arithmetic. It is not a Beespoke result, benchmark, target or prediction. Use comparable segments and give both variants the same time to accept, reply and book.
Fictional training examples. People, circumstances and outcomes are invented. These are not client messages or evidence of campaign results.
Scroll the table horizontally to read every column.
| Stage | Raw count | Rate and denominator |
|---|---|---|
| Approved contacts | 100 | The original contact cohort. |
| Invitations sent | 80 | 80 of 100 approved contacts. |
| Invitations accepted | 32 | 32 ÷ 80 = 40% acceptance. |
| People substantively messaged | 30 | The denominator for the message reply rates. |
| People giving a human reply | 6 | 6 ÷ 30 = 20%; this includes replies that are not useful interest. |
| People giving a relevant reply | 4 | 4 ÷ 30 ≈ 13.3%; define relevance before reviewing results. |
| Verified original bookings | 2 | 2 ÷ 100 = 2% of the approved cohort; 2 ÷ 30 ≈ 6.7% of people messaged. |
| Held and qualified | Not assessed | Unknown is not zero. Do not fill it from a calendar-link click. |
- Low acceptance: inspect fit, recognizable sender context and the invitation—not just a different opener.
- Accepted but no reply: check the actual message path, specific reason and size of the ask.
- Replies without relevant interest: inspect targeting and what the question invites people to discuss.
- Interest without verified meetings: inspect the requested handoff, client ownership and actual calendar records.
Count distinct people and original bookings, not total messages, reactions or reschedules. Vendor reply rates from another audience do not forecast your campaign. These prospecting metrics are also separate from website-acquired meetings: testing visits, a worksheet action and a booking-page view are not genuine website leads.
Edit the whole message, not a list of forbidden words
AI-assisted and human-written drafts need the same review: supported facts, individual relevance, a truthful commercial purpose and a proportionate ask. A natural message may mention a post the sender actually read. The problem is empty framing or invented familiarity, not proof that a particular word came from AI.
Generic praise becomes a specific question
Before · fictional editing exercise
Hi [name], I read your comment on [public topic] and was impressed by your remarkable journey. We leverage innovative solutions to unlock growth. I would love to connect, send our deck and arrange a call.
After · same commercial purpose, clearer reason
Your comment on [public topic] raised a question about [specific part]. Is that something you handle at [company]? We work on that area. I wanted to check the owner before sending a longer explanation.
The revision removes unsupported praise and competing asks. It keeps the sender’s actual work and one reason to reply. Only use the public-topic reference after checking what was really said.
A long no-reply pitch becomes a short reminder
Before · only appropriate to assess as a draft
I know you are incredibly busy, but I wanted to follow up again on our transformative solution and all the ways it could help your team. Have you seen my message, looked at our deck or found a time for a call?
After · if unanswered and still appropriate
Hi [first name], just checking whether the question above is relevant to you.
The reminder depends on a useful original. If the original was unsupported or badly targeted, a shorter follow-up does not fix it. A real reply needs an actual answer rather than this reminder.
| Pattern | Question to ask |
|---|---|
| “I saw that…” or “I noticed…” | Is the observation real and worth stating, or is this an empty wrapper? |
| “Impressive journey” or generic admiration | What specific, honest point does the praise add? |
| “Unlock”, “synergy” or “game changer” | What concrete work or effect is meant? Do not swap synonyms mechanically. |
| “No pitch” or “no agenda” | Does that truthfully describe the purpose? Do not disguise a sales approach. |
Use the optional private review to check your own draft. Its phrase matches are editorial prompts, not an authorship detector or a prediction of replies.
Review one message and its next decision
Choose the actual route, record the checked reason and review the current reply state. The workspace helps you organize your judgment; it neither sends messages nor verifies the facts you enter.
Open the private review
Use nonconfidential notes. Nothing is uploaded or saved; reload clears this review. Export what you need before leaving.
Without JavaScript, use the fields and complete examples manually. Interactive actions remain unavailable.
Length check
Counts use Unicode code points. Emoji and combined characters may be counted differently by the product. No quality score is calculated.
Wording to review in context
A match is a prompt to read the whole sentence, not evidence that AI wrote it.
Subject, unknowns and ownership
Clear only this review? Export anything you need first.
Choose a fictional situation
Fictional training situation. No real client or prospect is represented.
Your LinkedIn message review
These are your notes and judgments, not verified findings. No message is sent and no score is calculated.
Decision to review
Your draft preview
Your manual checks
When you want the work managed
Beespoke can research suitable people, prepare individual messaging and run the authorized cold-email and/or LinkedIn work against agreed criteria. The client approves suitable people and exclusions and handles the sales conversation and closing. There is no promised meeting volume; calling is separately scoped.
Continue with the next question: follow-up timing and replies · individual cold-email writing.
Questions about LinkedIn prospecting messages
Should we use one LinkedIn template for everyone?
Use a structure, not identical relevance. Check the person, role and available route, then rewrite the substantive reason for that recipient. A name and company substitution is not enough.
Does an accepted connection count as a lead?
It is a connection state, not evidence of buying interest, qualification or a booking. Record the actual conversation and verified outcomes separately.
What if the person is inactive on LinkedIn?
Review whether an appropriate business email or another authorized route is more suitable. A profile existing does not establish that the person reads LinkedIn messages regularly.
Are these real client messages?
No. The worked conversations and tool samples are fictional training material. They illustrate the founder-described research and writing approach without publishing client, sender or prospect identities or claiming results.
How long should a LinkedIn message be?
Use the space needed for a clear, relevant point and one primary ask. Invitation notes have different constraints from DMs and InMail. The linked help lists 200 characters for personalized notes; check the current product and composer rather than copying a limit from another product.
How many follow-ups should we send?
There is no universal optimum. Beespoke typically uses an individual substantive opening and one brief reminder, often about four days later, subject to the actual context. A reply, decline, timing request or unavailable route changes the decision.
When can we count a meeting as booked?
After an authorized calendar/CRM record or client confirmation verifies the booking. A link send, accepted request, reaction or page view does not prove it. Keep original bookings, reschedules, held meetings and qualified meetings separate.
What the guidance is based on
The campaign approach is supplied by Beespoke’s founder. Worked situations, messages and numbers on this page are fictional training material. They do not report a client’s outcomes or claim that any template has been tested to produce a reply rate.
- LinkedIn Help: personalized invitations — note guidance and the distinction between Basic and Premium personalization allowances.
- LinkedIn Help: invitation restrictions — restrictions, pending invitations and member-experience guidance.
- LinkedIn Sales: InMail scenarios — message context, one clear ask and permission behind mutual-contact references.
Primary pages were read October 30, 2026. Platform guidance and account controls can change. Limits are product-specific; this guide does not transfer a Recruiter allowance to Sales Navigator or promise that software avoids restrictions. Vendor template and outcome claims are not our results.