All signal plays

Signal play / They came to you

A visit from an account on your list

Someone from a company on your list reads your site, and the visit is matched to the company.

The account is looking, often at the pages that show how you work or what you charge. You know the company but not yet the person, so the play is to find the right person and give them a reason.

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

On your website, in your Clay workspace and your CRM

Illustration
  1. Visits are matched to companies and checked against your target list, with customers and open deals left out.

  2. The visit is written to the account in your CRM with the pages read.

  3. The person who owns the problem those pages answer is found and checked, then becomes a call task.

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
“I work with plant teams on how orders reach the schedule, and I think that sits with you.”

The question after it

“How is your team handling it this quarter?”

What our rep never does

Never says they visited the site or names a page they read.

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

The first message, by Email

Illustration

Plant teams looking at how they schedule work usually ask one thing first: how long the switch takes. The honest answer depends on how many lines you run. How many does yours run today?

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

  • The target list visits are matched against.
  • The call script and the first message, before anyone is contacted.
  • Each meeting, accepted or rejected against the written definition.

You keep

  • Every matched visit, on the account in your CRM.
  • The retargeting audiences, in your ad accounts.
  • 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, never the visit.
  • A visit names a company, not a person. The person is found and checked before anyone dials.
  • Customers and open deals are left out before anyone is contacted.

How far we run it today.

Built for clients. On our own pipeline it is drawn and not yet built.

Our services that run it
GTM engineering, then Paid media, then RevOps, then BDR
What it costs
Each service has its own published price. See pricing

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