Sales should follow up when someone fits the customer profile, has a relevant role and has given the team a useful reason to start a conversation. Check existing customers, open deals, opt-outs and current outreach before adding anyone to a new sequence.
A like can help you notice a person. A specific question can help you understand a problem. The next decision is whether a useful sales conversation makes sense for that person now.
If you use FirstTouch Social Engagement, it surfaces captured likes and comments from supported LinkedIn person profiles and company pages. It does not monitor an individual post URL. Collection runs daily and can take 24+ hours, so check the post date before deciding on follow-up.
Start here: check the existing relationship, score fit and context, then choose one next step: draft a relevant follow-up, research, route to the owner or exclude.
Check the existing relationship before scoring
Look up the person and company in the records your team trusts. Use current customer, deal, opt-out and outreach data. A strong score never overrides these checks.
- Opt-out or a matching exclusion: keep the person out of new prospect outreach.
- Current customer or open deal: send the context to the account or deal owner. Keep it out of a new cold-prospect sequence.
- Existing conversation or active outreach: review that history with the current owner before creating another touch.
- Uncertain identity or company match: hold for research. A name match alone is too little to choose a recipient.
This creates useful handoffs. A customer asking about a workflow may need help from their account team. A prospect already discussing that workflow with a rep needs continuity.
Use a six-point follow-up scorecard
A person on your team applies these points. Score three questions from zero to two and write down the evidence. FirstTouch surfaces engagement; your team makes this manual assessment. The worksheet is suggested guidance, not a built-in FirstTouch score or a validated prediction of purchase.
| Question | 0 points | 1 point | 2 points |
|---|---|---|---|
| Company fit | Outside the customer types you serve. | Plausible fit; an important fact is missing. | Verified customer-type fit and a use case you can serve. |
| Person fit | No relevant responsibility or influence is evident. | Relevant contributor or credible influencer. | Owns the relevant workflow, team or project. |
| Problem context | A reaction alone or unrelated conversation. | Relevant topic or additional account context, without a specific need. | Describes a relevant problem, asks a specific question or requests help. |
Consider a follow-up draft at five or six points, with company fit at two and both other scores at least one. At three or four, research the missing fact or keep the person in a content audience. At zero to two, leave them out of this sales play. A direct request still deserves an appropriate response while you establish fit.
Keep unknown facts unknown. Company size can describe your segment, but it does not replace a relevant use case. Include small businesses and agencies when they are customer types you serve.
Download the blank follow-up scorecard (CSV) to record the checks, evidence, owner and next step.
Four examples of the decision
These examples are fictional. They show how to apply the worksheet, not measured customer results.
A sales leader likes a general leadership post
The VP works at a 200-person company you can serve and owns the relevant team. Company fit: 2. Person fit: 2. Problem context: 0. Total: 4.
Decision: research or keep them in a content audience. The role fits, but the reaction provides no specific reason to pitch.
A RevOps owner asks about webinar follow-up
A relevant operator at a 120-person company comments that webinar leads are falling between sales and marketing. You have verified the company fit. Scores: 2 + 2 + 2 = 6.
Decision: answer the question and offer a useful next step. A checklist about ownership and exclusions fits the problem they raised.
An agency founder asks about a client workflow
An eight-person agency is a customer type you serve. Its founder describes a relevant client problem. Scores: 2 + 2 + 2 = 6.
Decision: review a follow-up. Confirm the intended client setup and any commercial permissions before proposing it. Small headcount alone is no reason to discard the person.
A strong-fit commenter already has an open deal
The person has a clear need, but the company is already in an active opportunity.
Decision: route the comment to the deal owner. The existing relationship decides the next step before points do.
Use the context to help, then qualify
For the webinar example, a short response could be:
Happy to share a follow-up scorecard. Are you deciding who should follow up, or how to run the workflow?
That gives the person an easy way to clarify the problem. Refer to what they actually said. A reaction alone does not give you the same conversational context as a request for help.
Add first-party context carefully
A form submission, event registration, previous conversation or known customer record can change the decision. Keep the source and date beside the score. A company's website visit adds account context; it does not identify which employee visited or establish that the LinkedIn engager did.
For example, an event registration can support a useful event reminder. A separate request for a demo should go to the appropriate sales owner. Neither needs to be disguised as a cold message about a like.
Review the decisions each week
Compare who was excluded, routed, researched and selected for follow-up. Then inspect the actual replies and qualified conversations. Check whether the context was useful, the intended owner followed up and missing information was resolved.
Adjust a score or rule when the evidence supports it. Keep the original signal and decision reason so you can distinguish a promising topic from a play that produces relevant conversations.
After the decision: route and record the work
Make the handoff explicit. For example, a rep reviews the six-point webinar prospect, chooses a useful response, then checks the review controls for the chosen route before any outbound action. The score records a selection decision. The message still needs its own review and execution steps.
- Bring the relationship checks together. Use your current source of customer, deal and outreach history. FirstTouch exclusion lists support contact emails, company domains, eligible saved audiences and, on paid plans, supported synced HubSpot lists. Confirm the intended records are covered and the workflow applies the relevant exclusion policy.
- Choose where the work belongs. Use FirstTouch Flows, HubSpot workflows or an agent according to where the actionable context lives. HubSpot is optional. CSV files and existing audiences are among FirstTouch's non-HubSpot source options.
- Review the proposed action. Keep the recipient, reason, intended sender and exact message together. Set the review responsibility and relevant action controls for the chosen route before outreach begins.
- Record what happened. Keep a reaction, reply, booked meeting and opportunity as separate outcomes. Use the outreach reporting guide for the measurement definitions. If HubSpot is your record, supported sync depends on configuration and matching.
Build the follow-up play around the decision
Bring one real example, your customer criteria and your current exclusions. We can help map who should be followed up with, who owns the work and where the result should be recorded. Book a FirstTouch demo.
Common questions
Should sales contact everyone who likes a LinkedIn post?
No. Check exclusions and existing relationships first, then assess company fit, person fit and the context of the engagement. A relevant reaction can justify research without justifying a sales message.
Does a LinkedIn comment prove buying intent?
No. A specific question can reveal a relevant problem, but it does not establish a purchase plan or permission for a sales sequence. Answer the question and establish relevance before proposing a sales conversation.
Can we use this scorecard without HubSpot?
Yes. Use the customer, deal, exclusion and outreach records your team maintains. FirstTouch supports non-HubSpot sources such as CSV files and existing audiences. HubSpot can be an optional source when connected and configured.
What if an engager is already a customer or has an open deal?
Keep them out of a new cold-prospect sequence and route the context to the account or deal owner. The owner can decide whether a customer conversation, deal follow-up or no action is appropriate.
