Hi JCrowe,
Since writing this i’ve learned a great deal about the reasons why this happens and should really write an update to the original post to include some of those details.
One thing that I’ve dug into extensively was the use of the HubSpot Chrome Extenstion for Gmail. If you or your users are using this, this can cause a rediculous amount of problems when the Default associations config includes “Tickets”.
How this little gem of a feature works is not really something that makes any sense to me really.
In sort, if you are using HubSpot sales extension for Gmail/chrome AND you have the default associations set to include “Tickets” and your users are sending and replying from email out of Gmail…you are likely pulling your hair out trying to understand the endless mess of cross associations.
Here is a quote from the extensive support ticket that I logged about the behavior of this “Feature”…
"
For some reason, the HubSpot Sales Chrome Extension has 2 major issues
When replying to a message that is associated with a ticket, and default associations include tickets,
- it is unable detect or preserve the existing association with the ticket that initiated the thread in the first place
- It selects a series of unrelated tickets that include tickets that are old, closed and are completely unrelated in any way other than they they include the same company contact and sending contact."
"
Having continued the conversation for some time it was explained that the auto-association function that is present in the chrome extension is different from how it is done in the CRM. This appears to be the case with the Outlook extension as well. I.e it behaves different than the auto association that exists in HubSpot CRM and it is also different from Chrome extension as well.
I late found out that the issue described in #2 above does not attempt to associate the email reply with the ticket that originated the thread. What it actually does when auto association of tickets is enabled is that it automatically associates the conversation with the first 3 tickets that exist for the first contact in the two line. It does this regardless of whether the ticket is 5 years old and closed or whether it was opened 10 minutes ago.
The response I received from HS goes like this…
“The auto-association behavior between sending emails in the CRM records page and sending emails in the extension is different. It is WAD that those three tickets are automatically selected as they are all associated to the recipient. That being said, we are actively working on aligning the association behavior between the CRM and extension, which hopefully will help make it less confusing.”
WAD for those who don’t recognize the accronym is “Working as Designed”…
In my opinion, if this is working as designed…then the design is broken. No one who has ever had to work in an organization with a service ticket system would ever have designed something like this.
As mentioned in the comments above, the behavior of CRM mail auto association is different than what occurs within the sales extension that is external to the app.
In my experience simpler is better
- If you have a support team or CS team using HubSpot ticketing…choose an interface and stick with that interface to interact with the customer.
- Email: I generally recommend people send and receive email from the ticket interface in CRM or the HubSpot inbox. This can be difficult with mobile users and different people in different roles with different working preferences.
- If your users insist on using the Gmail or the chrome sales extension, advise them to not select the Tickets in the default association section of the extension configuration.
This will result in the email being associated with the contacts and the company but not the ticket. This is not ideal and it does create addtional work in that it would still require manual association of the ticket to make sure it gets associated with the correct ticket. However, it does eliminate the havoc caused by the cross association of multiple email and the apparent random reopening of ancient completely unrelated tickets.
At the end of the day, sending, receiving and replying to email from within the ticket is still the most consistent option in my opinion for keeping the email thread, ticket, contacts, and company together as they should be.
Thankfully there is a global setting for this that can be set at a company level that will override the end user settings for the sales extension.