Philippines staffing research
What share of ecommerce exception cases close on a destination record?
Contents
A research protocol for testing whether partial-refund, missing-item, and delivery-exception cases close when the payment or fulfillment record changes, not when a message is sent.
Question and scope
This study asks what share of ecommerce exception cases have a destination record that matches the approved resolution at the time the case is closed. It covers partial refunds, missing items, damaged goods, and delivery exceptions. The unit is one case. The question is about closure evidence, not about whether the customer was satisfied or whether the policy was generous enough. The scope includes the customer claim, the order and payment records, the fulfillment and carrier evidence, the decision, and the final customer communication. It excludes cases that were never assigned to the team or that remain open at the end of the window. A case that is closed in the help desk but has no matching payment or replacement record is recorded as an evidence gap.
Method and evidence frame
Use a retrospective case review. For each closed case, identify the approved resolution and the record that should change as a result: a refund transaction, a replacement order, a return authorization, or a carrier claim. Check whether that record exists, matches the approved amount or quantity, and carries a date after the decision. Record the result as matched, mismatched, missing, or not applicable. The evidence frame separates the customer claim, the internal decision, the operational action, and the customer communication. A sent message proves that someone communicated; it does not prove that the refund was issued or the replacement shipped. A payment record proves that money moved; it does not prove that the customer was told. The study needs both sides to call a case closed.
Population and unit of analysis
The population is all exception cases closed during the observation window for the selected store or queue. The unit is one case, even if it involves several items or several messages. A case that is reopened is linked to the original but recorded as a new closure event. A case with multiple resolutions, such as a partial refund plus a replacement, is one unit with multiple destination checks. Define whether cases closed by a third-party marketplace or payment provider are included. Include them if the team owns the customer communication, but record the external dependency. Exclude cases that were closed before the observation window and never reopened. Report the counts so the denominator is clear.
Definitions and measures
The primary measure is the share of closed cases with a matching destination record. A secondary measure is the share with a customer communication that matches the approved resolution. A third measure is the share with a documented decision owner. Report each separately because a case can have a correct refund and a wrong customer message, or a correct message and no refund. Supporting measures include the time from decision to destination record, the number of reopened cases, the number of partial matches, and the share of cases with missing carrier or warehouse evidence. A partial match, such as a refund for the right amount but the wrong currency, is recorded as a mismatch rather than rounded up to a success.
Sampling and collection
Sample across exception types, order values, channels, and resolution methods. Include at least one refund, one replacement, one return, and one carrier claim if the population contains them. Include a reopened case if available. Use consecutive closures where possible and record every exclusion. A sample of only high-value cases will not represent the routine queue. Collect the case record, the customer messages, the order record, the payment transaction, the fulfillment or replacement record, and the decision approval. Record the observation time and the source system for each. If the payment provider's interface shows only a status, capture the transaction reference and the amount rather than a screenshot that cannot be verified later.
Analysis and reporting
Report the match rate by resolution type and by case age. A high overall rate can hide a low rate for carrier claims or for cases closed quickly. Group defects by no destination record, wrong amount, wrong item, wrong date, missing approval, and communication mismatch. Show the count and share for each category and the number of cases affected. Separate observation from interpretation. A missing destination record may mean the action was not taken, the record is in another system, or the case was closed prematurely. The study can report the missing evidence, but it cannot decide which explanation is true without a source that distinguishes them. State that limit rather than assuming the worst or the best.
Limits and sources of error
Payment and fulfillment systems have different retention and visibility rules. A refund may appear as a pending transaction before it settles, and a replacement may be created in a system the case reviewer cannot access. Record these system limits. Small samples are sensitive to one carrier incident or one bulk upload, which can distort the closure rate if events are not stratified. The study cannot establish that the customer was treated fairly, that the refund complied with the applicable policy, or that the case was legally resolved. It tests closure evidence. The Federal Trade Commission, the Consumer Financial Protection Bureau, and the PCI Security Standards Council provide general context on commerce, complaints, and payment security, not a decision for a specific case.
Operational use
Use the result to add a destination-record check to the closure step, to clarify which system is authoritative for each resolution, or to separate the customer communication from the financial action. A defect concentrated in one resolution type is a workflow problem. A defect spread across the queue may require a template or access change. A closure check also protects the customer relationship. When a customer asks whether the refund was issued, the team can point to the transaction instead of reopening the entire case. That reduces repeat contacts and makes the answer easier to defend.
Review cadence
Review closure evidence monthly for high-volume stores and quarterly for stable ones. Repeat the review after a payment-provider change, a fulfillment-system migration, or a policy update. Keep the sample rule and the definitions stable so the comparison is meaningful. Close the review with one owner, one workflow change, and a re-test date. Preserve the sampled cases and the destination references so a later reviewer can repeat the test. A case that is closed without evidence is not resolved; it is only removed from the active queue.