Lee V.

Both and it was helpful to separate the two (mentally if nothing else). Had a couple of other conversations on the topic today/yesterday and leaning towards a database for logging all the relevant activity but putting some checks in place to make sure the only signals that make it through to a rep are high value/ICP/immediately actionable. Feels like the database/event log options positions us for both, but also like it's a lower priority than getting meaningful, non-noise signals in front of the reps

Yea! If you're up for it

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

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

Yea I'm with you on noise. I guess what I mean is we need a structured data point to compare notification to action

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.

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