fbpx

CIMSNex User Guides

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

The Customer Feedback feature in AMSS provides a platform for capturing valuable insights, suggestions, complaints, and praise from customers. It allows organizations to actively listen to their customers, gather their feedback, and take necessary actions to improve products, services, and overall customer satisfaction. With a user-friendly interface and intuitive fields, the Customer Feedback module simplifies the process of logging, analyzing, and verifying feedback. By leveraging this feature, organizations can strengthen their customer-centric approach, enhance their reputation, and drive continuous improvement. Below is a guide on how to effectively utilize the logging, analysis, and verification fields within the Customer Feedback feature of AMSS: 

Logging Customer Feedback:

  1. Feedback No.: Assign a unique identifier to the feedback for tracking and reference purposes.

  2. Date: Enter the date when the feedback was received.

  3. Time (24Hr): Specify the time of the day when the feedback was logged.

  4. Respondent: Indicate the name or contact information of the person providing the feedback.

  5. Customer Organization: Enter the name or identifier of the organization to which the customer belongs.

  6. Business Service: Specify the specific business service or area to which the feedback relates.

  7. Feedback Type: Select the appropriate type or category of feedback, such as suggestion, complaint, or praise.

  8. Feedback Description: Provide a detailed description of the feedback provided by the customer.

 Analyzing Customer Feedback:

  1. Re-Occurrence: This field captures whether the feedback or issue reported by the customer has occurred multiple times or if it is a one-time occurrence.

  2. Feedback Classification: This field categorizes the type or nature of the customer feedback based on predefined categories or classifications. It helps in organizing and analyzing feedback data effectively.

  3. Correction/Containment: This field specifies the actions taken or measures implemented to correct or contain the issue reported by the customer. It may include troubleshooting steps, problem resolution, or preventive measures.

  4. Additional Description: This field provides space for additional information or details related to the customer feedback, such as specific observations, context, or relevant factors.

  5. AssignedTo: This field indicates the person or team responsible for analyzing and addressing the customer feedback. It assigns accountability for taking appropriate actions.

  6. When: This field captures the date when the analysis or assessment of the customer feedback was conducted. It helps in tracking the timeline and ensuring timely response and resolution.

Verifying and Closing Customer Feedback:

  1. Verification Status: Indicate the status of verification to determine if the feedback has been addressed and resolved.

  2. Completion Date: Enter the date when the verification process for the feedback was completed.

  3. Completed by: Specify the name or identifier of the person responsible for completing the verification process.

  4. Comment/Lesson Learnt: Add any relevant comments or lessons learned during the verification process.

  5. Upload Support Document: Attach any relevant support documents or files related to the feedback, if applicable.

By effectively utilizing the Customer Feedback feature, you can strengthen customer relationships, drive continuous improvement, and enhance overall business performance.

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

IT Service Request Management is a critical process that enables organizations to efficiently handle and fulfill various requests related to IT services and support. It serves as a centralized system for capturing, tracking, and managing user requests, ensuring timely resolution and customer satisfaction. With effective Service Request Management in place, organizations can streamline their IT operations, improve service delivery, and enhance the overall user experience.

Logging a Service Request:

  1. SR ID: This field represents the unique identification number assigned to the service request for tracking and reference purposes.

  2. Request Date: This field captures the date when the service request was initiated or submitted.

  3. Time (24Hr): This field allows the requester to specify the exact time (in 24-hour format) when the service request was made.

  4. Customer Organisation: This field indicates the organization or company name of the customer who made the service request.

  5. Requestor: This field captures the name or contact details of the person who made the service request.

  6. Request Mode: This field represents the method or channel through which the service request was submitted, such as email, phone call, online form, or in-person.

  7. IT Service: This field allows the requester to specify the particular IT service or area of support they are seeking assistance with.

  8. Details: This field provides a space for the requester to provide a detailed description or explanation of the service request, including any relevant information or specific requirements.

  9. Priority: This field indicates the priority level assigned to the service request, which helps in determining the urgency or importance of addressing it. It may be categorized as low, medium, high, or other relevant priority levels. 

  10. Low Priority:

    • Description: Issues or requests that are not time-sensitive and can be addressed when resources are available.
    • Examples: Non-urgent maintenance tasks, minor enhancements, or non-critical inquiries.
  11. Medium Priority:

    • Description: Issues or requests that require attention but are not critical. They should be addressed in a reasonable timeframe.
    • Examples: Standard support requests, moderate system issues, or routine maintenance.
  12. High Priority:

    • Description: Critical issues or requests that need attention and resolution promptly. These typically have a significant impact on operations or services.
    • Examples: Service disruptions affecting a department, critical system errors, or urgent support needs.

       

Analyzing the Service Request:

  1. SR ID: This field represents the unique identifier or reference number assigned to the service request for tracking and identification purposes.

  2. Date: This field captures the date when the service request was submitted or created.

  3. Service Scope: This field defines the extent or boundaries of the service being requested. It specifies what aspects or components of the service are included or excluded.

  4. Service Category: This field categorizes the service request into a specific category or type, such as System Integration

  5. Additional Description: This field allows the requester to provide any additional details or information related to the service request that may be relevant for analysis and resolution.

  6. Resources and Dependencies: This field identifies any specific resources or dependencies required to fulfill the service request. It may include equipment, software, personnel, or any other resources needed to provide the requested service.

  7. Assigned To: This field specifies the person or department responsible for handling or resolving the service request.

  8. When: This field captures the preferred or requested date for the service to be delivered or completed. 

 Verifying and Closing the Service Request:

  1. Resolution: This field describes the actions taken to address or resolve the service request. It may include troubleshooting steps, solutions implemented, or any other relevant details.

  2. Solution: This field provides a summary of the solution or resolution provided to the requester. It may include specific steps, recommendations, or instructions.

  3. Verification Status: This field indicates the status of the verification process to ensure that the service request has been successfully resolved or completed.

  4. Complete: This option confirms that the verification process has been completed and the service request is considered resolved.

  5. Completion Date: This field captures the date when the service request was verified and marked as complete.

  6. Completed By: This field specifies the person or department responsible for conducting the verification and confirming the completion of the service request.

  7. Comment/Lesson Learned: This field allows for additional comments, feedback, or lessons learned from handling the service request. It can be used to provide insights for future improvements or to share any relevant information.

  8. Upload Support Document: This field allows for attaching any supporting documents or files related to the service request, if applicable.

These fields serve as a guideline for logging, analyzing, and verifying service requests in AMSS. You can customize and tailor them to align with your organization's specific requirements and the types of services typically requested by your customers or users.

Image
SIMPLIFYING IMPLEMENTATION OF ISO STANDARDS, providing specialized guidance through reliable Expert Knowledge and Software to help you obtain and maintain your ISO certification.
ISO Compliance Software
Integrate . Mantain . Comply

Search