Yadulink / Documentation / Inbound leads

Do not let inbound LinkedIn signals die in the inbox.

Inbound leads often come from replies, comments, visits, or already warm requests. The workflow should qualify them quickly without creating sales noise.

Inbound leads

Why LinkedIn inbound leaks

Inbound signals are scattered across inbox, posts, lists, and CRM. Without prioritization, the best contacts are often handled after volume actions.

Inbound leads

Role of webhooks

A useful webhook does not push everything. It routes events that change a next action: reply, accepted invitation, repeat visit, or warm lead.

Inbound leads

Sales decision

Each inbound lead should get a status, priority reason, owner, and short action: reply, qualify, schedule, or exclude.

Verified facts

What this documentation should make explicit.

Purpose

Inbound leads often come from replies, comments, visits, or already warm requests. The workflow should qualify them quickly without creating sales noise.

Workflow proof

Inbound signals are scattered across inbox, posts, lists, and CRM. Without prioritization, the best contacts are often handled after volume actions.

Assistant prompt

Help me handle inbound LinkedIn leads in Yadulink: inbox, comments, visits, qualification, CRM, replies, and forgotten opportunities.

Verification method

How to turn the guide into an operational test.

  1. 01 Inbound handling Group inbound signals: replies, accepted invitations, comments, repeat visitors, and read messages.
  2. 02 Inbound handling Separate explicit demand, objection, curiosity, out-of-ICP, and weak signals.
  3. 03 Inbound handling Prepare a reply or CRM task only when context justifies an action.