Skip to main content

When company is changed for a contact, old company name persists in existing tickets


When I change/remove the company for a contact ( usually to correct a mistake ) the previous company name is still displayed in existing tickets and ticket lists and not replaced by the new one.

Did this topic help you find an answer to your question?
This topic has been closed for comments

11 replies

  • Community Debut
  • 7 replies
  • November 3, 2016

I too found a duplicate company name. I changed the company name for the contact and then attempted to update each ticket created with the incorrect company name to the correct company name which I could not do.


I had hoped to update the tickets then delete the incorrect company name from Freshdesk to prevent future entries.


I'm also not sure what the results will be if I change the incorrect company to zzDoNotUse... Any insights or work arounds to this would be appreciated.


  • Author
  • Contributor
  • 176 replies
  • November 9, 2016
I see that this issue still persists.

 


sukanya.arunachalam
Top Contributor
Forum|alt.badge.img+1


Hi Everyone, 


This is more of a behavioural change rather an issue considering a few scenarios like a customer being moved to a different/new concern or a reseller working for different companies at a time. Hence, only tickets created after the change will be mapped to the new company records whilst the old records will remain the same for reporting purposes.



Regards,

Sukanya


  • Author
  • Contributor
  • 176 replies
  • November 16, 2016
Dear Sukanya,

I see the reasoning behind this decision and it makes sense.
However, I would still appreciate having a way to correct a mistaken assignment of a ticket to a particular company.

 


  • Community Debut
  • 1 reply
  • February 22, 2017

There needs to still be a way to move tickets from one Company to another.  If a company was entered or imported twice with a slightly different name and tickets created under both, there should be a way to merge the tickets from one company into another. 


  • Apprentice
  • 2 replies
  • June 22, 2017

I understand the logic, but it's incorrect because if the ticket was assigned to the wrong company, then the reporting for that company will be wrong since it has bad data. Also this is bad UX. It doesn't give the users ( us ) a way to rectify mistakes. 

I would really appreciate this be rectified and not simply ignored.


  • Contributor
  • 113 replies
  • June 23, 2017

This needs to be broken out very clearly in the Customers tab user interface.


I haven't dug into this to see how it works presently, but the area should be very well handled for Freshdesk to be comfortable with how it works, in my opinion. Merging companies when a duplicate company is created; a person who works (simultaneously or serially) at different companies; merging a duplicate person into one person at one company; changing which person or person-at-what-company is associated with one or many tickets; etc.


  • Community Debut
  • 1 reply
  • October 15, 2018

This is still not handled well.

We MUST be able to change the associated contacts or Customer for any ticket.


As a workaround, I edited the ticket and assigned it to myself, then reassigned to the contact. It now shows current Company info and all is well.


  • Community Debut
  • 2 replies
  • December 14, 2018

 I'm adding my "vote" that us Admins need a way to be able to bulk update tickets so they can be moved from one company to another.  As previously mentioned, there is a use case for correcting mistakes.  One could argue a use case is for when businesses merge and a new company is formed.  The newly formed company would prefer to have all their historical tickets in one combined list.


  • Community Debut
  • 2 replies
  • October 22, 2019

I agree with Patrick Carroll. I would really like to be able to do bulk changes on tickets to move them from on company to another mostly to correct our own mistakes.


  • Community Debut
  • 2 replies
  • May 18, 2020

we would also really like this to correct mistakes without it impacting our reporting