Inbound Speed To Lead

Inbound Speed-to-Lead

Solo/default path: a single AE or founder can run this from a meeting-booked/signup 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: Add a fast, light LinkedIn touch to high-intent inbound moments - booked meetings, signups, trials, demo requests - when the agent runs or on a configured schedule. True live speed-to-lead uses the HubSpot workflow → FirstTouch action-card path when the portal supports it; agent-run or scheduled list/import workflows are fallback paths.

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

• A meeting is booked and the AE wants same-day LinkedIn auto-connect/follow-up
• New signup or trial starts in HubSpot
• Demo request submitted
• Inbound contact reaches a high-intent lifecycle state
• The user says "attach LinkedIn to inbound" or "improve speed to lead"

Inputs

• Trigger event: meeting booked / signup / trial / demo / hand-raise form / list membership
• Window: how soon after trigger to act (default: same day)
• Connection-note policy: use note only if sender has Premium/Sales Nav and the motion is warm enough

Step-by-step

1. Pull inbound contacts

Path A - HubSpot connected: query the trigger event, including meeting booked, signup, trial, demo, form-fill, or list-membership events, and return contacts created or updated in the window. Capture: name, title, company, owner, event type, timestamp, lifecycle stage, LinkedIn URL.

Path B - no HubSpot access: ask for a FirstTouch-accessible inbound list, CSV import, audience, or other connected source list containing the hand-raisers. If the contacts exist only as raw rows, have the user import them in the FirstTouch app or build an audience from them (create_audience_from_profiles) - the agent should name which audience it will work from. A FirstTouch-accessible list means FirstTouch can read the contacts from an imported CSV/audience or connected source. State clearly: this is list/import-based unless a source continuously feeds FirstTouch; true speed-to-lead automation requires HubSpot or another connected inbound source. Capture the same fields when available. State that HubSpot owner routing and CRM timeline logging are unavailable until HubSpot is connected.

2. Check readiness

For each contact:

• Run Gate 0 suppression/DNC check from ../../references/safety-governance.md; if suppressed or unsubscribed → skip
• Has owner? if HubSpot is connected and no owner exists → stop, report the no-owner contact, and ask the user/RevOps to assign it before drafting
• Has LinkedIn URL / can be matched? if no → enrichment queue
• Already connected? yes/no
• Recently contacted? if yes → skip

3. Choose the action

• Not connected → connection request
• Already connected → light opener / follow-up

4. Draft the message (load firsttouch-messaging)

Use the booked-meeting or inbound event as the signal.

Rules:

• conversational, usually 2 sentences max
• smallest possible ask
• do not force a meeting immediately unless the inbound event explicitly warrants it
• if Premium/Sales Nav is available, a short connection note is allowed

Example directions:

• Meeting booked → "Saw we have time on the calendar. Wanted to connect here too so it is easy to stay in touch before the conversation."
• Demo request → "Saw you just requested a demo. Wanted to connect here too in case helpful as you evaluate."
• Trial signup → "Saw you started a trial. Happy to be useful if anything jumps out as you get into it."

5. Present for approval

Show per contact: | Contact | Trigger | Connected? | Message type | Draft | Awaiting approval only.

6. Execute + log

On approval per row:

• before creating any one-contact LinkedIn action, run get_guide with topic=dynamic_actions, 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
• send via FirstTouch
• log to the HubSpot timeline and tag as inbound_speed_to_lead when the connected FirstTouch-HubSpot integration supports it; otherwise log the execution record in FirstTouch and state that CRM logging was skipped

7. Track

Measure touch-to-meeting rate and reply rate for inbound contacts who received the LinkedIn touch versus those who did not.

Output

• prioritized inbound queue
• drafted social touches, gated for approval
• send + log confirmation
• tagged cohort for attribution when HubSpot/list metadata is available

Pitfalls

• treating all inbound equally - prioritize hand-raisers over lightweight ebook downloads
• asking for too much too fast - keep it conversational
• missing the same-day window - this play depends on running the agent quickly or scheduling it against a connected inbound source

Reference

• HubSpot setup / real-time action-card path: ../../references/hubspot-setup.md
• Messaging: ../../references/messaging-framework.md
• Safety: ../../references/safety-governance.md