These 93 templates are fictional, adaptable examples, not records of campaigns we ran, customer stories or measured reply rates. They cover cold connection requests and later outreach stages, including invited supplier responses, recruiting, agency partnerships and active buying conversations. Choose a message for the actual stage; do not send the examples in order.
Categories 1–5 cover connection requests, outreach based on public context and related follow-up. Category 7 covers recruiter outreach and search follow-up. Category 6 covers relevant outreach and invited replies involving identified visitors; categories 8 and 9 cover partnership approaches and active commercial conversations. Category 10 is re-engagement based on a relevant request or development. Check each example’s stated situation: a later-stage message should not be used as a cold opener. The 93 examples retain their reference numbers, so some numbers are skipped.
Before using a message, check the person's current responsibility, the actual source or conversation, existing account ownership and any refusal. Replace placeholders with verified facts and preserve your real identity and affiliation. A shared group, profile view, new job or funding announcement does not establish buying intent. If no useful reason to contact the person exists, choosing no message is a valid result.
For any example mentioning a mutual contact, customer, public result, event attendance, ticket, data finding, private group or available resource, use it only when that exact statement is true and sharing is authorised. A placeholder is not permission to invent proof. Follow-up dates must come from actual context; silence is not permission to continue.
For a paid offer, begin with the buyer's task and explain what you can actually deliver. Do not conceal commercial intent by calling a sales approach research or an agenda-free chat. These examples make no promise of a reply, meeting, purchase or account outcome.
Category 1: Cold connection requests (10 templates)
Template 1.1: The "I noticed" pattern
Hi {firstName}, noticed you lead {function} at {company}. Curious what you're using for {tool category} these days. Open to connect?
Template 1.2: The "asking for advice" frame
Hi {firstName}, building a tool for {role} like yourself. Would love your perspective on what's broken in {workflow} today. No pitch, just curious.
Template 1.3: The shared connection
Hi {firstName}, we're both connected to {mutualName}. She speaks highly of your work on {project}. Would be great to be in your network.
Template 1.4: The conference / industry hook
Hi {firstName}, saw you spoke at {event} last month on {topic}. Brilliant point about {specific takeaway}. Would love to connect.
Template 1.5: The "challenger" frame
Hi {firstName}, I disagree with your take on {topic} from your last post. Would love to connect and discuss.
Template 1.6: The "I'm new here"
Hi {firstName}, just moved into {new role / new market}. Building my network in {industry}. Your work caught my eye. Would love to connect.
Template 1.7: The compliment + curiosity
Hi {firstName}, your post about {topic} was the best thing I read this week. How did you arrive at that framework?
Template 1.8: The local angle
Hi {firstName}, fellow {city}-based {role} here. Always like to connect with locals doing interesting work. Open to a virtual coffee?
Template 1.9: The "we serve similar companies"
Hi {firstName}, we work with several {companyType} companies similar to {company}. Would love to learn how you approach {challenge}.
Template 1.10: The "alumni network"
Hi {firstName}, fellow {school} alum here. Saw your work at {company} and wanted to connect.
Category 2: Outreach after a public comment (10 templates)
Template 2.1: The direct commenter reference
Hi {firstName}, saw your comment on {Author}'s post about {topic}. You said {paraphrase their comment}. Curious how you're approaching that at {company}.
Template 2.2: The "we agree"
Hi {firstName}, your point on {Author}'s post about {topic} was spot on. We've been seeing the same thing with our {customers / users}. Would love to compare notes.
Template 2.3: The follow-up question
Hi {firstName}, your comment on {Author}'s post got me thinking. You mentioned {specific point}. How do you actually measure that?
Template 2.4: The "I built that"
Hi {firstName}, your comment on {Author}'s post described exactly the problem we built {Product} to solve. Would love to show you the 60-second version.
Template 2.5: The "data follow-up"
Hi {firstName}, your comment on {Author}'s post about {topic} aligns with what we're seeing in our data. We just compiled {finding} across {sample size} users. Want a copy?
Template 2.6: The disagreement
Hi {firstName}, respectfully disagree with your take on {Author}'s post. Here's why: {1-sentence counter}. I'd be interested in how you reached that conclusion.
Template 2.7: The peer connector
Hi {firstName}, your comment on {Author}'s post was great. Two of our customers ({CompanyA}, {CompanyB}) tackle {topic} the same way. Happy to intro if useful.
Template 2.8: The compliment + ask
Hi {firstName}, your reply to {Author}'s post was the most thoughtful in the thread. Where do you publish your own writing?
Template 2.9: The "we're in your tribe"
Hi {firstName}, fellow {Author}-fan here. Saw your comment on the {topic} post. We're building tools for the same audience. Would love to connect.
Template 2.10: The pure curiosity
Hi {firstName}, your comment on {Author}'s post about {topic} surprised me. Genuinely curious: what made you frame it that way?
Category 3: Event-related outreach (10 templates)
Template 3.1: The pre-event
Hi {firstName}, saw you registered for {event}. Will be there too. Always like to connect with attendees beforehand. What are you hoping to take away?
Template 3.2: The post-event
Hi {firstName}, saw you attended {event} last week. Best session for me was {speaker / topic}. Yours?
Template 3.3: The session reference
Hi {firstName}, you attended {session} at {event}. Would love your take: did the speaker's framework work for you in practice?
Template 3.4: The "we sponsored that"
Hi {firstName}, you attended {event}, which we sponsored. Hope you grabbed {item}. If you want to chat about how we approach {topic}, I'm here.
Template 3.5: The future event
Hi {firstName}, you went to {past event}. Heads up: {upcoming similar event} is happening. We've got a few extra free tickets if you want one.
Template 3.6: The speaker connection
Hi {firstName}, saw you attended {event} where {speaker} spoke. We work closely with her at {Company}. Happy to make an intro if useful.
Template 3.7: The follow-up ask
Hi {firstName}, post-{event} I'm reaching out to attendees in {industry}. Building a mini-survey on {topic}. Would you take 90 seconds to share your perspective?
Template 3.8: The peer roundtable
Hi {firstName}, fellow {event} attendee. We're hosting a small roundtable next month with 6 other attendees on {topic}. Want in?
Template 3.9: The video recap
Hi {firstName}, you attended {event}. We recorded a 5-min video recap of the best 3 takeaways. Want me to send it?
Template 3.10: The connection
Hi {firstName}, also at {event}. Would love to keep in touch and trade notes on {topic} as we both navigate it.
Category 4: Group member outreach (10 templates)
Group membership alone is not a reason to pitch. Use the actual thread and the stated request. A group rule, existing conversation or refusal can prevent an approach.
Template 4.1
Hi {firstName}, fellow {group} member. Your recent post in the group about {topic} stood out. Would love to connect.
Template 4.2
Hi {firstName}, saw your question in {group} about {topic}. Have a tactical answer if helpful, but also wanted to connect.
Template 4.3
Hi {firstName}, group member here. Curious what brought you to {group} originally?
Template 4.4
Hi {firstName}, in {group} I noticed you focus on {sub-topic}. We're working on the same thing. Want to compare approaches?
Template 4.5
Hi {firstName}, both in {group}. I'm building a private channel for the most active 20 members. Would you want in?
Template 4.6: Answer a request for a supplier-comparison brief
Fictional situation: A member asks how to compare agencies for an existing website project. You have a short comparison sheet you can actually share.
Hi {firstName}, in {group} you asked how to compare the website proposals. I have a one-page sheet for checking deliverables, client inputs and ownership after launch. Would it help if I shared it in the thread, so the other members can use it too?
Check before use: The sheet exists, sharing is permitted and the member has not asked suppliers to stay out of the discussion. This offers a specific answer in their chosen forum.
Template 4.7: Clarify a requirement that your service may not meet
Fictional situation: A member's request specifies an on-site workshop, while your service is delivered remotely. Check the decisive constraint before sending a proposal.
Hi {firstName}, your request in {group} says the workshop needs to be on site. Is that essential, or would a remote session with your local facilitator be workable? Our delivery is remote, so I would rather check that first than send you an unsuitable proposal.
Check before use: Remote delivery is your actual constraint. This is a fit question, not an attempt to disguise a mismatch.
Template 4.8: Supply the worked example someone asked to see
Fictional situation: In a discussion about project handovers, a member asks what a completed handover record looks like. You have an anonymised or explicitly fictional example cleared for sharing.
Hi {firstName}, you asked for a completed handover example in {group}. I can share a fictional record showing the final deliverable, open decisions and next owner. It contains no client information. Would you prefer a short reply in the thread or the document link here?
Check before use: The example is safe to share and is labelled accurately. It demonstrates a format without pretending to be customer proof.
Template 4.9: Volunteer for a defined peer review
Fictional situation: A group member invites people to review one specific section of a public draft. You can review that section within the requested boundary.
Hi {firstName}, I saw your invitation in {group} to review the supplier-onboarding section. I can check whether the steps and responsibilities are clear to a first-time reader. Is that the feedback you need, or are you looking specifically for a legal review?
Check before use: You can offer the stated review; do not imply legal expertise you lack. This establishes the requested kind of help before doing it.
Template 4.10: Respond to an organiser's speaker request
Fictional situation: A group organiser requests a practitioner for a session on a task you actually perform. Offer a bounded outline rather than a generic sales presentation.
Hi {firstName}, your post in {group} asks for a speaker on {task}. That is part of my work at {company}. I could propose a session built around one fictional example and the decisions it raises. Would you like a short outline to assess against the programme?
Check before use: Your role and experience support the subject, and the organiser invited proposals. Do not claim a speaking credential or customer result you cannot substantiate.
Category 5: Outreach after a job or company change (10 templates)
A public change gives context for a question. It does not establish a budget, a problem or a buying window. Use the source's actual wording and date; verify the person's current responsibility.
Template 5.1: The new job
Hi {firstName}, congrats on the new role at {company}. We help new {role}s ramp on {workflow} fast. Open to a 15-min call?
Template 5.2: The promotion
Hi {firstName}, congrats on the promotion to {new title}. We work with several {peer companies}. Want a 10-min call?
Template 5.3: The funding
Hi {firstName}, congrats on {company}'s {funding round}. We help with {specific outcome}. Worth a chat?
Template 5.4: Ask who owns a process after an acquisition
Fictional situation: A company has announced an acquisition. Your service concerns a process that might remain separate or be combined; neither outcome is known.
Hi {firstName}, I read {company}'s announcement about {acquisition}. Do the two teams expect to keep their supplier-onboarding processes separate? I work on that process at {yourCompany}, and wanted to understand the ownership before suggesting anything relevant.
Check before use: The acquisition announcement is real and the role is relevant. Avoid assuming that systems are broken or that integration work has been commissioned.
Template 5.5: Check responsibility for a new market's support content
Fictional situation: A company announces entry into a market where language and support-content ownership may matter to your service.
Hi {firstName}, {company} has announced its launch in {market}. Who is responsible for deciding which support material needs local adaptation? That is the part of launch work we handle at {yourCompany}; I would be interested to know whether it is already covered internally.
Check before use: You can support the language and task you name. A new market does not itself prove that translation or an outside supplier is needed.
Template 5.6: Separate a product launch from its partner rollout
Fictional situation: The public product launch is complete. Your work concerns material used by channel partners, which may follow a different timetable.
Hi {firstName}, I saw the launch of {product}. Is partner enablement part of this release, or will that come later? At {yourCompany} I work on turning product information into material partners can use. If that work is already handled, I will leave it there.
Check before use: Partners are genuinely relevant to the product. Do not invent a missing launch asset or imply that a launch automatically creates a sales opportunity.
Template 5.7: Find the owner of an announced office move
Fictional situation: A business announces a specific move. Your service covers one practical part of relocation, such as transferring reception arrangements.
Hi {firstName}, the announcement says {company} is moving to {location}. Who is coordinating the reception handover for that site? I work on {specificRelocationTask} at {yourCompany}. I would like to check whether that part is already assigned before sending an outline.
Check before use: Use an announced business move, not inferred personal-location data. Name only the relocation work you actually deliver.
Template 5.8: Test whether hiring reflects a process need
Fictional situation: Several current vacancies relate to one function. Your service might help its process, but hiring could be sufficient on its own.
Hi {firstName}, {company}'s current vacancies include several {function} roles. Is the immediate priority simply adding capacity, or is the team also changing how {specificProcess} works? We support that process, so the distinction would help me judge whether an introduction is useful.
Check before use: Verify the live roles and avoid treating vacancy counts as evidence of pain, budget or guaranteed growth.
Template 5.9: Ask how a rebrand affects existing material
Fictional situation: A company announces a rebrand. Your offer concerns existing sales or support assets, whose treatment is not stated publicly.
Hi {firstName}, I saw {company}'s new brand announcement. Are the existing partner guides being updated in the same programme, or kept as they are for now? My work at {yourCompany} covers those guides. I can explain the relevant scope if there is an open task there.
Check before use: The guides and announcement exist. Do not assume that old branding represents an error or that the current supplier needs replacing.
Template 5.10: Reconfirm a live proposal after a leadership change
Fictional situation: You already have an active, authorised conversation. The client names a new leader; you need to confirm the review route rather than approach that leader independently.
Hi {firstName}, we were discussing {definedTask} before the leadership change. Should we continue through you, or is there a new person you want involved in reviewing the scope? I will keep the existing proposal unchanged until we have confirmed the decision route.
Check before use: Send to the existing conversation owner. An organisation-chart change does not reopen a closed or refused approach.
Category 6: Identified visitors: relevant outreach and invited replies (8 templates)
Use these only when LinkedIn actually identifies the visitor and there is an independent professional reason for the message. A visit is not consent, purchase intent or permission to reopen a refusal. Do not try to identify an anonymous visitor.
Template 6.1
Hi {firstName}, saw you viewed my profile yesterday. Anything specific I can help with, or just exploring?
Template 6.2
Hi {firstName}, you visited my profile. We're working in similar spaces. Always happy to connect with peers in {industry}.
Template 6.4: Route an existing client's question to the right person
Fictional situation: An identified person from a current client visits your profile. Your colleague already owns that account and should coordinate any new work.
Hi {firstName}, good to see your name here. {accountOwner} is still your main contact for our work with {company}. If you were looking for information about {specificService}, I can send the relevant outline through them so you do not get two separate approaches.
Check before use: Confirm the relationship and owner internally first. Do not use a visit to bypass an existing account conversation.
Template 6.5: Reconnect with a former delivery partner about an actual request
Fictional situation: A former partner is an identified visitor and has also posted a specific request for a capability you can provide.
Hi {firstName}, I noticed your visit and your post asking for help with {task}. We worked together on {sharedAssignment}, so you know the part I cover. Is the current request for that same delivery role, or has the scope changed? I can send a relevant availability note once that is clear.
Check before use: Both the shared assignment and public request are real. Verify availability before offering it; the visit alone would not justify a message.
Template 6.6: Confirm the permitted format for a supplier response
Fictional situation: An identified visitor has issued a real supplier request that disallows attachments. You need to establish the permitted response format before supplying a scope or pricing basis.
Hi {firstName}, your {supplierRequest} says attachments are not accepted. Would your process accept the requested scope and pricing basis in the message itself, or through an approved web page? I can use the permitted format rather than send a file you cannot assess.
Check before use: The request genuinely invites supplier responses through this channel. Follow its stated submission route and information requirements; do not use a profile view to bypass a tender process or infer a project need.
Template 6.7: Respond to a journalist's stated source request
Fictional situation: An identified journalist has visited your profile and published a request for sources on a subject you directly work on.
Hi {firstName}, I noticed your visit and the source request about {topic}. I can speak about {specificExperience} from my own work, but would not be the right source for {outsideExpertise}. Would a short written background note help you decide whether an interview is useful?
Check before use: The request is current, your experience is supportable and the proposed contribution respects the journalist's format and deadline.
Template 6.9: Deliver the resource an event contact requested
Fictional situation: An identified visitor is someone who asked for a specific resource during a real event conversation. The visit is only a reminder to fulfil that request.
Hi {firstName}, you asked for the {resource} when we spoke at {event}. Here is the version we discussed: {link}. The example in {section} covers your question about {task}. If I have picked the wrong resource, tell me and I will correct it.
Check before use: The conversation and request happened, the link works and the resource is cleared to share. Do not attach a meeting request to fulfilment of a simple request.
Template 6.10: Offer a clear professional route without guessing the reason for a visit
Fictional situation: A relevant, identified visitor appears to be seeking a supplier contact, but has made no request. You can offer one route without claiming to know their intention.
Hi {firstName}, I noticed your visit. I handle {specificTask} at {company}. If that is what you were looking for, the short scope is here: {link}. If it was something else, no explanation needed; I simply wanted to make the right contact route easy to find.
Check before use: There is a relevant professional connection beyond the visit and the scope page accurately describes your work. Do not follow up solely because this message receives no answer.
Category 7: Recruiter outreach and search follow-up (10 templates)
Use the real vacancy, approved details and actual sender affiliation. State constraints early. A recruiter should not invent a vacancy, compensation range, client endorsement or confidential relationship to start a conversation.
Template 7.1: The opportunity (no resume ask)
Hi {firstName}, recruiting for {role} at {company}. Your background in {specific skill} matches what they need. No resume needed yet: open to a 15-min chat first?
Template 7.2: Ask permission to share a confidential role summary
Fictional situation: You are authorised to recruit for a real role, but cannot name the employer in the first message. An approved summary contains enough practical detail to assess interest.
Hi {firstName}, I am recruiting for a {role} position through {agency}. The employer's name is confidential at this stage, but I can share the approved responsibilities, location and compensation range before asking for a call. Would you like that summary so you can decide whether to explore it?
Check before use: You have the mandate and approved information. Do not use confidentiality to hide that the role is speculative or that essential terms are unavailable.
Template 7.3: Check a contract's timing before discussing the fit
Fictional situation: A defined contract requires a start date and commitment that may rule out an otherwise suitable candidate.
Hi {firstName}, I am recruiting a {specialism} contractor for {definedAssignment}. The required start is {date}, for {duration} at {weeklyCommitment}. Are those constraints potentially workable for you? If they are, I can send the actual scope and rate basis before we discuss suitability.
Check before use: The dates, commitment and assignment are confirmed. Do not suggest that availability creates an obligation or a guaranteed offer.
Template 7.4: Clarify hands-on work in a senior-sounding role
Fictional situation: The job title could imply a leadership position, while the actual role includes substantial hands-on delivery.
Hi {firstName}, the {role} I am handling includes direct {deliveryTask} as well as team leadership. I wanted to make that clear because the title alone is ambiguous. Is that combination something you would consider, or are you looking exclusively for a leadership remit?
Check before use: The responsibility split comes from the hiring brief. This allows an early no without asking the candidate to complete an application first.
Template 7.5: State a fixed location requirement up front
Fictional situation: A vacancy has a non-negotiable on-site pattern. The candidate's public profile suggests relevant expertise but does not establish willingness to travel or relocate.
Hi {firstName}, I am recruiting for {role} in {location}. The current requirement is {onSitePattern}; I do not have approval to offer it as fully remote. Would you consider that arrangement? If not, I will not ask you to spend time on the process.
Check before use: State the actual policy, not your prediction of flexibility. Do not infer private family or travel circumstances from a profile.
Template 7.6: Request only shareable work evidence
Fictional situation: A technical or creative role needs evidence of a specific skill, and the candidate may be unable to share employer-owned work.
Hi {firstName}, the team needs to assess {specificSkill} for {role}. If you want to explore it, is there a public or permissioned example you would be comfortable discussing? A short explanation of your contribution is useful; please do not send confidential material from an employer or client.
Check before use: The hiring process genuinely uses that evidence. Accept a suitable alternative when the candidate cannot share proprietary work.
Template 7.7: Update preferences for an opted-in talent relationship
Fictional situation: A candidate previously asked you to retain contact and return when a stated preference could be met. A relevant role now meets that preference.
Hi {firstName}, you previously said you would consider {roleType} if it offered {statedPreference}. I now have an authorised brief that matches that condition. Is it still a useful criterion for you? I can send the scope, or leave your search on hold if your plans have changed.
Check before use: The earlier preference and permission are recorded; check that no later stop supersedes them. Do not treat every old candidate record as an active opt-in.
Template 7.8: Make a candidate referral optional and permissioned
Fictional situation: A candidate has said the role is unsuitable for them, but the conversation remains open and they have not asked you to stop.
Thanks for clarifying, {firstName}. I will close this role for you. If someone in your network independently asks about {specificRole}, you are welcome to pass on this public brief: {link}. There is no need to send me anyone's details or make an introduction.
Check before use: This is a courteous close to an actual conversation, not a way around a refusal. Do not add it after an explicit no-further-contact request.
Template 7.9: Clarify a hiring manager's request before proposing recruitment support
Fictional situation: A hiring manager publicly asks for help with a named vacancy. You need to distinguish candidate introductions from a wider hiring assignment.
Hi {firstName}, your request mentions support with {vacancy}. Are you looking for a small number of candidate introductions, or help running the search and selection process? I represent {agency}, and those are different assignments for us. I can outline the relevant one once the boundary is clear.
Check before use: The request invites supplier responses. Do not imply that you already have suitable candidates unless you have verified that separately.
Template 7.10: Reopen a paused search with the changed facts
Fictional situation: A genuine search was paused and the candidate was told why. It has now reopened with a material change the candidate should know about.
Hi {firstName}, the {role} search we paused in {month} has reopened. The main change is {confirmedChange}; the earlier {unchangedConstraint} still applies. Would you like the revised brief, or should I leave the previous close in place? I will not assume your availability is unchanged.
Check before use: The search is authorised again and the candidate had not opted out. Explain the change; do not present a recycled vacancy as a new urgent opportunity.
Category 8: Agency partnership outreach and buying-stage follow-up (9 templates)
Explain the proposed division of work and any real relationship. Do not imply a client mandate, capacity, commission or endorsement that has not been agreed. Coordinate account ownership before involving a shared client.
Template 8.1: The white-label
Hi {firstName}, your agency works with {client type}. We have a tool that solves {problem} for that exact audience. Open to white-label or affiliate setup. Any commercial terms would need to be agreed separately.
Template 8.2: Check capacity for a defined overflow task
Fictional situation: Your agency has an actual assignment and permission to consider a delivery partner. You can state the work without disclosing the client's identity initially.
Hi {firstName}, we are looking for delivery support on {definedTask}, with {deliverable} needed by {date}. We would retain client coordination. Is that the sort of work your team can assess? If so, I can send a redacted scope so you can judge capacity before we discuss a quote.
Check before use: The assignment, deadline and subcontracting route are real. An agency's advertised service does not prove that it has spare capacity.
Template 8.3: Respond to a buyer's request for two complementary disciplines
Fictional situation: A buyer has asked for a proposal combining two disciplines, and you cover only one. You want to establish whether a joint response is sensible.
Hi {firstName}, a buyer has asked us to cover {disciplineA} and {disciplineB}. We cover A; B appears to fit your work. Would you be open to reviewing the B scope separately? Before involving the buyer, we would need to agree responsibilities and confirm their permission for a joint response.
Check before use: The buyer request is genuine. Do not claim that the other agency has joined the team or share client material before permission is established.
Template 8.4: Offer a referral without transferring a person's details
Fictional situation: A prospective buyer needs a service outside your scope. They are willing to receive another supplier's public details, and you are checking whether that supplier wants the referral.
Hi {firstName}, an enquiry we cannot serve concerns {task}. It appears relevant to your published scope. Are you currently considering that work? If so, I can pass your public contact page to the enquirer; I would not forward their details without asking them first.
Check before use: Check suitability rather than promising the referral will become a sale. Disclose any referral arrangement when it becomes relevant; do not invent a fee.
Template 8.5: Propose a joint educational example with a clear evidence boundary
Fictional situation: Two agencies cover adjacent parts of one buyer task. You have a specific educational format in mind, without a customer story available to use.
Hi {firstName}, your article on {taskPartA} complements our work on {taskPartB}. Would you consider a joint walkthrough of one fictional example, with each team explaining its decisions? I suggest keeping it separate from customer claims and agreeing the outline before either of us prepares material.
Check before use: You have read the work you reference. Do not imply the other agency endorses your product or is already committed to co-marketing.
Template 8.6: Evaluate a potential integration partner's fit
Fictional situation: You need a partner for a specific integration boundary. Public claims alone do not establish whether it can support your actual environment.
Hi {firstName}, we need to connect {systemA} to {systemB} for {definedWorkflow}. Your team lists work with B. Could you confirm whether you assess that exact boundary, including {knownConstraint}? A brief fit check would help us decide whether to send the technical scope.
Check before use: Name the real systems and constraint. Avoid saying that an integration is supported until the partner has verified the relevant version and route.
Template 8.7: Coordinate a shared prospect's supplier review
Fictional situation: A prospect has independently involved both agencies. You want to prevent conflicting answers or duplicate approaches, without assuming either supplier controls the account.
Hi {firstName}, {prospectContact} has included both our teams in the {task} review. Could we agree which questions each team will answer, and send one clear responsibility note back to them? I do not want the buyer to receive overlapping commitments or assume either team owns the other's work.
Check before use: Both teams' involvement is authorised and known to the buyer. This coordinates an existing process; it is not permission to share other prospects.
Template 8.8: Clarify an international handover boundary
Fictional situation: A delivery arrangement needs a defined working-hours handover. You are seeking coverage for the handover task, not unlimited regional availability.
Hi {firstName}, our proposed assignment needs someone to receive {handoverItem} during {timeWindowAndTimezone}. The task is {specificAction}, with escalation staying with our team. Can your team assess that coverage? I can send the exact boundaries; we are not asking for general round-the-clock support.
Check before use: The timezone, action and escalation owner are known. Do not promise continuous coverage to the client before the partner accepts it.
Template 8.9: Confirm the order and invoice route for joint work
Fictional situation: You and a partner have agreed the proposed division of work. The buyer has requested one supplier and one purchase order, while the partner would normally contract directly with the buyer.
Hi {firstName}, the buyer has requested one purchase order for the joint {scope}. Would your team consider working through {proposedLeadSupplier}, or do you require a separate direct agreement? Before we submit, can we confirm the proposed order and invoice route, so neither team commits the other to an arrangement it has not accepted?
Check before use: The buyer requirement and partner discussion are real. Ask the authorised commercial owners to confirm an acceptable route; do not assume either party accepts a purchase order, subcontract or invoice, or make claims about legal, tax or accounting consequences.
Category 9: Outreach follow-up by conversation state (10 templates)
Choose the example that matches the actual conversation state. These are alternatives, not a sequence to send in order. Silence alone does not justify repeated reminders. Honour refusals, pauses, existing owners and agreed return dates.
Template 9.1: A reminder when the conversation permits it
Hi {firstName}, no rush, but wanted to make sure my last note didn't get buried. Quick recap: {1-line value prop}. Want a 10-min call this week or next?
Template 9.2: An available resource relevant to the discussion
Hi {firstName}, last ping from me. We just published {relevant article / case study}. Might be useful even if you don't take a meeting: {link}.
Template 9.3: Close an approach without another automatic reminder
Hi {firstName}, completely understand if not the right time. I'll stop pinging. Door's always open if {trigger} comes up.
Template 9.4: Honour an agreed decision date
Fictional situation: A buyer explicitly asked you to return after a named internal review. That date has passed; there is no refusal or later pause.
Hi {firstName}, you asked me to return after the {reviewName} review on {date}. Is {definedTask} still something you want to assess? If the review changed the priority, I can close our proposal rather than keep sending reminders.
Check before use: The return instruction and date are recorded. Do not infer a decision deadline from your own sales calendar.
Template 9.5: Make the next unresolved proposal choice explicit
Fictional situation: You have answered the buyer's questions and the next step depends on a specific choice between two scopes.
Hi {firstName}, I have answered the questions on {proposal}. The remaining choice is whether to cover {scopeA} alone or include {scopeB}. If neither matches what you need now, we can stop here. Otherwise, tell me which scope to carry into the final version and I will update that document.
Check before use: Both scopes are real and still available. Do not use a forced A-or-B question when the buyer has already declined.
Template 9.6: Correct a material error in your own earlier message
Fictional situation: You discover that information you sent was wrong. The correction matters whether or not the buyer continues the conversation.
Hi {firstName}, I need to correct the {figureOrTerm} in my earlier note. The accurate position is {correction}; the earlier version should not be used. I have attached or linked the corrected document here: {link}. No response is needed unless the change raises a question for you.
Check before use: Verify the correction and identify the superseded version. Do not dress up a promotional update as an error correction.
Template 9.7: Fulfil a requested supplier-document step
Fictional situation: A buyer requested a specific approved document. You have supplied it through the agreed route, and want to make the delivery location clear once.
Hi {firstName}, the {requestedDocument} is now in {agreedWorkspace} under {filename}. It addresses your question about {specificRequirement}. If your review needs a different approved document, let me know which one; otherwise I will leave you to complete the review.
Check before use: The document exists in that location and is cleared for the recipient. Do not send credentials, sensitive records or invented certifications as supporting proof.
Template 9.8: Update a genuine delivery constraint before acceptance
Fictional situation: The proposed work has not been accepted and your actual available schedule has changed. The buyer needs accurate planning information.
Hi {firstName}, a delivery update for the unaccepted {task} proposal: the earliest date I can now support is {date}, subject to the agreed inputs. I have updated the schedule in {document}. If that no longer works for you, I understand; I am not asking you to accept the old date.
Check before use: The change is real and the stated date is supportable. This is a planning correction, not manufactured scarcity.
Template 9.9: Provide the reference route the buyer actually requested
Fictional situation: A buyer asked about a particular delivery concern. A former client has explicitly agreed to discuss that concern with them.
Hi {firstName}, you asked how we handled {specificDeliveryConcern}. {referencePerson} has agreed to a reference conversation on that topic. If you still want it, I can introduce you through the route they approved. There is no need to book another sales call with me first.
Check before use: Obtain current permission from the reference and check what they are willing to discuss. Do not imply a broader endorsement or disclose their details without approval.
Template 9.10: Ask for the missing input needed to finalise an agreed pilot
Fictional situation: The buyer has asked for a pilot proposal, but one specific acceptance condition remains unanswered. You should not guess it.
Hi {firstName}, the pilot draft is ready apart from {specificAcceptanceCondition}. Could you confirm {oneConcreteQuestion}? Without that answer I would be guessing what your team needs to accept. I will keep the draft on hold rather than send it as a finished scope.
Check before use: This is a genuinely requested pilot with an essential gap. Do not invent an acceptance question to generate another touchpoint on a cold proposal.
Category 10: Re-engagement for a relevant commercial reason (6 templates)
Time passing is not a reason to restart contact. Each example below needs a specific relevant request or commercial development. A previous refusal or opt-out remains in force; a new job or announcement does not erase it.
Template 10.1
Hi {firstName}, been a while. Saw your recent post on {topic}. Reminded me to reach out. How's {company / role} treating you?
Template 10.3: Ask permission for a relevant introduction
Fictional situation: Someone you know has asked to meet a professional with an old contact's specific experience. The contact has not yet agreed to an introduction.
Hi {firstName}, a colleague is looking to speak with someone who has worked on {specificTask}. Your contribution to {sharedWork} came to mind. Would you be open to seeing their short request before deciding about an introduction? I have not shared your details or suggested that you have agreed.
Check before use: The request and shared work are real. Send the request only after permission, and accept a no without asking for someone else's details instead.
Template 10.6: Follow through on an agreed project notification
Fictional situation: After a completed assignment, a contact asked to be told when a specific external dependency changed. You have verified that change.
Hi {firstName}, at the close of {assignment}, you asked me to let you know if {dependency} changed. The official update now says {verifiedChange}: {sourceLink}. I have not assessed what that means for your current setup. If the question is still relevant, that would be a separate piece of work to define.
Check before use: The notification request is recorded and the update is accurately sourced. Avoid converting the announcement into an unsupported diagnosis of the old project.
Template 10.7: Notify someone about the exact capability they asked to revisit
Fictional situation: An earlier prospect said a particular requirement prevented fit and explicitly asked for a notification if it became demonstrably available. You now have relevant evidence.
Hi {firstName}, you asked us to return only if {specificRequirement} became available. We can now show that exact workflow in {currentEvidence}. If the requirement is still relevant, would you like the evidence link? The rest of the fit would still need checking; I am not assuming the old project is open.
Check before use: Verify the capability and evidence before sending; a roadmap promise is insufficient. Honour any later refusal, and do not generalise one demonstrated step to the whole workflow.
Template 10.8: Distinguish a former candidate's new hiring request from their old job search
Fictional situation: A person you previously spoke to as a candidate now publicly asks for hiring support in their current role. The old candidate relationship does not define this new task.
Hi {firstName}, we last spoke about your own search. I saw your current request for help hiring {role} at {company}. Is it appropriate for {agency} to respond to that brief, or is the request limited to direct candidate referrals? I will treat this separately from your earlier candidate record.
Check before use: The current request invites that type of response. Do not reuse private candidate information to personalise a supplier pitch.
Template 10.9: Reconfirm the scope before repeating an old engagement
Fictional situation: A past client has asked you to repeat earlier work after a long gap. You need current inputs before quoting the same assignment again.
Hi {firstName}, thanks for asking us to repeat {previousAssignment}. Before I reuse the old scope, could you confirm whether {keyInputOrAudience} is still the same? The earlier output was designed around that condition. If it has changed, I will show the effect on the work rather than quietly quote the old version.
Check before use: The new request came from the client. An old successful engagement does not prove that its scope, fee or result applies now.
Choose the next step from the actual conversation
Use one example only when it fits the situation. Keep genuine refusals closed, respect pauses and route an existing account through its owner. Verify every resource and factual claim before sending; do not promise something you cannot supply.
For LinkedIn prospecting, consider the whole commercial task: targeting relevant people, outreach, conversations and follow-up. Review current Leadsforlinked workflows and offers to assess whether they fit your task. These templates do not establish product execution or predict acquisition results.