Recent searches
No recent searches
Organization Hierarchy
Answered
Posted Jun 14, 2023
I'd like to get an idea of how others may have implemented Zendesk amongst their departments/areas. Was a user field, type dropdown list, called department with a list of departments/areas? Or was an organization created for each department and a user field created (Type: Lookup Relationship - Organization) called Department/Areas?
0
7
7 comments
Stephen Belleau
What do you mean by different departments - is it like Support vs IT vs Sales? Do each of the departments use Zendesk as well? Are they agents? If so, I think it's common for each department to have a Group, with an intake process for each. Maybe department A will also create side conversation tickets for department B. That can be done between Groups.
If you're talking about tracking which department various agents belong to - say, for reporting reasons - then a simple user dropdown field makes sense.
Might need some more context to better understand your situation though!
0
Jahn
Tyler Duncan - can you tell us more about your use case please?
As what I have understand it you pretty much want to use Zendesk for all of your departments? For us we actually have 6 departments which also means 5 groups in Zendesk.
1. There are 2 departments/groups which are customer facing
2. 4 departments/groups are for internal communication only (agent to agent)
We are escalating internally via side conversation ticket for us to track down as well the productivity of other groups and report it in Explore.
0
Tyler Duncan
At the moment, each user profile has a user field called department. The department user field is a drop-down list of departments. I want the department field to become an object with properties. I noticed that the same departments listed in the dropdown are also in organization. I want to consider changing the department field to a lookup field, which would be an organization. The lookup field option would be a good option instead of an creating a custom object, seeing as custom objects cannot be referenced to another lookup relationship. By adding organization fields to the organization would help in the development of workflows, user onboarding, and more projects I see that would fit in the functionality with the use of lookup relationship fields.
0
Tyler Duncan
Has anyone come across the use of developing departments using custom objects or organizations?
0
Viktor Osetrov
It seems your use case with developing departments using custom objects or organizations can be related to New Custom Objects EAP. Please follow this link.
Hope it helps
1
Tyler Duncan
@... I am not authorized to view the article.
0
Brett Bowser
Thanks for commenting! The Custom Objects EAP topic is no longer active since we have now launched this functionality. You can find out more in our Custom Objects Resources page which I have linked for you. Let me know if you have any other questions!
1