Great minds think alike

Often, as we add new features to our software, we want to be able to mass edit tickets so that they can be re-classified or have a team that would like to be able to mass assign tickets. It would be great if you could select a group of tickets and then mass edit them to change descriptions, types, owner etc.  ...read more

We want to be able to pull a report of the most frequent inquiries in submitted service tickets.  ...read more

Could I see if someone receive my email in 1to1?   Whe I send and email with hubspot I want to see if the receiver has actually receive it.   Like Whatsapp, I have 1 check when I sent it, 2 check when he received it and double check blue when he saw it. Could we have something like that for the email in HubSpot? ...read more

We would like the Revenue Attribution Report to be able to only display metrics from a particular domain. Similar to what we see in the traffic analytics report.    - Posted on behalf of customer ...read more

Hi guys here is a point to change on your next update   Issue : For the custom object search   HubSpot\Client\Crm\Objects\Api\SearchApi    The method to run a search is called "search()" But for others object from the CRM namespace the function is called doSearch. It's actually an issue because it's not good to have different syntax for the same action in different object and it's a BIG issue for people like writing a beautiful code where we don't need to specifiy which class to use of whatever specific to the object you want to import. All class instantiation are based on a programticly generated class name according to the data scheme i want to import   $result = $hubspot->{strtolower($schema->sdk->namespace)}()->{strtolower($schema->sdk->object)}()->searchApi()->doSearch($searchRequest);   but for custom object it **bleep** because of the method name.   Expected behaviour   HubSpot\Client\Crm\Objects\Api\SearchApi::doSearch()    Change the method name or add an alias to keepcode from people using search() method functionnal.   Reason There is a lack of documentation, developper must use their intuition to code with the sdk, have different name for the same action don't make sens and it's not intuitive. It's a brake on abstract code development   ...read more

Hubspot does not corerctly log inbound emails that have been forwarded by (as oposed to created by) a known CRM contact.   The Hubspot team reply to this question indicates this is by design: https://community.hubspot.com/t5/CRM/inbound-forwarded-email-not-logged-correctly/m-p/342075#M119789    That seems crazy to me - one of my known CRM users deliberately forwards a email message into our Hubspot inbox , but Hubspot will not recognise the know customer who sent it to us, from their known email address,  and Hubspot does not log the incoming forwarded message to the know customer's CRM record.   I need Hubspot to recognise and log all incoming messages from a known CRM contact, regrdless if that message was created by the known CRM contact, or forwarded by the known CRM contant ...read more

With some great integrations in the Marketplace, I have a suggestion to also integrate with the Checkfront Booking platform.  ...read more

Not all items in a sequence are emails and it is super frustrating that I can only to go to emails to enroll a contact in the sequence. The way we use it, I get a task when a contact hits an MQL level score. I do some research on the contact activity to see which sequence I need to enroll them in based on their activity. But I have to go to 3 different tabs to do that rather than just staying in Activity and Tasks. ...read more

In HubSpot you can comment on many things - emails,  notes, meetings, workflows (very helpful) BUT we cannot comment on lists. My team creates lists all the time for different email campaings, internal projects, ect. and while we try to have good, consistent naming conventions things happen and we are left with a list that we don't know why it was created (or forgot why we created).   Being able to create a comment on the list would allow us to add notes like what project the list was for, when it will no longer be needed, ect. This will help keep the list of lists clean as old obsolete list can either be deleted or filed away.   Who: anyone who uses lists Goal: make the admin (and every users) life easier by being able to add a comment (note) on a list to help keep things organized in one platform.     ...read more