End User Views

Sub Banner

Overview
Keeping it simple is a great strategy, but can be limiting when supporting a sophisticated end-user audience. Break out of Zendesk's fixed and limited set of views, in the same way as you define views as you do for agents, expose different column data in lists and add more view types.

The exposed additional data is legitimately available to the end-user, it's just that there's no mechanism to configure the Web Portals fixed view or to add the fixed view types.

CloudSET Widgets-as-a-Service (WaaS) is a subscription based, dynamically reconfigurable widget run on the CloudSET infrastructure that provides a customizable user interface component, often as replacement for native interface components. It leverages the Zendesk API to get and create data in Zendesk. 

Security is maintained by dynamically generated security tokens to limit the use of the interfaces exposed to only the logged in user.

End-user Experience
A CloudSET widget is used to swap out the normal end-user view content and a with replacement interface component that is painstakingly authentic in its exact look and feel as the original. This extends to the selection of view mechanism and the ability to mouse-over for more detail,  drill down, and to perform the same operations such as adding comments.

 
The difference lies with the ability to expose specifically configured list views, exposing different column data. Depending on auxiliary access control roles, it's also possible to provide a greater range of views.

The ultimate level of empowerment is to grant roles to specific end-users to view aggregations beyond their own organization membership. Examples of use include where organizations are used to represent departments or companies. Company management views that span departments and companies within a group of companies become powerful ways to keep a range of users informed.

Implementation
CloudSET achieves this by getting administrators to use the exiting Zendesk standard view design methods as a first level building block that provides the underlying scope of the view, the column data elements, and the baseline query.

The CloudSET end-user view tool is then used to map replacements for the Zendesk standard fixed views, as well at the ability to define new views. The dedicated configuration tool collates together the underlying first level building block view. It then augments this with the ability to define roles to control who has access to these views. This can be further expanded to define the spanning definition that control the dynamic aggregation scope to return tickets records from more than one organization.

User tagging is used to define the end-user roles. A further configuration tool is used to define the spanning organizations.

As such, it is possible to now configure the richness and scope of the end-user views to help manage your relationship with your customers. This is achievable with the supplied configuration tools and leveraged native capabilities of Zendesk.




  • Overview
  • End-user Experience
  • Implementation

End User Views

Sub Banner

End User Views

Overview
Keeping it simple is a great strategy, but can be limiting when supporting a sophisticated end-user audience. Break out of Zendesk's fixed and limited set of views, in the same way as you define views as you do for agents, expose different column data in lists and add more view types.

The exposed additional data is legitimately available to the end-user, it's just that there's no mechanism to configure the Web Portals fixed view or to add the fixed view types.

CloudSET Widgets-as-a-Service (WaaS) is a subscription based, dynamically reconfigurable widget run on the CloudSET infrastructure that provides a customizable user interface component, often as replacement for native interface components. It leverages the Zendesk API to get and create data in Zendesk. 

Security is maintained by dynamically generated security tokens to limit the use of the interfaces exposed to only the logged in user.

End-user Experience
A CloudSET widget is used to swap out the normal end-user view content and a with replacement interface component that is painstakingly authentic in its exact look and feel as the original. This extends to the selection of view mechanism and the ability to mouse-over for more detail,  drill down, and to perform the same operations such as adding comments.

 
The difference lies with the ability to expose specifically configured list views, exposing different column data. Depending on auxiliary access control roles, it's also possible to provide a greater range of views.

The ultimate level of empowerment is to grant roles to specific end-users to view aggregations beyond their own organization membership. Examples of use include where organizations are used to represent departments or companies. Company management views that span departments and companies within a group of companies become powerful ways to keep a range of users informed.

Implementation
CloudSET achieves this by getting administrators to use the exiting Zendesk standard view design methods as a first level building block that provides the underlying scope of the view, the column data elements, and the baseline query.

The CloudSET end-user view tool is then used to map replacements for the Zendesk standard fixed views, as well at the ability to define new views. The dedicated configuration tool collates together the underlying first level building block view. It then augments this with the ability to define roles to control who has access to these views. This can be further expanded to define the spanning definition that control the dynamic aggregation scope to return tickets records from more than one organization.

User tagging is used to define the end-user roles. A further configuration tool is used to define the spanning organizations.

As such, it is possible to now configure the richness and scope of the end-user views to help manage your relationship with your customers. This is achievable with the supplied configuration tools and leveraged native capabilities of Zendesk.




  • Overview
  • End-user Experience
  • Implementation

End User Views

Sub Banner

Overview
Keeping it simple is a great strategy, but can be limiting when supporting a sophisticated end-user audience. Break out of Zendesk's fixed and limited set of views, in the same way as you define views as you do for agents, expose different column data in lists and add more view types.

The exposed additional data is legitimately available to the end-user, it's just that there's no mechanism to configure the Web Portals fixed view or to add the fixed view types.

CloudSET Widgets-as-a-Service (WaaS) is a subscription based, dynamically reconfigurable widget run on the CloudSET infrastructure that provides a customizable user interface component, often as replacement for native interface components. It leverages the Zendesk API to get and create data in Zendesk. 

Security is maintained by dynamically generated security tokens to limit the use of the interfaces exposed to only the logged in user.

End-user Experience
A CloudSET widget is used to swap out the normal end-user view content and a with replacement interface component that is painstakingly authentic in its exact look and feel as the original. This extends to the selection of view mechanism and the ability to mouse-over for more detail,  drill down, and to perform the same operations such as adding comments.

 
The difference lies with the ability to expose specifically configured list views, exposing different column data. Depending on auxiliary access control roles, it's also possible to provide a greater range of views.

The ultimate level of empowerment is to grant roles to specific end-users to view aggregations beyond their own organization membership. Examples of use include where organizations are used to represent departments or companies. Company management views that span departments and companies within a group of companies become powerful ways to keep a range of users informed.

Implementation
CloudSET achieves this by getting administrators to use the exiting Zendesk standard view design methods as a first level building block that provides the underlying scope of the view, the column data elements, and the baseline query.

The CloudSET end-user view tool is then used to map replacements for the Zendesk standard fixed views, as well at the ability to define new views. The dedicated configuration tool collates together the underlying first level building block view. It then augments this with the ability to define roles to control who has access to these views. This can be further expanded to define the spanning definition that control the dynamic aggregation scope to return tickets records from more than one organization.

User tagging is used to define the end-user roles. A further configuration tool is used to define the spanning organizations.

As such, it is possible to now configure the richness and scope of the end-user views to help manage your relationship with your customers. This is achievable with the supplied configuration tools and leveraged native capabilities of Zendesk.




  • Overview
  • End-user Experience
  • Implementation

End User Views

Sub Banner

End User Views

Overview
Keeping it simple is a great strategy, but can be limiting when supporting a sophisticated end-user audience. Break out of Zendesk's fixed and limited set of views, in the same way as you define views as you do for agents, expose different column data in lists and add more view types.

The exposed additional data is legitimately available to the end-user, it's just that there's no mechanism to configure the Web Portals fixed view or to add the fixed view types.

CloudSET Widgets-as-a-Service (WaaS) is a subscription based, dynamically reconfigurable widget run on the CloudSET infrastructure that provides a customizable user interface component, often as replacement for native interface components. It leverages the Zendesk API to get and create data in Zendesk. 

Security is maintained by dynamically generated security tokens to limit the use of the interfaces exposed to only the logged in user.

End-user Experience
A CloudSET widget is used to swap out the normal end-user view content and a with replacement interface component that is painstakingly authentic in its exact look and feel as the original. This extends to the selection of view mechanism and the ability to mouse-over for more detail,  drill down, and to perform the same operations such as adding comments.

 
The difference lies with the ability to expose specifically configured list views, exposing different column data. Depending on auxiliary access control roles, it's also possible to provide a greater range of views.

The ultimate level of empowerment is to grant roles to specific end-users to view aggregations beyond their own organization membership. Examples of use include where organizations are used to represent departments or companies. Company management views that span departments and companies within a group of companies become powerful ways to keep a range of users informed.

Implementation
CloudSET achieves this by getting administrators to use the exiting Zendesk standard view design methods as a first level building block that provides the underlying scope of the view, the column data elements, and the baseline query.

The CloudSET end-user view tool is then used to map replacements for the Zendesk standard fixed views, as well at the ability to define new views. The dedicated configuration tool collates together the underlying first level building block view. It then augments this with the ability to define roles to control who has access to these views. This can be further expanded to define the spanning definition that control the dynamic aggregation scope to return tickets records from more than one organization.

User tagging is used to define the end-user roles. A further configuration tool is used to define the spanning organizations.

As such, it is possible to now configure the richness and scope of the end-user views to help manage your relationship with your customers. This is achievable with the supplied configuration tools and leveraged native capabilities of Zendesk.




  • Overview
  • End-user Experience
  • Implementation