Warm Engager Followup

Warm Engager Follow-Up

Solo/default path: a founder, AE, or BDR can run this from one monitored personal profile or engager list and approve every touch themselves. If you later run it with a team, add owner-based routing, per-seat cap sharing, approval review, and FirstTouch/HubSpot logging checks.

Outcome: Convert recent LinkedIn engagement (post likes and comments) into booked conversations. Log to HubSpot when the connected FirstTouch-HubSpot integration supports it; otherwise log the execution record in FirstTouch and state that CRM timeline logging is unavailable.

First-run onboarding gate

Before running this skill for the first time in a workspace, load ../../references/onboarding.md and complete the onboarding questions. Do not proceed until you know: LinkedIn account type (free/basic = no connection notes; recommend 10 connection requests/day and never exceed the FirstTouch max of 20/day; Sales Navigator/Premium = connection notes available; recommend 20 connection requests/day and never exceed the FirstTouch max of 30/day), HubSpot access (MCP, service key/private app token, HubSpot list only, or none), and which play the user wants to run. Recommend high-intent plays before outbound to keep the LinkedIn account healthy. If HubSpot is unavailable, do not run HubSpot-specific steps unless the user provides a HubSpot list FirstTouch can access.

When to use

• The user says "follow up on people engaging with my posts," "who liked my last post," "monitor this competitor founder/influencer," "work my warm leads"
• A BDR/AE/RevOps user wants to monitor a CEO, founder, exec, company thought-leader, competitor founder, or category influencer profile and route engagers to reps
• A post or campaign just got engagement and you want to turn it into pipeline
• Weekly/biweekly warm-lead follow-up motion

Inputs

• Window: how far back to pull engagement (default: 7 days)
• Post scope: specific post, all recent activity, or a monitored CEO/exec/leadership profile (default: all)
• Tier filter: which engagers to prioritize (default: ICP match + seniority)

Step-by-step

1. Pull engagement (FirstTouch MCP)

Before using monitored profiles, confirm Social Engagement is enabled in the workspace (get_social_engagement_config). If it is not enabled, turn it on through the FirstTouch MCP monitored-profile flow when the connected account has permission (manage_social_engagement_monitored_profile with action=add and enableSocialEngagement=true, or write_social_engagement_config with isEnabled=true); otherwise ask for a user-provided/exported engager list and continue from that list instead of promising monitored-profile capture. Social capture is a FirstTouch setting - it is configured in FirstTouch (settings or the MCP config tools), not in HubSpot. Confirm it is on rather than assume. After capture is first enabled, allow up to a day for engagement signals to start appearing; an empty engager list in the first hours is not a failure. Social Engagement can monitor LinkedIn profiles for post likes and comments. Prefer the user's own founder/leadership personal profile. FirstTouch does not track company-page/profile engagement. If they do not have enough owned engagement yet, plug in a relevant competitor founder, category influencer, or executive profile and work the ICP-fit people engaging there. User-provided/exported engager lists also work. Do not use profile views as a signal; FirstTouch does not provide profile-view capture for this play.

Get recent engagers - post likes and comments - within the window (list_social_engagement_engagers). Record for each: name, title, company, engagement type, what they engaged with, timestamp.

1a. If monitoring a leader, competitor, or influencer profile

Use the FirstTouch social engagement monitored-profile flow before pulling engagement:

• add or confirm the CEO/founder/exec, competitor founder, or influencer profile as a monitored profile, for example manage_social_engagement_monitored_profile with action=add and enableSocialEngagement=true when that tool is available in the connected harness
• confirm the monitored profile is authorized by the customer and relevant to the sender/team
• pull engagers from that monitored profile's posts, then route drafts through the appropriate sender/owner for approval
• if drafts should route through the linked Social Engagement flow instead of one-off dynamic actions, publish that linked flow first with manage_flow_publication before expecting captured engagers to enter it
• if the monitored-profile tool is unavailable in the connected harness, ask the user to provide a FirstTouch-accessible engager list exported from the leadership post; do not imply the play is broken

1b. Monitoring external profiles

Monitoring uses public post likes and comments only - the same information you would see scrolling the profile yourself; nothing private is accessed. If a prospect asks how you found them: "Saw you engaged with {person}'s post on {topic}."

2. Qualify the engager

If qualification requires FirstTouch discovery or enrichment beyond the captured engager fields, run Gate 3a from ../../references/safety-governance.md: preview a small sample, state estimated maximum credits, and get approval for bulk credit spend.

For each engager, run Gate 0 suppression/DNC first, then check:

• If HubSpot is connected: existing contact context, owner, lifecycle stage, suppression fields, and prior activity
• If HubSpot is not connected: ask for or use the saved ICP brief (industries, company size, geography, target titles, exclusions) and qualify from FirstTouch/enrichment/user-provided fields
• Suppressed, unsubscribed, opted out, or DNC? → skip and log the reason
• Already in an active sequence or recently contacted? → skip (Gate 1: duplicate check)
• Do they match ICP? → tier them (T1 strategic / T2 mid / T3 volume)

If no ICP is defined and HubSpot is unavailable, stop and ask the user to define ICP before drafting.

3. Score and prioritize

Rank by: ICP fit + seniority + engagement depth (commented > liked). Produce a prioritized list.

4. Draft per engager (load firsttouch-messaging skill)

For each T1/T2 engager, draft the appropriate message type:

• Not yet connected → connection request
• If the sender has Premium / Sales Navigator and this is a warm engagement signal, use a short connection note referencing the engagement.
• If they do not have Premium / Sales Navigator, send the connection without a note.
• Already connected, no recent FirstTouch-tracked message → opener referencing the engagement

Preferred opener pattern after engagement: > "Thanks for engaging with some of my content. Anything stick out?"

Keep drafts conversational, usually 2 sentences max, and optimize for the smallest next step. Run the messaging quality gate on each.

5. Present batch for approval

Output a review table: | # | Prospect | Engagement | Signal | Owner | Message type | Draft | Each row clearly marked "awaiting approval - will not send."

6. After approval → execute + log (FirstTouch MCP)

On human approval per row:

• before creating any one-contact LinkedIn action, run get_dynamic_action_guide, then call add_dynamic_action in the supported order
• if a LinkedIn message should only send after a connection request is accepted, append it to the connection_accepted branch rather than queueing it as an immediate message
• FirstTouch sends the LinkedIn action
• If the connected FirstTouch-HubSpot integration supports timeline logging, log the touch to the HubSpot contact timeline and confirm log success; if it fails or is unsupported, alert (Gate 5) and keep the FirstTouch execution record
• If HubSpot is not connected, log the execution record in FirstTouch and clearly state that CRM timeline logging was skipped

7. Track

Tag these contacts with a warm_engager_followup property/list so the team can measure downstream replies, meetings, and influenced deals.

Output (deliverable)

A Warm Engager Follow-Up batch:

• Prioritized engager list with signals
• Drafted messages, gated for approval
• Send log + HubSpot timeline confirmation when the connected integration supports it; FirstTouch execution log when it does not
• Tracked cohort for attribution

Examples

Trigger: "Follow up on everyone who engaged with my post this week." Signal source: Their comment/like on your specific post, the strongest possible "why now." Draft (connection request, ≤300 chars): "Hi Maya, appreciated your comment on the HubSpot attribution post. Connecting with RevOps leaders thinking through social attribution. Happy to compare notes on what good measurement looks like."

Pitfalls

• Treating all engagers equally - a competitor employee who liked your post is not a lead. Filter by ICP.
• Skipping the duplicate check - half of engagers may already be in a sequence. Always gate.
• Generic "thanks for the like" - that's not a signal-led message. Tie it to their context.
• External-profile ambiguity - if the signal came from a CEO/exec/company, competitor founder, or influencer profile, name that monitored profile and route through the right sender rather than pretending it was the rep's own post.
• Sending without approval - never. Gate 4.

Reference

• Messaging: [../../references/messaging-framework.md](../../references/messaging-framework.md)
• Safety gates: [../../references/safety-governance.md](../../references/safety-governance.md)
• System model: [../../references/system-grounding.md](../../references/system-grounding.md)

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: First-Touch-Inc
• Source: First-Touch-Inc/firsttouch-agent-skill-packs
• License: MIT

Install and usage instructions live in the source repository linked above.