Skip to content
Astera Technology

Record customer confirmation without inferring it from silence

Separate a staff repair check from the customer’s observed task outcome.

Keep proposed and confirmed resolution separate

Synthetic support policy distinguishes repair-verified, customer-confirmed and review-needed. T-181 has a staff pass but no customer reply; it stays repair-verified awaiting outcome. T-182 has the customer’s matching task success; it can be customer-confirmed. T-183 has a reply reporting continued failure and returns to investigation. This fixture has no automatic silent closure rule.

Filled synthetic support record
TicketStaff evidenceCustomer evidenceResult state
T-181Matched test passNo replyRepair verified; outcome pending
T-182Matched test passSame task now succeedsCustomer confirmed
T-183Matched test passSame task still failsInvestigate remaining failure
Download editable CSV ↓

Apply the customer observation when received

  1. Record staff verification
  2. Request relevant customer outcome
  3. Classify reply or absence of reply
  4. Confirm or investigate on evidence

A delivery receipt or a thank-you about response speed is not a matching task confirmation.

How many tickets have customer-confirmed recovery?

Show the worked answer

One: T-182. T-181 has no customer outcome yet, and T-183 reports continued failure.

Use the closure policy actually agreed. Where a case may close without a reply, distinguish that disposition from customer-confirmed recovery.

Related resources