CharlieFellenbaum

I guess it's about time for my yearly update on this fabulously good idea. And hopefully this week I will also send a note to our ZD Account Manager to see if we can get traction and/or action there.

To spec it out further, stating our business needs, and why: We misspelled a customer's name and if I merely correct it, it creates a whole new organization. We have at least one other situation where a customer subaccount should Not have been given its own ZD Organization, so now it exists independently in the system. If I could merge them completely, their information would all be back together in one place where they should be. These may be self-caused issues, but the reason doesn't really matter. I saw others post that if one of their customers buys or otherwise merges with another, then they too are stuck in ZD separately. How annoying !

For us, this need is driven in large part by GoodData reporting, not just convenience. Once I pull a spreadsheet, I have to go in and manually merge data from two accounts and that is a drag and creates another opportunity for error, especially if someone else unfamiliar with the situation was asked to do this (new employee?).

Yes, even closed tickets should be brought along in a merge account action. If we cannot do it ourselves as Administrators, can ZenDesk do it for us?

I believe this topic is more important to more people than this conversation thread may indicate.

Charlie Fellenbaum

September 03, 2013 11:45

Adding my 2 cents also for support for this 'merge' feature/ability. Sad to see the date of this original request, very well stated, was 2 years ago. My workaround for now is to rename an organization, but if the system would allow it cleanly, then reporting would not be split between two names and 'corrupted.'