All signal plays

Signal play / They came to you

A reaction to your post

Someone at a company on your list comments on, reposts or reacts to a LinkedIn post from your founder or team.

They read something your people wrote and chose to respond in public. That is a warmer start than any cold line, and the post gives the call its topic.

How it is spotted.

In your own tools, not ours. The steps below run where the heading says, and what they find stays there.

From the signal to a call task

In your LinkedIn, your Clay workspace and your CRM

Illustration

  1. First

    Anyone you must never message, such as customers, open deals and partners, is on a blocklist before anything is collected.

  2. Then

    Everyone who engaged is collected every morning with the post and their comment, and checked against a short list of facts.

  3. Last

    Each match is written to your CRM with the post attached, and the warmest become call tasks.

What this shows: where this signal is read and where it lands. Both are in accounts in your name.
What this page is
A signal play: one thing that happens at a company on your list, and what we do about it, from spotting it to the call.
The examples
The examples are written for a made-up company that sells scheduling software to manufacturers.

The call, and the first message.

A rep on our payroll picks up the phone. This is the line the call opens with, the question that follows it, and the written message that goes beside it.

The first line of the call

Illustration
“You commented on our post about changeovers, so I wanted to hear how your plants handle them.”

The question after it

“Where does the schedule break first when an order changes?”

What our rep never does

Never reads their comment back to them as a sales point.

Your yesWaits for you: the call script and the first message, before anyone is contacted.

The first message, by LinkedIn

Illustration

Thanks for the comment on the post about changeovers. The part most plant teams get stuck on is who owns the schedule when an order changes. Who owns it at yours?

Held to our own message rules: three sentences at most, a question, no link and no pitch.

What waits for your yes, and what you keep.

You approveYour yes

  • Whose posts are watched and who is never messaged.
  • The call script and the first message, before anyone is contacted.
  • Each meeting, accepted or rejected against the written definition.

You keep

  • The blocklist and the list of authors watched.
  • Every engagement, with the post and the comment, in your Clay workspace.
  • Every call note and outcome, written to your CRM with the signal attached.

Where it goes wrong, and the rule that stops it.

  • A person is matched by profile or work email, never by name.
  • Code checks every draft before a person reads it, and a person starts every campaign.
  • This entry is for your own people's posts. When the post is someone else's, the message talks about the topic and never mentions the reaction.

How far we run it today.

We run this on our own pipeline every morning.

Our services that run it
LinkedIn content, then GTM engineering, then BDR
What it costs
Each service has its own published price. See pricing
Where it can start
A plant starts a new line. Each is a sample of the ad we would run on a buying signal, with who sees it and the email and call that follow the same week.
The guide behind it
The social listening play, the build written out step by step.

The other signal plays.

Have us run this play for you.

We build it in your tools and run it with your team, in accounts in your name. You approve the script before anyone is called.

Or skip the form