Skip to content

Scenario · Manufacturing · Customer complaintsScenario · Complaints

A closed complaint comes back. Can you show what was done?

Kiara closed the gland-leak complaint a day early. A week later the customer found one more leaking valve, from a lot assembled before her fix.

TaskMIS task 1007-0003, Corrective action: gland leak complaint, lot 0928: raised by Aarav Shah on 7 Oct as an External request, assigned to Kiara Rao, In Progress, High priority, Very High impact, due 30 Oct after one move from 21 Oct with the reason Reopened: Customer found one more leak, on lot 1019, assembled before the change. Shown on Tuesday 27 Oct at 10:20 AM
Task 1007-0003 on Tuesday 27 Oct, 10:20 AM · Beta1 demo workspace, sample data
See the same complaint in TaskMIS

Illustrative scenario. Beta1 is a fictional company. Not a customer story.

Meet Beta1 — a fictional valve manufacturer in Coimbatore.

  • Kiara RaoKiara · Quality
  • Aarav ShahAarav · Sales · Admin

What went wrong

Closed in the register. Open with the customer.

  1. CustomerReports gland leaks on lot 0928.
  2. QualityFixes the packing. The register says “closed”.
  3. CustomerFinds another leak, on an older lot.
  4. ManagementAsks what was done. Nobody can show it.

One closed complaint. Three problems.

  • The same complaint twiceThe second leak looks like the first fix failed, even when it didn’t.
  • No proof for the customerWhat changed, and from which lot, is scattered across mails and calls.
  • Starting again from zeroThe second round begins without the first one in front of it.

The same complaint with TaskMIS

Same complaint. One record from start to finish.

  1. 01 AssignWed 7 Oct
  2. 02 CloseTue 20 Oct
  3. 03 ReopenTue 27 Oct
  4. 04 Close againFri 30 Oct

Wed 7 Oct, 4:30 PM · Assign

The complaint becomes Kiara’s corrective action.

After the complaint review, Aarav raises it for Kiara as an External request: High priority, Very High impact, due 21 Oct. The customer’s complaint goes in as what done looks like.

Task 1007-0003 on Kiara Rao’s phone: Corrective action: gland leak complaint, lot 0928, Quality, Customer complaints, raised by Aarav Shah on 7 Oct, on track; assigned to Kiara Rao, not started, High priority, due 21 Oct in 14 days, not waiting, Quality and Customer complaints, External request from Aarav Shah on 7 Oct
Kiara’s phone, 7 Oct, 4:45 PM

New-task mail to Kiara

Mon 12 – Tue 20 Oct · CloseMon 12 – Tue 20 Oct · Find the cause, fix, close

Cause found, fix made, closed a day early.

On the 12th Kiara records the cause: undersized packing rings from a new supplier. On the 19th the torque values go on the assembly sheet, and twenty valves from stock pass a re-test. She completes the task on Tuesday 20 Oct. It moves to the Archive, and Aarav gets the completion mail.

Completion mail to Aarav Shah: Kiara Rao completed your task, Corrective action: gland leak complaint, lot 0928; completed on Tue 20 Oct 2026; target date Wed 21 Oct 2026, early; date moved never; reminders sent 1; done by Kiara Rao; task 1007-0003; Not done the way you needed? The team admin can reopen it, with a reason.
Aarav’s completion mail, 20 Oct

Completion mail to Aarav

Tue 27 Oct, 10:15 AM · ReopenTue 27 Oct, 10:15 AM · Reopen, with the reason

One more leak. The same task comes back, with the reason.

The new leak is on lot 1019, assembled before the change. Aarav reopens the task from the Archive. The reason is required, and goes on the record. He sets a new date, 30 Oct, and Kiara gets the reopen mail. His dashboard now counts it under Reopened last 30 days.

Record entries on task 1007-0003: Status: In Progress → Completed, Kiara Rao, 20 Oct, 12:00; Aarav Shah, 27 Oct, 10:15: Reopened — Customer found one more leak, on lot 1019, assembled before the change; Date moved 21 Oct to 30 Oct by Aarav Shah, 27 Oct, Reopened: Customer found one more leak, on lot 1019, assembled before the change.
The record, 27 Oct · the first completion, then the reopen and its reason

Reopen mail to Kiara

Tue 27 Oct · 10:15 AM

Kiara’s reopen mail carries the reason and the new target date.

Reopen mail to Kiara Rao: Aarav Shah reopened a task, Corrective action: gland leak complaint, lot 0928; reason: Customer found one more leak, on lot 1019, assembled before the change; new target date Fri 30 Oct 2026; raised by Aarav Shah; task 1007-0003; It is back on your list.
Kiara’s reopen mail, 27 Oct

Fri 30 Oct, 3:20 PM · Close againFri 30 Oct, 3:20 PM · Close again, with both rounds kept

Closed again. Both rounds on one record.

Kiara re-packs and re-tests lot 1019, tells the customer, and completes the task at 3:20 PM. Aarav gets the completion mail. The record keeps the cause, the fix, both completions and the reopen with its reason, and a search of the Archive for “gland” finds it.

The complete record of task 1007-0003: raised by Aarav Shah on 7 Oct at 16:30; Status: Not Started → In Progress, 8 Oct; Kiara Rao on 12 Oct, cause: packing rings from the new supplier are undersized, going back to braided graphite packing; 19 Oct, torque values added to the assembly sheet, twenty valves from stock re-tested, no leaks; Status: In Progress → Completed, 20 Oct; Aarav Shah on 27 Oct, reopened with the reason, customer found one more leak, on lot 1019, assembled before the change; date moved 21 Oct to 30 Oct; Kiara Rao on 30 Oct at 15:15, lot 1019 re-packed and re-tested, customer informed; completed and delivered 30 Oct at 15:20
The record after the second completion · append-only, no user can edit

Completion mail to Aarav

Archive, searched for gland, Friday 30 Oct: 1 completed task, history stays forever, nothing is ever deleted; 1007-0003, Corrective action: gland leak complaint, lot 0928, Kiara Rao, High, completed 30 Oct
Archive → search “gland”, 30 Oct · history stays forever, nothing is ever deleted

Try it on the customer complaints open today.

Free for up to 6 members. No credit card required.

Join TaskMIS Today

The difference

Same complaint. Different second round.

DateIn a complaint registerIn TaskMIS
7 OctWedRegisterLogged “under analysis”.In TaskMISTask 1007-0003 · owner Kiara Rao · due 21 Oct
20 OctTueRegisterThe register says “closed”.In TaskMISCompleted a day early; Aarav gets the completion mail
27 OctTueRegisterAnother leak. A new row, or an argument about the old one.In TaskMISReopened from the Archive, with the reason; new date 30 Oct
30 OctFriRegisterWhat was done the first time is in someone’s mails.In TaskMISLot 1019 re-packed and re-tested; customer informedCompleted

The second leak came either way. The difference is that the complaint came back to the same owner, with the reason and the first round in front of her.

What could change

Three outcomes for Beta1

A complaint has an owner and a date from day one.

The corrective action is Kiara’s task, raised as an External request, due 21 Oct.

FeatureOne owner on every task · A target date is required

Closed doesn’t mean gone.

A completed task moves to the Archive with its record. If the problem comes back, an admin reopens the same task, with a reason.

FeatureArchive · Reopen with a reason

Management sees what came back, and why.

Reopened work is counted on the dashboard, and the reason is on the record for anyone on the team to read.

FeatureDashboard · Reopened last 30 days

Possible outcomes in a fictional scenario, not measured customer results.

Used in this scenario

  • One accountable owner
  • One target date
  • Completion mail
  • Archive
  • Reopen with a reason
  • Task history
See every feature on the Product page →

For management

Four answers, before the customer asks

  • Which complaints are still open, and with whom?

    Answered in: Tasks · Department filter
  • What did we reopen this month, and why?

    Answered in: Dashboard · Reopened last 30 days
  • What did we do about the last gland-leak complaint?

    Answered in: Archive · Search
  • Was it closed by the date we promised?

    Answered in: Completion mail · Target date

Start this week

Start with the complaints open today

  1. Raise each open customer complaint as a task for one owner, with the date you promised the customer.
  2. Put the complaint in what done looks like, and post the cause and the fix as updates.
  3. When a closed complaint comes back, reopen the same task from the Archive, with the reason, instead of starting a new one.

Questions

Quick answers

Who can reopen a completed task?

A team admin, from the Archive. A reason is required, and it goes on the task’s record.

Who is told when a task is reopened?

The owner and the person who raised it get a reopen mail, except whoever reopened it.

Is anything deleted when a task goes to the Archive?

No. The task keeps its full record. The Archive says it plainly: history stays forever, nothing is ever deleted.

Bring clarity and accountability to your team.

Join TaskMIS Today

Free for up to 6 members. No credit card required.