How to Operationalize Custom Signals in Clay with Salesforce for Better Rep Accountability

Lee V. · 2026-09-23T16:08:51.542Z

We're starting to get beyond enrichment and into custom signals in Clay. We have a few other tools (Factors, 1st party engagement from Hubspot, G2) and I'm trying to figure out how to operationalize all of these so that interrupt signals get owned by a rep and we can track accountability metrics. In the case studies for Clay it looks like some folks are just writing signal data back to fields/properties in the CRM but this feels a little fragile. We're using Salesforce for our CRM so I've been considering Tasks, Campaigns, and/or a custom object so we get that point in time capture each time the signal fires. How are people solving for this? Most of the articles I read tend to gloss over this part and it feels... not obvious

Willy H.
·
·
workflows
Willy H.
·
·
I mean honestly Clay should be able to handle:
Factors, 1st party engagement from Hubspot, G2
But it depends on how you want to operationalize the signals with your sales team.
Willy H.
·
·
like it gets to its destination, so what? what then?
Willy H.
·
·
every org is different so it depends
Lee V.
·
·
I feel like in general the ask is going to be for a rep to take action, but there's also an element of wanting to understand what signals are working which is why I'm considering campaigns/Activity timeline. Ideally, I want to be able to see "New Person meeting criteria was hired" -> Date Stamp somewhere -> Notification to the rep -> Sales Activity after said notification. Slack doesn't really cut it on its own
Lee V.
·
·
I'm tempted to write it back as a task of it's own type at least so we have some pseudo event log and can see all of the 'signals' in one view alongside sales activity, form fills, etc.
Willy H.
·
(edited)·
In my opinion, you don't want signals to become noise. So you definitely want to take the signal, score the signal, make sure that it's something that the rep is going to get excited about, and then after that send it to Slack. And I would disagree with you. Slack does cut it if you have high fidelity type of signals coming through to a rep.
Willy H.
·
(edited)·
Same thing with a task.
Lee V.
·
·
Yea I'm with you on noise. I guess what I mean is we need a structured data point to compare notification to action
Willy H.
·
·
Yeah, the format should be the same, in my opinion. And then you just say where is the signal coming from and why should they call it.
Willy H.
·
·
that why is taste.
Willy H.
·
·
You're only gonna get that from hearing from the sales team, OR the data that suggests "hey, this type of person through firmographics and heuristics closes for our company at a high clip"
Lee V.
·
·
Yea the why makes sense. In my experience, the SLA dictates some action. We can see whether or not the action was taken from reporting. when we see it isn't, we ask the reps and get the anecdotal feedback, follow the data and make adjustments
Lee V.
·
·
Right now, the signal goes through (slack) and the rep actions it (or doesn't) and we never really know if the signals are working or not
Willy H.
·
·
The SLA? What do you mean? When you say service level agreement, how quickly a rep responds?

How to Operationalize Custom Signals in Clay with Salesforce for Better Rep Accountability

23 comments

How to Operationalize Custom Signals in Clay with Salesforce for Better Rep Accountability

23 comments