Add call duration as a field for manual call logs

Upvoted as well, as this is quite essential as to how I wish to use the meeting booking.

I would like this feature. As a workaround, I have made custom properties on the Contact object that allow users to manually log a meeting and duration. These calls are added to a Google sheet via a workflow which I then import at the start of each day as call records linked to the original contact and salesperson.

It’s a little tedious and doesn’t allow us to view call duration as a KPI in real-time. This would all be avoided if manually logged calls could include a call duration property.

I left Salesforce to HubSpot and I am SO incredibly disapointed to discover this frustrating issue which is SO basic and clients have been complaining about for YEARS. Change the duration drop down in Meetings to 1 minute increments (especially for legal purposes where it’s customary to mark time by 6 minutes) and add that SAME duration to the “Log a Call” so you can manually list how long calls are that happen outside of HubSpot. This should be a slam dunk for the dev team. PLEASE?!?!?!?!?!?!?!

I get that it’s extra development but it’s SO basic. HubSpot wants to be the easier system to use for marketing and sales teams. HOW are you unable to report on duration of activities? How do you provide a field for Duration on Meetings but NOT allow it to be pulled into ANY REPORTING?! WHY would you limit your customers from logging manual time for calls? It’s nuts. NUTS. Why won’t you fix this?

Agreed this is a must to help track team call times espcially through 3rd party devices

Please make this happen. I am constantly receiving calls on my mobile from my clients. These calls can range from 1 minute upto an hour or so sometimes. This is a hugely important field to accurately measure the performance of myself and my sales team.

This is a very good idea and would help my sales team to no end. Based on my understanding, it would also be simple to implement

AGREE! @hubspot Can you please give us an update? You have the ability to track time. WHY would you not let us track time (any increments) for ALL activities?

Exactly! This really needs to happen, the underlying code wouldn’t be
difficult to change at all. The database has the capability, the frontend
already exists elsewhere, why not just add it?

It would be great if it were possible to log not only the time but also the duration of a call when logging it manually. This, in conjunction with an evaluation option of the call result in connection with the duration of the call, would make it possible to determine which topics are particularly tying up a lot of resources.

I would find this feature useful, too.

Actually this here is a good way to add duration to a ticket (also call) and then be able to export duration and filter per costumer later: Create calculation and rollup properties

+1

Would love this option as well! Thank you for considering.

Would love to see this, please!

I would like this feature. As a workaround, I have made custom properties on the Contact object that allow users to manually log a meeting and duration. These calls are added to a Google sheet via a workflow which I then import at the start of each day as call records linked to the original contact and salesperson.

It’s a little tedious and doesn’t allow us to view call duration as a KPI in real-time. This would all be avoided if manually logged calls could include a call duration property.

+1 for a customer, as we only currently have an option for meeting duration, but not call duration. Can we get an update from Product if this will be considered in the future?
The customer also created a custom object with a custom property for this and is hoping the +Add association option will default to +Create New instead of +Add existing as well.

Yes, this should be mandatory.

Wow, I cannot believe this is not an option @hubspot, make this happen ASAP. We need to be able to tell the whole story and if my team is getting incoming calls on their cell and can’t log them it’s hard to make decisions.

Just chimming in that this is a required metric for CS.