Posts: 3
Threads: 2
Joined: May 2010
i am a final year computer science student,i need help in writing my project i need the design and analysis stage,problems of the manual system,systems flowchart,source codes.i will really appreciate if i can get a response as soon as possible
Posts: 1,149
Threads: 370
Joined: Jun 2010
22-09-2010, 09:09 AM
Abstract
An organization’s customers may have complaints about its products. They will be given an email id for each product, where they can send an email when they have a complaint to register. The emails will get converted to complaints and get assigned to the persons handling that product. The complaints can be assigned to different persons and will get tracked to closure. The person handling the complaint will have the facility to communicate with the customer via emails through the system.
Functional components of the project
Every product will have an email id assigned to it. Customers, when they have a complaint about the product, will send an email to the email id provided to them for that product.
These Emails should get logged into the database and a complaint number should be generated. The customer should get an acknowledgement back saying that his/her complaint is received.
Administrators will be set up for each product and he/she should see all the complaints received for that product.
Groups of complaint handling executives should be set up for each product.
The administrator for a product should be able to assign the complaints to specific members of the complaint handling team for that product.
The complaint management team member should see the complaints assigned to him/her in his inbox. He should be able to send mail to the customer through the system with any clarification/solution or asking for more information.
These subsequent communications should be stored as a part of the same complaint.
The complaint should show all the communication that happened between the customer and the organization.
A complaint can be closed with some pre defined statuses like: Open, Closed, Abandoned, In-progress, etc.
Reference information should be maintained in the system like complaint management team for different products, mail ids for different products, default mail texts for products, default mail subjects for products, list of users, list of products
Posts: 2,300
Threads: 878
Joined: Sep 2010
[attachment=6942]
Industrial Training Report On
COMPLAINT MANAGEMENT SYSTEM
Submitted by
MOHITA CHALIA
Roll No. 61000810117
PREFACE
An effective complaints management system is integral to providing quality customer service. It helps to measure customer satisfaction and is a useful source of information and feedback for improving services. Often customers are the first to identify when things are not working properly.
The project tries to accomplish all the following features:
1) Smooth flow of data without any hurdles.
2) Adequate validation checks for data entry.
3) Adequate security of data.
4) Facility to update data from time to time.
5) Prompt and specific retrieval of data.
6) Flexibility in the system according to the changing environment.
7) Controlling redundancy in storing the same data multiple times.
8) Accuracy, timeliness and comprehensiveness of the system output.
9) Stability and operability by people of average intelligence.
10) Enhancement in the completion of work within the constraints of time
The scope of the system is quite wide. It can be implemented on a WAP-enabled mobile handset, thus providing the Customers and the Providers, the ease of accessing the projects and their status without any difficulty and within no time.
