Deactivating an evaluation: set a conversation aside from your quality monitoring, without losing it

Raisetalk lets you deactivate an evaluation: an administrator or a supervisor can set an evaluation aside from quality monitoring when it should not count (poor recording quality, customer GDPR request, out-of-scope conversation, wrong attribution). A deactivated evaluation disappears from the list, reporting, exports and searches, but nothing is deleted: the action is reversible, validated by an administrator and fully traced.

Deactivating an evaluation in Raisetalk

Key takeaways on deactivating an evaluation

  • Raisetalk lets you deactivate an evaluation: an administrator or a supervisor can set an evaluation aside from quality monitoring when it should not count (poor recording quality, customer GDPR request, out-of-scope conversation, wrong attribution).
  • A deactivated evaluation disappears everywhere: conversation list, reporting and indicators, exports, and searches in the Discovery section. Your figures are no longer polluted.
  • Deactivating is not deleting: the action is reversible. Permanent deletion (GDPR) remains a separate act.
  • Control stays with the administrator: every deactivation goes through a validation, or a rejection (reactivation), from a dedicated monitoring page.
  • Everything is traced: each step creates a version of the evaluation, timestamped, with its author and justification comment.

Why would you need to deactivate an evaluation?

In a quality monitoring setup, not all analysed conversations are meant to count. An unusable recording, a call attributed to the wrong advisor, an out-of-scope conversation, or a customer asking that their exchange no longer be used: all cases where an evaluation must be set aside.

Until now, the choice was between two extremes: keep everything, at the risk of skewing your indicators and coaching on questionable data; or delete everything, losing the data and its traceability for good. Deactivation opens a third way, clean and governed.

In practice, how do you deactivate an evaluation?

From a conversation's detail page, a "Deactivate evaluation" block lets you start the request by entering a mandatory justification comment. The action is deliberately explicit and restricted to authorised profiles.

The Deactivate evaluation panel opened on a Raisetalk conversation

Once the deactivation is requested, the evaluation is immediately removed from monitoring and placed pending a decision. It can even be deactivated while its analysis is not yet complete.

Is deactivating an evaluation the same as deleting it?

No, and the distinction is essential. Deactivating an evaluation means excluding it from quality monitoring, in a reversible way: at any time, an administrator can reactivate it and bring it back everywhere. No data is destroyed.

The permanent deletion of a conversation (for example as part of a GDPR erasure) remains a separate, irreversible act, handled distinctly. Deactivation answers the everyday need to set aside without losing, and to be able to go back.

Who can deactivate, and who decides?

The feature separates two responsibilities: triggering a deactivation, and settling it. The default rights are as follows:

ActionAdministratorSupervisorAdvisor
Deactivate an evaluation✅✅❌
Validate or reactivate✅❌❌

A supervisor can therefore flag an evaluation to be set aside, but it is an administrator who confirms the deactivation or rejects it. This separation guarantees a systematic control check.

What happens to a deactivated evaluation?

As long as an evaluation is deactivated, it is excluded from all monitoring uses:

  • it no longer appears in the conversation list;
  • it is removed from reporting and all indicators;
  • it is excluded from exports (CSV and PDF);
  • it is no longer used in Discovery searches.

Its detail remains accessible to administrators only, the rest of the page being intentionally greyed out, with an option to show it occasionally without reactivating it. The goal: never let a set-aside piece of data influence a decision, while keeping the ability to review it.

How do you monitor and handle deactivations?

Administrators have a dedicated page, with a badge showing the number of requests awaiting handling. Each deactivation is tracked individually (the same evaluation can be deactivated several times over time).

Evaluation deactivation tracking page in Raisetalk

The page offers indicators (requests, validated, rejected), filters by status and by evaluated advisor, and two actions on each pending request: validate the deactivation, or reactivate the evaluation to bring it back into monitoring.

How do you keep track of every decision?

Each step, deactivation, validation, reactivation, creates a version of the evaluation: who, when, and why. The justification comment is kept and viewable, including on hovering the status.

Version history of a deactivated evaluation in Raisetalk

This complete history lives alongside the usual evaluation changes, in the conversation's detail page. Nothing is lost, everything is justified.

Why is this a governance matter?

Steering quality with data only makes sense if that data is reliable, and if the decisions that set it aside are themselves controlled and traceable. Deactivation delivers exactly that: a clean way to exclude what should not count, without destruction, with administrator validation and a full audit trail.

It is one more trust building block, consistent with the Raisetalk promise: transparency, explainability, and respect for privacy. This is different from contesting a single criterion, where the advisor discusses one specific score inside an evaluation: deactivating sets the whole evaluation aside. To go further, explore automated quality monitoring.

Blue tokens spread over a board divided into four zones, a single coral token set apart in one corner
Quality Monitoring 12 min

Evaluation disputes: what they tell you about your quality scorecard

A heavily disputed criterion is not necessarily a badly written one. Dispute rate and acceptance rate read criterion by criterion, the cause selected by the arbitrator, response time as a median: the method for knowing which criteria to review and which to explain, and how the Raisetalk Disputes report puts it into practice.

A row of blue chairs facing each other in pairs, one coral pair in the centre
Quality Monitoring 12 min

Tracking coaching: checking that debriefs take place, and what they change

Evaluating is not coaching. The number of debriefs says neither whether they were completed nor which advisors were seen. Stages, times as a median, team coverage, criteria worked on before and after: the method for tracking coaching, and how the Raisetalk Debriefs report puts it into practice.

A queue of blue call bubbles, two of them coral and joined by an arc
Quality Monitoring 14 min

First call resolution rate: measuring it on your customers' real callbacks

A customer who calls back about the same thing was not served on the first call. Advisor-entered status, instant survey, same number within 7 days: the usual FCR measures mislead. The method for a reliable rate, and how Once & Done in Raisetalk applies it to 100% of calls.

A coral speech bubble with jagged edges, picked out in the middle of a stream of blue bubbles
Use Case 12 min

Customer incivility: identifying it in calls to alert and support advisors

An angry customer is not an uncivil customer. Insults, threats, discriminatory remarks: incivility targets the advisor as a person, and most of the time it goes unnoticed. A three-step method to identify it on 100% of calls, alert the right manager and support teams, without measuring emotion.

Three screens of the new Raisetalk interface: dashboard, evaluation page, contestation panel
Conversational Analysis 7 min

The new Raisetalk interface: conversational analysis moves up another gear

Raisetalk unveils its new interface, delivered the weekend of 1 November: more modern, clearer and, above all, more productive, built on the foundations that make it strong. A dashboard for every role, every score proven in one click, one way to search everywhere, and everything you rely on still in place.

A coral label is tied by four threads to four distinct objects set side by side
Quality Monitoring 16 min

Quality monitoring: what the term really covers, and why two tools carrying that label do not do the same job

Scoring advisors, checking regulatory compliance, listening to the voice of the customer, coaching a sales force: four disciplines circulate under the "quality monitoring" label. They do not have the same users, the same scorecards or the same standards of proof. The framework for telling them apart, why a tool does not carry over from one to another, and how to write a specification that does not mix them up.

Upload a call. Read its analysis. Five minutes.

Sign up in seconds, with no credit card and no cookies. A welcome tour walks you through the key principles, then you add your first conversation.

Early access · Your feedback shapes the product