Custom events in prospecting agent
Tuesday, November 17, 2026
What it is
Custom events track activity unique to your business, like attendance at an in-person event. The Prospecting Agent can now use them to recommend contacts, set outreach cadence and create outreach content.
Why it matters
You get more choice over which events and signals drive the agent, including signals from external apps, so you can build more customized workflows. Smart CRM and Revenue Hub get it on Professional and Enterprise only.
The Take
Imagine if they could understand every signal that was happening at the event all at the same time on the floor.
Per the panel, Custom events in prospecting agent lets you enable the Prospecting Agent to use the custom events you have created to recommend contacts, set outreach cadence and create outreach content. Custom events let you define and track activity unique to your business, like attendance at an in-person event. It is live on Starter, Professional and Enterprise, and on Smart CRM and Revenue Hub for Professional and Enterprise only. The point of the Why text: you get more options for which events and signals power the agent, and you can link signals from external applications and build more customized workloads.
Chris raised this one first on purpose, out of order, because he wanted to take the two prospecting agent updates as a pair. His framing: signals are a type of event, so it makes sense that the two are linked. The difference he drew is intention. Custom events are things you create in your portal "with intention to make space for data and context that we know will be happening, that we're often in control of, or we understand the process behind." That leans into the inbound side: the email came in, the thing happened on the website, so what does it mean for the business, and let's add metadata next to it so it is documented. Custom signals sit beside them as the cues you cannot control the timing or source of. Casey read the Why, including the part about external applications.
His working concern is the agent knowing the difference. "Who said what when becomes very important as to what the rules of the game are and what's documented and what's in stone, what's not." If you have events and signals with a similar set of data on them, one that came in organically and one your team created while importing an event list, the agent has to understand the weight and the difference between them, and he said he would be interested to see how that plays out. His picture of why it can be worth it: a salesperson at a trade show can only understand what is within earshot. "Imagine if they could understand every signal that was happening at the event all at the same time on the floor. Right? And what happened yesterday." The same caveat from the signals conversation applies here, which is Casey's: this is not the same as scoring, so design the events for the agent and do not reuse the setup you built for Lead Scoring.
What to do: if you are on Starter or above, or Smart CRM or Revenue Hub on Professional or Enterprise, and you already track custom events, such as event attendance, look at which ones carry real meaning for outreach and put the metadata next to them before you let the agent read them. If you have none, creating them is the first piece of work. If you do not use the Prospecting Agent, skip this one.
Watch Us Discuss This
The full segment from the show, us working through this update start to finish.
Produced by Value-First Media

