All signal plays

Signal play / Seen in public

A reaction to a competitor's or creator's post

Someone at a company on your list comments on, reposts or reacts to a LinkedIn post about your field from a competitor or a voice your buyers follow.

They chose to respond in public to the problem you solve, which says what is on their mind this week. They did not respond to you, so the reason to talk is the topic, never the post.

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 Clay workspace and your CRM

Illustration
  1. The authors to watch go into one file, each marked as a competitor or a creator, beside a blocklist of customers, open deals, partners and the authors' own staff.

  2. Everyone who engaged is collected every morning and checked against six facts about the person and their company, such as their role and the company's size.

  3. Each person who passes goes to a campaign written on the topic, and those at accounts on your list become call tasks.

What this shows: where this signal is read and where it lands. Both are in tools 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
“I am calling about changeovers, because it is what operations leads at plants like yours keep raising this month.”

The question after it

“How does your team decide what moves when an order changes?”

What our rep never does

Never names the post, the reaction or the person who wrote it.

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

The first message, by LinkedIn

Illustration

Changeovers come up with most plant teams right now, mostly over who decides what moves when an order changes. Some teams have handed that decision to the schedule itself. How is it decided 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

  • Which authors 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 list of authors watched and the blocklist.
  • Every engagement, with the post and the six facts, 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.

  • The call and the message talk about the topic and never name the post, the reaction or the author.
  • Connection requests go out blank.
  • A person is matched by profile or work email, never by name.
  • A person reads the first batch and starts every campaign. Nothing sends on its own.

How far we run it today.

We run this on our own pipeline every morning, on competitors' and creators' posts as well as our own.

Our services that run it
GTM engineering, then BDR
What it costs
Each service has its own published price. See pricing
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 run it with your team, in tools you own. You approve the script before anyone is called.

Or skip the form