Complaint Ownership and Closure

Newly opened complaints sitting without an owner, SLA misses passing without anyone acting, or reports that count an operational fix and a customer-confirmed closure as the same thing all call for this journey. Complaints need a type, a severity and a related record, the owner must be derivable from those, every severity needs an SLA threshold, and a permitted contact route for the confirmation question has to be stored before launch. If records open from a negative sentiment score alone or from support conversations that have not yet established a failure, fix the trigger source first; this journey follows a detected failure.

Confirmed closure rate

The journey exists to produce an owned fix and a closure the customer has confirmed; a recorded operational fix or a delivered confirmation question does not show that on its own.

How it is counted: Among all complaints opened into the journey, the share closed as resolved and confirmed within the same follow-up window. A classic control group does not apply here; report closures that did not require confirmation on a separate line, and do not let delivery or non-response to the question change the denominator.

Also track

• Resolution rateOf all opened complaints, count those whose operational fix is recorded within the SLA threshold; the intermediate step before confirmation and the work that closes without escalating.
• Unowned and escalated shareTrack records handed off for lack of an owner and records escalated at least one level separately; if both climb, the problem is in the assignment rule or in team capacity.
• Unconfirmed closures and reopensCount closures that went unconfirmed because the window expired or no permitted route existed, and reopens where the customer said the problem persists, as separate numbers; a rise in the second says the fix is not closing the real issue.
• Complaints and opt-outs on the confirmation askAmong people who received the confirmation question, watch email unsubscribes, in-app message opt-outs and new support contacts; asking for confirmation should not create a fresh complaint.

• Trigger and entryAn actionable issue enters once it is formally created and verified in the system with a type, a severity and a related entity. Because the only customer message is the confirmation question, do not hold out a random control group; measure the outcome across every complaint that enters.
• Who must not enterOne complaint record is one journey instance. Duplicates against the same underlying problem are reconciled at entry rather than opened twice, and a negative sentiment score or a support conversation that has not yet identified a failure does not start the journey.
• Timing and channelsWhen the owner is known, the issue is assigned and waits for the operational fix up to the SLA threshold for that severity; a miss escalates one level and nothing goes to the customer. If closure requires confirmation and a permitted route exists, the confirmation question goes out by email or in-app message.
• Exit and handoffAn issue with no determinable owner is handed to Work assignment, and one that outlives its escalation ladder to the Human-in-the-loop journey. The record closes either as resolved and confirmed, or as fixed operationally when the confirmation window expires or no permitted route exists.
• Frequency and consentThe confirmation question goes out once per fix, only where a permitted route for issue correspondence exists; if the customer says it is still not right, the record returns to resolution until the reopen limit, then escalates. Engagement does not extend the confirmation window; assignment and escalation are human tasks and carry the full history.

1. 1Read the confirmed closure rate next to unconfirmed closures: if total closures rise while the confirmed share falls, records are closing quietly rather than quickly. Where confirmation is required, never assume closure before it arrives; an unanswered record is an unconfirmed closure, not verified satisfaction.
2. 2Keep the conclusion tied to these SLA thresholds, this confirmation window and this reopen limit. The outcome of a record handed off for lack of an owner, or escalated past the ladder into the Human-in-the-loop journey, is credited to that journey; a record left without an owner never counts as a resolution here.
3. 3When confirmed closure is a rare outcome and volumes are low, monthly rates will swing; before comparing two periods or two teams, use the sample size calculator with your current closure rate and the smallest difference you want to see to find how many records you need, and keep the follow-up window long enough to cover the whole confirmation window.