All signal plays

Signal play / They came to you

A request from your website

Someone fills in a form on your site or asks for a meeting.

They asked. The risk is not interest. It is a slow reply, and a first call spent finding out who they are.

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. First

    The email on the form is turned into a company and a job title before anyone picks up the phone.

  2. Then

    Each fit check answers pass, fail or unknown, with its evidence. A personal email address goes to a person to look at.

  3. Last

    The rep gets the request with the verdict and the evidence, and follows up while it is fresh.

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
“Thanks for getting in touch about scheduling. I looked at your plants before calling so I would not waste your time.”

The question after it

“What made this the week to ask?”

What our rep never does

Never makes them repeat what they wrote on the form.

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

The first message, by Email

Illustration

Thanks for your note about scheduling across your plants. I can walk you through how other plant teams set it up, or answer one question first. Which would help more?

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 checks that decide fit, before they run.
  • The call script and the first message, before anyone is contacted.
  • Each meeting, accepted or rejected against the written definition.

You keep

  • The checks file and every verdict with its evidence.
  • The routing rules, in your CRM.
  • Every call note and outcome, written to your CRM with the signal attached.

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

  • Finding nothing is not a pass. A thin lookup goes to a person.
  • A good company with the wrong person on the form is still a good company, with a note to reach someone else.
  • Customers and open deals go to the person who owns them, not to the rep.

How far we run it today.

Built for one company's book-a-call form and running as a pilot: it reads the CRM and writes nothing back yet.

Our services that run it
RevOps, then GTM engineering, then BDR
What it costs
Each service has its own published price. See pricing
The guide behind it
The inbound qualification engine, 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