language: Deutsch   Français   italiano   Español   Português   日本語   russian   arabic   norwegian   swedish   danish   Nederlands   finland   ireland   English  

complaint definition | English definition dictionary | Reverso

complaint definition, complaint meaning | English dictionary English-French English Synonyms English for learners Grammar Search also in: Web News Encyclopedia Images Search Synonyms Conjugate Speak Suggest new translation/definition complaint   
      n    1    the act of complaining; an expression of grievance   
2    a cause for complaining; grievance   
3    a mild ailment   
4       (English law)    a statement by which a civil proceeding in a magistrates' court is commenced   
English Collins Dictionary - English Definition & Thesaurus    complaint    1    accusation, annoyance, beef       (slang)    bitch       (slang)    charge, criticism, dissatisfaction, fault-finding, grievance, gripe       (informal)    grouch       (informal)    grouse, grumble, lament, moan, plaint, protest, remonstrance, trouble, wail   
2    affliction, ailment, disease, disorder, illness, indisposition, malady, sickness, upset   
English Collins Dictionary - English synonyms & Thesaurus   
See also: compliant, complain, complainant, complaisant

Collab moncler-jackets-baby-rid-111267.html. us digital millennium copyright act 1998orative Dictionary     English Definition cyber protest n. cyber protest is expression of complaint through the medium of electronic communication on the electronic and digital Medias. [Tech.];[Leg.] You want to reject this entry: please give us your comments (bad translation/definition, duplicate entries...)
complaint definition

moncler baby boy snowsuit
outlet moncler online recensioni
discount moncler usa
outlet moncler milano via pisani Are Incident and Complaint different things? Submitted by skeptic on Mon, 2009-06-08 03:17 Share this post with Google Plus One Tweet Widget Pinterest

Continuing our philosophising over Incidents, the service management group down at the employment centre were wondering about Complaints and Incidents.

Recently this blog came up with a list of all the different kinds of request of which Incident is one (not in ITIL V3 it isn't, just in my taxonomy. In ITIL V3, a Service Request is by definition a not-Incident, a catch-all bucket for anything the Service Desk is asked to deal with that is not a service deviation.) One of those was a "Complaint".

Is a Complaint the same thing as an Incident? If a user is unhappy about what they receive from IT, is a service therefore deviating from the expected levels, or at least accused of being so?

I'm suggesting that by definition if a user complains, then they are saying that there is an Incident... but there is still a distinction worth retaining.

A Complaint can lead to one of a number of outcomes: There is a deviation from service levels that needs to be corrected - we respond to the Incident. I think we turn the Complaint into an Incident. There is not a deviation from service levels but they are complaining about a service. We need to follow up the Complaint as an Incident until we find that service levels are being met, then explain to the user and work out what can be done for them. We could provide advice or training They are complaining about something that is not covered by services, in which case we may not be empowered to help them. We need to explain to them that it is out of scope of services. We can accept a proposal that it should be a service, or we can pass on the negative feedback to someone else who might cover it or to those colllating such things, or we can perform some ad-hoc support for them, in which case there really ought to be a defined service for Ad Hoc Support in the catalogue to cover - and measure - such contingencies, which puts us back to (1)

I think this process and set of outcomes is the same as what will happen when someone reports an Incident: "Complaint" is a synonym for "first report of a possible Incident" and that's how we treat it at least initially. However if we find it isn't an Incident, it is useful to turn it into a Complaint. Someone wasn't happy and that is worth tracking and reporting. In fact something first reported as an Incident may end up being a Complaint.

The classic example is "It is too slow". If response times are within SLA then it isn't an Incident but that won't make the user any happier. We need to first ensure that response times are in fact within SLA (Incident) and then track and report dissatisfaction so that users feel heard and so that trend analysis may identify a real need to revise the SLA (Complaint).

What about "I wasn't happy with the way Dennis dealt with my call"? That's a Complaint alright but is it an Incident until proven otherwise? And if not, how do the Service Desk decide which Complaints to treat as Incidents initially and which not?

Published in The Skeptical Informer , July 2009, Volume 3, No. 5 Previous story: The information barrage - blinded by the light Next story: Common sense around ITIL V3 certification paths incident ITIL Comments Submitted by Geert (not verified) on Thu, 2009-06-11 11:03. KISS

In my company we've setup our service desk webinterface for end-users in a way that they can only log service requests of the following types (afterwards they're screened by the Service Desk and classified according to the ITIL V2-cycle): 1. problem 2. question 3. demand 4. complaint

1 would be your typical incident, 2 & 4 remain service requests and 3 is your RfC. Users don't care what (ITIL-)classification you use afterwards, they found it hard enough already to choose from these 4. I've seen the "My computer is slow" logged as anyone of the 4 categories, so why do we bother in the first place? ;-)

We do although deliberetaly leave the real complaints out of our formal Incident mgt. because there's no direct solution, workaround,... and we feel it needs to be treated by another "proces" we aptly called "complaints mgt." We see this complaint category in terms of a subjective interpretation of events caused by a (lack) of service. Eg.: the technician insulted me, you had to come back 5 times to finally solve it, why do we still have to use that M$-shit,...

All complaints are formally discussed at the regular service desk teammeetings, escalated if needed, discussed,... and eventually closed in accordance with the user. Of course we can't satisfy everybody, but people are generally appreciative of the fact that their issues aren't being discarded but always treated in the same, formal way.

Luckily we don't receive many "real complaints" but in my experience there's always a lesson to be learned somewhere, so I feel it's a usefull little proces to have.

Submitted by Mr. H (not verified) on Thu, 2009-06-11 01:06. Anyone Event Management?

According to ITIL Service Operation :

"An event can be defined as any detectable or discernible occurrence that has significance for the management of the IT Infrastructure or the delivery of IT service and evaluation of the impact a deviation might cause to the services"

A network working slower than usual (but inside SLA levels), bad manners of IT support personnel, an "ugly" user interface, a perfectly working but maybe "uncomfortable" process... those are occurrences that have significance for the management of IT services.

Why?

- Bad manners should be corrected to improve customer satisfaction and ease IT/Business cooperation - An ugly user interface could be improved and users morale and productivity could improve - An uncomfortable process could be the cause of change resistance and not compliance, and it can be improved

Event management is not limited to technical occurrences. All the before mentioned occurrences can impact services, and should be recorded and followed.

Submitted by Visitor (not verified) on Mon, 2009-06-08 16:03. Possible Solution

Re-route complaints. If you listen to a complaint you'll possibly have to consider whether or not it's an incident or blah blah. Re-route the call to the guy who sold the product/service etc. They or (general consumer ignorance) are generally the cause of all consumer complaints because they mis-represent the product/service in the first place.

You don't need ITIL for that either ;-)

Is mise le meas, Visitor

Submitted by skeptic on Tue, 2009-06-09 04:35. You've read the satirical

You've read the satirical Introduction to Real ITSM : • Complaint: complaints are a form of feedback but they are best dealt with separately, so that they can be ignored in a more focused manner and so they can be reported separately (or not at all).

Submitted by Harvey (not verified) on Mon, 2009-06-08 08:01. or it could be a Problem..

The service could be within SLA but the caller's service is still marginal.. e.g within the 99/100 limits but the 1 affected user happens to be the same one each time. This is particularly true for statistical measures e.g VOIP quality where it falls within limits but is still unacceptable to the user and hence the complaint.

Submitted by Mark O'Loughlin (not verified) on Mon, 2009-06-08 09:22. Hi, Whether or not a

Hi,

Whether or not a complaint is an incident or a service request, complaint handling should have its own distinct 'process' (or could it be a 'function'?). Complaint handling should be concerned with finding the "conditions of satisfaction" and trying to satisfy this (in as much as possible). A service management system could be used to record the complaint but I suggest that it needs to be configured with appropriate fields and workflow to achieve the objective rather than just logging an Incident or Service Request.

Submitted by jvbon on Mon, 2009-06-08 06:15. think out-of-the-ITIL-box

With all due respect, I think this is an example of 'classic thinking'. For the challenge of understanding the nature of a "complaint" you should think out-of-the-ITIL-box. There are only a few customer-facing processes in ITSM. Find these and you'll understand all of the interfaces between customer and provider in an IT setting. ITIL largely missed the boat here from version 1 forward. Another way of putting it: ITIL never meant to provide that kind of structured information in the first place. NB: this is a very personal opinion. It definitely is not what the fleet of ITIL-following consultants will tell you. But then again: who says the church (in whatever flavour you can find it) is right?

I say: think out-of-the-ITIL-box. There is a truck-load of service management knowledge outside of the IT domain available to help you out. Once you understand that, you can put ITIL to good use.

Submitted by aroos on Mon, 2009-06-08 06:46. Service does it using the IM tool

Jan This is the same argument we had a while ago. You had such a good point about keeping the process simple so I gave up.

After that discussion I have asked a couple of SD managers how they actually handle complaints and it seems that most have just added complaints as an additional class, along with incidents and service requests. It seems that most of the IM applications have more classes than what the book says.

When ITIL V4 or whatever that succeeds V3 comes, I think it should have one Customer Service process with several sub-processes for handling incidents, faults, service requests, sales, complaints and other feedback. It all comes to the same SPOC anyway and they usually have just one tool for recording calls.

Aale

Submitted by jvbon on Mon, 2009-06-08 15:11. That's what MOF v4 does

Aale, processes can be designed as activity clusters in many ways. MOF v4 does exactly what you describe. It's kind of playing leap-frog with ITIL. Have you read the ITIL v3-MOF v4 Cross Reference that was just published as a MOF Companion Guide by Microsoft? It's here: http://go.microsoft.com/fwlink/?LinkId=151991

Submitted by aroos on Tue, 2009-06-09 16:33. According to it MOF 4 stays closer to ITIL than V3

Yes, I have seen it. It is interesting that the document puts MOF in between of ITIL V2 and V3 Incident Management.

"...MOF on the other hand stays much closer to the ITIL V2 practice.."

How many times I have heard that V3 contains the V2 processes.

Submitted by buraddo on Mon, 2009-06-08 04:54. Confused

So if a system throws an error that was previously unknown and a ticket is created, what is that ? My assumption is incident.

If the error is found not to have created a service deviation, does it become something else. The incident definition used to talk about "or may cause a deviation in service", which means you don't have to pre-analyse the fault to determine impact to that level. A complaint would mostly fall into the category "or may cause".

I always thought a service request was a documented process that was driven from the service catalog, not a catchall. I think the service request definition is now "information, advice, routine change and/or initiation of service". You might be hard pushed to stick complaint into one of these categories.

Please quote the book on me for this one, because my detailed knowledge is fading in age.

$0.02

Brad Vaughan

Submitted by pjotrg on Mon, 2009-06-08 09:45. The servicedesk is the cargbage can

Nice and classic discussion. Indeed Jan, we should not be to dogmatic ;-)

To make a distinction between incident and a complaint I always use this example: The office manager of a high standing bank office (e,g, on the Champs Elysees, Paris) calls the servicedesk to tell that all worskstations in his bank office (on a very very busy day ! ) are out of service. This is clearly an incident. Technician (who is located at the other side of Paris) jumps on his motorbike, get there in 10 minutes, fixes the incident in another 10 minutes. Incident closed. An hour later the same office manager calls again. He says he's very happy about the speed and quality of the resolution, but that he is absolutely NOT satisfied about the way things are solved. He complains about the technician being dressed in shorts and an open shirt and behaving very rude and unpolite against bank staff and their customers. Now that's a complaint in myn opinion.

We at Dutch Telecom, way back in 1998 in the ITIL V1 era ;-), had the same sort of discussion while setting up a Servicedesk for our outsourcing service. We assumed that a user would not call the servicedesk just for fun ( OK, I know even that kind of users exists, even those who call just to hear the voice of the female operator.... ), so we decided that we wanted to be able to dispach, track, trace and follow all calls. We "invented" a call process which handled this and shifted all calls in: - incidents - request for change - service requests (in our definition: small jobs to be done by IT, neither being incident nor change. Things like fill toner, abort print queues, print jobs, etc.) - requests for information, like status of an incident, "where do I find", "how do I print in bold" - complaints - other/undefined (all other calls)

We adapted our servicedesk system (ARS/Remedy at that moment) so that every call could be given a reference number (to give to the user who called). The trouble we got afterwards was of a technical nature: a call gets classified as an incident. How to transfer the date into the incident database, without changing the reference numer and without creating redundant data or corrupt numbering but still being able to trace back the reference number easily. That gave us a lot of trouble. so basically the idea was nice, the (technical) implementation at that moment was hardly impossible.

Submitted by buraddo on Tue, 2009-06-09 19:56. Rudeness might be a deviation from servicelevel

Isn't a bit limiting to think of service quality in just terms of technical service levels. The way service is delivered is also contributes to the satisfaction with IT..

If a service delivery staffer abused me, but still met the service levels. Thats a incident in my book.. In fact, an incident that might be logged at the HR help desk.

Brad Vaughan

Submitted by pjotrg on Wed, 2009-06-10 11:39. Indeed, but the point I

Indeed, but the point I wanted to make is that a complaint may follow a totally different route from "normal" incidents (which are more "technical"). Still it is important to track and trace complaints to. Complaints can be seen as indications from the user oragnisation that we have chances to improve our services!

The compliant example I gave was not very measurable. It was adressed at the servicedesk, but quickly dispatched to the manager of the technician in shorts. It was treated as a quality issue and was followed up a such.

Delivering services is not an easy job nor is measuring service. The tangible things can be easily measured, measuring perception is much more difficult. Still a good technical quality delivered by unfriendly and unwilling people will be percieved as bad whereas a lousy service but deliverd with a big smile can be percieved as very good. Aren't we human?

Submitted by JamesFinister on Tue, 2009-06-09 20:05. Agreed

I've put things like attitude, behaviour in the client's offices and dress code into contracts and SLAs before now

Submitted by skeptic on Mon, 2009-06-08 10:35. Brigitte

I worked one place where we argued over who got to call the service desk, just ot hear "'Allo. Thees ees Brigitte. Can I 'elp you?" in the sexiest French accent. In those days women in IT were very few and far between :)

Submitted by pjotrg on Thu, 2009-06-11 06:15. as a summary...

Even though we apparantly all want to give it another name and contain it yes or no within an existing ITIL proces, we do all agree that also the more untangible, non-technical moments of negative customer perception do need to be dealth with in a proper way.

I think it's not very important whether or not you use an ITIL proces to do so as long a you deal with it in a proper way.

Having sorted that out (with your permission ;-) ) I've got another one: how do we deal with compliments, positive feedback ? ;-)



Define: Spam Complaint

For email, a spam complaint refers to when an email user flags a message as “junk” or “unsolicited.” Spam complaints can be reserved for emails of a promotional nature that are sent to email users without their permission. Email providers often display a simple, one-click solution to report and block spam from an account. However, spam complaints have evolved with the increased popularity of email marketing to affect email communications that users perceive as unwanted. If a user has subscribed to a mailing list requesting regular messages, they may still mark these messages as spam as soon as the messages transition in the email user’s mind from “useful” to “bothersome.”

Email users sometimes mark legitimate messages as spam because it is the easiest way to “unsubscribe” from a list that is no longer valuable to them; this can occur because the unsubscribe option is not readily available to the user or because they are unaware that reporting as spam and unsubscribing are not synonymous actions. Because there is no check to ensure that email users are only marking truly unsolicited emails as spam, email marketers must be careful to avoid being marked as spam. Those that are marked as such run the risk having their emails blocked and their email campaign efforts stunted.

Email marketers can take precautions to prevent their messages from being marked as spam. First, the marketer can implement clear opt-in subscriptions — or double opt-in subscriptions to recruit list members. This practice ensures that members actively request information. Second, the marketer can ensure that all messages are relevant to the list’s interests and that messages are not sent at an overwhelmingly frequent or infrequent rate. Finally, marketers can provide a clear “unsubscribe” option in each email message that signals to readers that they should follow these steps to end further communication.

Browse Glossary A B C D E F G H I J K L M N O P Q R S T U V W X Y Z