How to Structure End Users |
|
In Revelation Helpdesk there are two distinct groups of users – you and them. You are the support staff who will be distributing and acting on new tickets and they are the end users who will be the cause of new tickets. However, as we have seen above – the ‘end user’ may not necessarily be a person.
Above an end user there are three levels of hierarchy that look like this:
Client Type is a text name of up to [max #?] characters. When you create a client you must associate it with a client type so if you are not going to be using this feature you will need to create at least one as a default (you can even call it default J).
NOTE: You can filter the clients that a staff person can see when logging new tickets by client type.
Client is a text name (long), a text name (short – 15 characters), and a client type. You can attach documents to a client as well as a description.
Location is a far more complex entity. A location not only has a name but it is associated directly with a client. A location also has a physical address.
End User is configured to be a person. An end user is associated with a location and as a result, a client and a client type.
As you decide how to organize your end users in Revelation consider these questions:
Here are some common end user structures that are easily configured in Revelation Helpdesk.
School District
IT Support Company
Internal IT Department
Software Company
Nationwide Trucking Company