After the launch of the web application, we got notified about 2-fold improvement in the efficiency of the customer support department. The successfully released final product helped to decrease the number of customers’ emails by 84% and the number of calls up to 91%.
Users, roles, and permissions are defined in database tables. Avoiding hard-coded definitions of roles and permissions provides a wide flexibility in the future.
The permissions table has basic CRUD permissions for each model.
Roles determine what users can access. Although there are only two currently existing roles, further development may involve the bigger number of roles.
The Customer Portal is designed with the end-user in mind. The primary users are enterprise customers. When using the platform, customers have:
The customer portal is organized into these modules
Provides customers with a snapshot of current activity. All references to the projects or service cases link directly to their detail page
The product database that is accessible by both – the customer and the company. The company’s service department can use this to help locate equipment and determine the warranty status
The product database which is available for both – the customer and the company. The company’s service department can use this to help locate equipment and determine the warranty status
Allows customer to browse all their projects and project details:
Users can browse all their service. Like the project module, the client can view basic information and the Сustomer Portal team working on the service. The customer can track the status of a case
Users can browse all their service. Like the project module, the client can view basic information and the Сustomer Portal team working on the service. The customer can track the status of a case