INTRODUCTION OF THE CUSTOMER COMPLAINTS MANAGEMENT

Are you looking for customer complaints management for your final year project? We are here to help you. You can contact us 

Working with any company or organisation or any other group. There is always a small gap between perfect system and the worker or any other user. They might have some problem with the system or against any person or with the whole system.

So there must be some system which could make it easy register their problem with the system which could be transferred to the particular person who can resolve this issue.

The token of the complaint is generated with can be seen by the complainer and the claim is decided to transfer it from here to given department. The claim has a grace period and makes it clear to fill the problem get the expected resolving date.

Now here we come up with notice interface where the resolver gets the scope of the problem and give notices to concerned person to do the particular task. Then the person takes the action and notifies him as all are registered to the system.

In this manager, the complaint pass through a hierarchy and one after another the problems get resolved.

MODULES OF THE CUSTOMER COMPLAINTS MANAGEMENT

The module of the customer complaints management is made of the combination of modules which work with collaboration with each other and make it beneficial to accomplish the main aim of the scheme.

Complaint:

This interface is made for the users who want to make a complaint against some person or some problem they are facing and to get rid of it.

The interface allows them to give them a description of the problem, that is when they were facing the problem where it was . the name of the person responsible for that and here space for describing it properly is given.

Notice:

This interface is critical regarding making the person aware of the problem and notice to the individual if the responsible person is the part of the organisation.

Here the staff have the option to sent notice after or during to resolving of problemo complaint of the users. Here users also get notice of the problem solved status.

Staff:

This interface is mainly for the staff of the organisation working under different conditions of the department and try to resolve the problem after getting assigned over that according to the problem.

The person is responsible for giving notice to the responsible of the problem and notifying the user about the problem status of resolving. Further, they are capable of giving enough reasons about it.

Registration:

Users information have to be compelled to be registered within the system thus on the establish every of them unambiguously and do the required group action as real potential .like on the name of the bill is issued.

on the far side, this plenty of things require measure there wherever we will reference him. Without registration, there are few options and pages one user can see which are landing on the home page and taking the features read but he won’t be allowed to use those.

For use, he will have to register. One person needs to put his all the details correctly and precisely as it will be helpful in identifying them and believing that he is the real person who has booked for the same.

It also includes driver license for them who is driving and parameter too.

Login:

After registration one will register within the system because the operator of the system either on the behalf of user. when this he has the opposite helpful interfaces accessible for any actions.

Here either bride or groom both have to log in with their unique identity and passwords. After this, they will be directed to the primary user interface from where they have further options.

Forgot password:

This is quite often that people tend to forget the password they keep for the login. So this could be very tedious and hectic to recover the password manually in case if one needs to login in the emergency.

So to overcome this problem we have this module named ass forgot the password and using this module user can recover their password in seconds. So here we need to only put our registered email Id and hit the enter.

then one confirmation email will go to the email where he has the option to reset the password. In seconds one can use this module and get rid of forgetting password problem.

Admin:

Admin has the official powers to control the flow of the data from one part of the system to the other. He can manipulate the access of the users to the data.

The primary purpose of this account is to make the user data relevant and then giving the inputs to the other an interface module and make it work optimistically and get the timetable according to the wish we want to create for a particular type, of inputs.

Hence all the data will be reflected in clean and well data in the interfaces.

SYSTEM REQUIREMENT OF THE CUSTOMER COMPLAINTS MANAGEMENT

Now, this method is intended in such the way that it takes fewer resources to figure out work correctly. it’s its own type of minimum needs that we’d like to require care of :

The system wants a minimum of two GB of ram to run all the options sleek and unforeseen.

It wants a minimum 1.3 gigahertz processor to run sleek as else which will produce issues.

The system must be operated by some approved person as wrong hands will build it happy-go-lucky.

Rest is all up to the user’s usage can take care of hardware

For security opposing anti-virus is suggested.

The system is made correctly, and all the testing is done as per the requirements. So, the rest of the things depend on the user, and no one can harm the data or the software if the proper care is done.

All the attributes are working correctly, and if any error is found, then it can be removed easily.

SYSTEM DESIGN OF THE CUSTOMER COMPLAINTS MANAGEMENT

 

SYSTEM DESIGN OF THE CUSTOMER COMPLAINTS MANAGEMENT

 

Entity Complaint :

The main complaint is written in this feature of the scheme.

Expected Resolve date:

The time till what it will be resolved is written here.

Status:

The status of it I .e. is it cleared or not.

Foreign Key Problem_id:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number. This used to uniquely identify every table in the database and perform the crud operation on it.

It is used to reference that table to any other table or any interface to show the data of it and support other entities.

Entity Problem:

The user describes the problem context.

Primary Key Problem_id:

This is system generated and unique, which can be referenced in any other entity.

Place of the problem:

Where mainly the problem is faced is given here.

Category:

The type of the problem to which belongs according to the severity.

Time:

The time at which it was faced.

Description:

Reason and any other thing about the problem needed are given in brief description about it on the facts.

Entity Staff:

Officers of the department are here.

Primary Key Staff_id:

This is system generated and unique, which can be referenced in any other entity.

Staff name:

The team name is taken from the user and fed into this it is properly validated so that no mistake happens.

Qualification:

The requirement is made as to filter the events according to this so that user does not need to filter out the events to register it makes this system more reliable and useful.

Number:

The phone number is taken here to keep the member updated and for the confirmation of the event is also managed through this method.

Email:

email is made to make member aware of new offers new events and for future reference, it is also relevant.

Type:

The kind of user is mentioned here like is he a student, teacher or he is the vendor of any shop. According to this data, the discounts offers and other things are decided plus few other things of adjusting the task of the user also with this.

Address:

The location of the user is also mentioned here to make it accessible to the delivery and few other things too.

Foreign Key Department_id:

It is used to reference that table to any other table or any interface to show the data of it and support other entities.It references the department which the user belongs.

Entity Notice:

Primary Key Notice_id:

This is system generated and unique, which can be referenced in any other entity.

Name:

Name of the Notice or we can say the title.

Issue date:

When the notice is published, the time stamp is given here.

Foreign key Complaint_id:

The complaint Id is referenced here.

Status:

The status of the complaint is it resolved or pending or in progress.

Action:

The necessary measures needed to be taken written in this.

Description:

Any other reason about the problem is fed in this attribute

EntityUser:-

User data have to be saved in this entity, and all fields are required for this purpose which taken from the user .proper validation is checked, and the attributes are as follows:

Primary KeyUser_id:

This is system generated and unique, which can be referenced in any other entity.

Username:

Username is taken from the user and fed into this it is properly validated so that no mistake happens.

Qualification:

The requirement is made as to filter the events according to this so that user does not need to filter out the events to register it makes this system more reliable and useful.

Number:

The phone number is taken here to keep the member updated and for the confirmation of the event is also managed through this method.

Email:

email is made to make member aware of new offers new events and for future reference, it is also relevant.

Type:

The kind of user is mentioned here like is he a student, teacher or he is the vendor of any shop. According to this data, the discounts offers and other things are decided plus few other things of adjusting the task of the user also with this.

Address:

The location of the user is also mentioned here to make it accessible to the delivery and few other things too.

Entity Admin:

Primary key admin:

This is primary supervisor of all task happening in the system for long. It is system generated unique identity number. This used to uniquely identify every table in the database and perform the crud operation on it.

It is used to reference that table to any other table or any interface to show the data of it and support other entities. It has all the power to make changes in the field of other tables.

It grants the privileges to other users of the system that what kind of operations they can perform.

Logs:

The logs are saved here to analyse the system accordingly. The changes occur. For necessary changes.

Password:

A Strong password is recommended for this account as no one wants to get hacked and lose the sophisticated data.

Description:

Any relevant info. Regarding this statement is attributed in this.

CASE DIAGRAM OF THE CUSTOMER COMPLAINTS MANAGEMENT

Here in use case we have 3 actors, one is user have problems he register in the system with attributes and then log in and record the complaint in it and then the claim is forwarded to the staff to resolve it and notifying the person who is responsible to do necessary action and to the user about the resolved .

Staff can update the status of the complaint resolved or not in the interface. Ultimately the reason and minute detail will be checked and solved the problem . in this way the data is managed by the admin and works under his supervision.

FUNCTIONAL AND NON-FUNCTIONAL OF THE CUSTOMER COMPLAINTS MANAGEMENT

Functional requirements of the customer complaints management:-

The functional requirements are those requirements which are necessary to the eye of the user and the client. Here we try to make the module possible to accomplish the need of the desired function.

few of its functional requirements are as follows-

User required to fill the details with necessary validated inputs and registered to the system and using credentials doing the login task.
The user can specify the problem of his with the system determining the severity of the problem and when he gets the problem successfully.

The complaint goes to staff interface, and he reads that and takes necessary action.

The team takes action by sending notice to the responsible staff and saying him to resolve the problem or take appropriate action.

As problem get solved, he sends notice to the users such that the problem can be solved or not and the reason of the problem was the given and what necessary action needed to take care.

Non-Functional requirements of the customer complaints management:-

These requirements needs unit among the style of “system shall be “, associate an overall property of the regime as a full or of a particular aspect and not an individual operates.

The system’s overall features remarkably mark the excellence between whether or not the event project has succeeded or unsuccessful.

Non-functional needs of the customer complaints management –

Unit of measurement usually divided into two broad categories:

Execution qualities, like security and quality, that unit evident at the runtime.

Evolution qualities, like liabilities, maintainability, flexibility and quantitative, that unit embodied among the static structure of the code.

Non-functional of the customer complaints management needs place restrictions on the merchandise being developed, the event technique, and specify external constraints that the merchandise has to be compelled to meet

Our project qualifies all the factors of helpful and not helpful consequently, and the system is up to mark performance device.Here we’d prefer to need the care of few lots of things before heading towards the system.

the many sensible intuitive interfaces are usually created. that ultimately build interface easy to use for a lengthy time. in distinction to ancient vogue wherever the goal is to make the difficulty or application physically enticing, the purpose of interface trend is to create the user’s interaction expertise as straightforward and intuitive as double – what’s typically mentioned as user-centred vogue.

where smart graphic/industrial fashion is daring and eye-catching, intelligent interface trend is sometimes delicate and invisible.

Keep things simple and consistent:-

Straightforward and harmonic means that are making u i is extraordinarily intuitive and needs to followed

observe the use of typography:-

The typography is taken care really strictly as the wish of the system.

Use colour and distinction correctly:-

Color band of skin and dark is sweet means that stress and done well throughout this method

Consider feedback messages:-

Feedback sort may well be excellent implies that taking feedback of forms and rising the system.

Simplified forms:-

The structure is made simple to fill with a clean program.

ONLINE COMPLAINT MANAGEMENT SYSTEM DOCUMENTATION

CONCLUSION OF THE CUSTOMER COMPLAINTS MANAGEMENT

Finally in the customer complaints management, we have a system where users have problems he register in the system with attributes and then log in and record the complaint in it and then the claim is forwarded to the staff to resolve it and notifying the person who is responsible to do necessary action and to the user about the fixed and all the functions working fine and smooth.