1 of 1 people found this helpful
Hey Rachel, in cases like these, we subscribe to a smart list. We come up with this specifically when there's a large volume of email alerts—an overwhelming amount that should be consolidated.
This happens with exception reports, where we have large volumes that might be landing in exception reports to the point that the noise drowns out the individual value of each email alert.
Here's an example of a smart list subscription email regarding people who haven't successfully synced to SFDC in the last week:
Here's an example where the smart actually has members (in this case, for persons who didn't have a proper Lead Source value):
The "Download Report" button in that email is accessible outside of a Marketo login, so the person with the link doesn't need access to Marketo, and that link expires after a certain amount of time (4 days).
You just make the smart list in Marketo, such as this one, but obviously targeting the persons who you want to be included:
List Actions > New Smart List Subscription
Then you can set up the specifics of the subscription in the modal that pops up:
Here's a link to the documentation for smart list subscriptions: Subscribe to a Smart List - Marketo Docs - Product Docs
In the case of targeting, you can do a smart list of something like: (1) attended webinar and (2) lead owner was [lead owner name]:
That'd have to mean you'd have as many of these for as many of your interested sales owners, though, and the scalability of that depends on your sales team size and turnover.
Edward Unthank | Founder, Etumos
Ed's solution is right.
But on a wider level, why do you want to immediately flag these people to Sales? Shouldn't you do this based on MQL (scoring) criteria? attending a webinar does not mean leads want to buy (or hear from sales) right now. I see a lot of firms do this and it just seems like it's jumping the gun.
Josh, I totally agree that someone who attends a webinar isn't necessarily ready to speak with sales and we don't want to immediately flag people to Sales. For this use case, it's just people who are already owned by a seller in SFDC. If they haven't reached the MQL threshold or are in "Recycle" or "Will never buy" we wouldn't include them in the list.
I create SFDC campaigns with people who are already owned in SFDC so that sellers can go there to view their leads, but they keep requesting separate lists.
Thanks Edward! I think this is the solution I'm leaning towards, although you're right in that it's not scalable. I might do it by regions so that I just have however many regions, then the report can go to either that lead, or the regional sales alias.