Make Call Outcome required

[bfelker]

 Today call outcome and call type are optional fields for someone who is logging an activity. I need to make them mandatory so that a rep cannot log an activity without populating those 2 fields. How do I do it?

[bfelker]

Hi @AFD, @NKolev @HubspotterOHIO ! Thanks for your patience as we corrected this. The ability to require call outcomes for manually logged calls is restored. Let us know if you have any questions/feedback. Thank you! 

[bfelker]

Hi @NKolev and @HubspotterOHIO ! I just reached out in a seperate email to grab examples from you. The build for this does solve for manually logged calls and outbound calls. This worked in testing portals before we launched, so I would love to chat you briefly to see what is occuring and escalate to my engineering team from there. Thank you!

[bfelker]

Hi HubSpot Community!

We are excited to announce we launched the ability to make call outcomes required!

Once this setting is enabled, when seated reps in your account place an outbound call from the HubSpot browser or log a call, the ability to save the call will be greyed out until they select a call outcome.

To enable this feature:

1. Admins, Navigate to the Settings icon in the top right corner of your screen.

2. On the far left menu panel, scroll down to the Tools section. Click "Calling."

3. On the Calling page, click the "Call Configurations" tab.

4. Click the check box next to "Make call outcome required."

5. Click Save.

*This setting is currently for outbound calls placed from the HubSpot browser or logged calls. This functionality does not require call outcome logging for inbound calls, mobile calls, or imported calls.

[bfelker]

Hi Community!

We appreciate all the feedback you’ve shared here to help our team evaluate this feature request. However, at this time, making call outcome selection required is not something our team is currently planning to build natively into HubSpot. This is certainly subject to change in the future and we will update this idea if that becomes the case. 

As we progress in our current Calling priorities we will update here with more details on timing and plans. 

[bfelker]

Hello HubSpot community,

Thank you for your continued feedback.

Allowing call outcomes and types to be required is on our list of things we’d like to do. However, the list of calling improvements is long and resources are limited. At the moment this is a lower priority compared to some of the other things we’re working on. We're continuing to keep an eye on this use case and we'll be sure to update this thread when this is a more near-term deliverable.

[bfelker]

We're currently evaluating this enhancement  and will update this issue with more information in the next few months.

[ARich]

When HubSpot doesn't listen to its users that makes it difficult to justify going to bat for the product when executives start looking at alternatives. Your users expect to see improvements to the existing product, not just new offerings that you charge more for. This is a simple fix that could be accomplished in any sprint. Why not get your Product and Development teams to listen to your users rather than flat out ignoring them? 

[Ceridwen1971]

Our reps are unable to follow process, so we are in desperate need to have these fields be required. This is preventing us from creating additional automatic workflows including feedback loops, follow up emails, etc. Because these are the optimal triggers.

[Hail]

What are the calling priorities that are being upvoted and put ahead of this request?

I wouldn't even call it a calling item. It is just a required field selection that is in place in other areas.

[aidentech]

+1 - This is a MUST HAVE!

[AFD]

Great Idea - we would find that veyr helpful (our previous CRM had this ability which really helped with consitent reporting amongst the team as everyone had to fill in the fields). It would be great if you could add this HubSpot! Thanks.

[JScott88]

Yes, we need to be able to make call outcome mandatory. 

[luke-moagency]

I'm having to do some fancy footwork to land a 110 seat HubSpot Enterprise deal. The client is leaning toward Salesloft as they have this functionality! Even though HubSpot is better on the whole for their requirements! Please fix this HS product team! 

[MHolzer]

Idea/Workaround:

Only works if every Call needs a Calloutcome:

Make a Workflow (Contact + Company) that creates a Task and assigns it to the individual Sales Rep when a Call outcome is unknown. 

Could be problematic finding the right owner if more people work on the same contact/company; or if the Owner is not equal to the one calling on the contact. -> Shared Task queue could be the solution then (or implementing a Hubspot User category for this workflow particular.

[CGrilo]

This is very important for us as well, Also the meeting types.

[AS_Girikon]

This is very important feature for one of our partner, I hope this will be rolled out soon. Meeting Types & Outcome

[ALandes]

We would very much appriciate the "Outcome" and optionally the "Type" to be a mandatory field for calls. So that we can drow up reports on this basis.

[SHall]

Hi HubSpot Community!

We are excited to announce we launched the ability to make call outcomes required!

Once this setting is enabled, when seated reps in your account place an outbound call from the HubSpot browser or log a call, the ability to save the call will be greyed out until they select a call outcome.

To enable this feature:

1. Admins, Navigate to the Settings icon in the top right corner of your screen.

2. On the far left menu panel, scroll down to the Tools section. Click "Calling."

3. On the Calling page, click the "Call Configurations" tab.

4. Click the check box next to "Make call outcome required."

5. Click Save.

*This setting is currently for outbound calls placed from the HubSpot browser or logged calls. This functionality does not require call outcome logging for inbound calls, mobile calls, or imported calls.

[Bareld]

Excellent thank you!

[ALandes]

Lovely, thanks a lot!

Already activated this new feature.

[HubspotterOHIO]

THANK YOU!!!!!!!!!!!!! I have checked the box!!!

[AFD]

Thank you!

[NKolev]

@SHall Just to let you know that it does NOT work for logged calls. I've checked with support and they've advised me that the internal documentation noted that it won't work for logged calls. But on all external documentation, it is noted wrongly that it applies to logged calls as well.

I've submitted it as a new idea here.

[HubspotterOHIO]

I saw that late yesterday that it does not work for logged calls!!!

[SHall]

Hi @NKolev and @HubspotterOHIO ! I just reached out in a seperate email to grab examples from you. The build for this does solve for manually logged calls and outbound calls. This worked in testing portals before we launched, so I would love to chat you briefly to see what is occuring and escalate to my engineering team from there. Thank you!

[AFD]

Hi @SHall I am also finding that it doesn't work for manually logged calls...