Add "Type" constraint to "Activity was Logged" filter

[Anonymous]

We need our activity-related smart lists to be able to differentiate between a call attempt and a call connect based on the value the salesperson enters in the Task Type field (e.g. "Call" for an attempt and "Call Connect" if an actual conversation occurs).  Having "Type" available as a constraint in the Activity was Logged filter would enable us to do this.

[Anonymous]

Thanks Elliott Lowe​.  We will take a closer look at this feature request as well as merge the ideas together to move this up into the Top 10 ideas section. 

[Grégoire_Miche2]

We need Type AND record type.

-Greg

[Anonymous]

Update on merging the ideas which would bump this idea to top 10? Or even better, is this on the roadmap for 2017?

[Anonymous]

Are there any product or roadmap considerations for this yet?

[Debi_Richter]

We need "task record type" - please.

[Anonymous]

We need Record Type as well as Task Type.  Task type is a sfdc standard field on a task. 

Here are just a few examples of what we use

Activity type for trade show interactions - meeting

Activity type for a sales person to visit customer site to provide product training – face to face visit

Activity type for a phone call - phone

Activity type for email - email (this one is covered- thank you! )

Activity type for webinar - webinar

I know I can create interesting moments, however the problem is that I need to report on tasks only. Using interesting moments would actually make the problem worse.  It takes too long to be able to join multiple tables to get the analysis I need.  I need to report on how effective sales and marketing efforts are in closing a customer.  This data helps managers coach sales and marketing, and gives us insight on direction we need to take in the future. 

This is my current work around: I create tasks which include notes from trade show scans.  The create task in flow doesn’t allow me to specify type.  Then I run a report in SFDC, export it, update the csv file and then use the data loader to update task type. Annoying Alert - this isn't really automated is it?  Please add this feature!!!  This would take me 5 seconds to do in Marketo, but instead takes 1/2 hour or more depending on how many records.  I do this quite frequently, so this extra time for every program with create task in flow adds up to wasting a lot of time.

[Anonymous]

Yes, need Type as a Constraint, so we can align Sales / Marketing lead lifecycles across Salesloft, SF, Marketo.

[Anonymous]

A less ideal workaround is to create a workflow rule in SFDC that populates the task subject to begin with the task type. So in marketo you can filter off of the activity subject "begins with" to mimic the taks type constraint.

[Roy_Hegger1]

Its been far too long - please add this!

[Anonymous]

can we have an update if this will be ever delivered? Because this is such a pain!