1 respuesta
I'd say their comment of "not currently possible" probably just meant within the confines of what they're able to offer as part of their Premier services. Depending on how much elbow grease you want to put into it, this would be possible.
Activities use a polymorphic relationship, which makes certain types of customizations difficult. If you can use a formula field to pull down the Lead owner's email address, then you could copy it into a standard email address field on the task (need to do this in order to reference it as an email alert "to" address) then you could write a process builder + email alert to send to that email address when the applicable conditions are met. But I'm not sure if you'll have trouble pulling through the lead owner email due to the polymorphic relationship.
Another idea that comes to mind would be to use a process builder to kick off a headless flow - this gives you more apex-like functionality and access to objects without having to jump right into code writing (which would also make this possible). I'm thinking you should be able to grab the ID of the item the activity is related to, check if it's a lead or not, and if it is a lead then lookup the lead owner's email and send them an email.
Just doing a little brainstorming aloud with those ideas as some possible paths to explore.
