A return request is matched to the order it belongs to and checked against the account's return history for a pattern that looks more like shrinkage than preference. Refunds only post after a support lead has looked at flagged accounts.
How it runs
pattern matchcleanapproved
Trigger
Return request receivedMicrosoft 365 and Outlook
Extraction
Read the return requestemail, portal form, marketplace message
Lookup
Match to the order historyShopify and marketplace channels
Triage
Check against the return patternaccount-level pattern check
Rule
Confidence check
Branch
Flag pattern matches for a closer look
Human gate
Support lead sign-off
System writesensitive
Post the refundFinance and ledger systems
Outbound comms
Notify the customerMicrosoft 365 and Outlook
Outcome
Refund processed
Trigger
Extraction
Lookup
Triage
Rule
Branch
Human gate
System write
Outbound comms
Outcome
What it could return
Support minutes spent matching a return to its order and checking the account for a pattern before a refund posts.
$13,662per year, returned
569 hrsper year, back
A rough estimate until this is measured on your own numbers. Every input above is yours to change.
Systems touched
Agentic skills run
Where the human sits
Refunds don't post on their own. A support lead checks the return against the account's history and signs off first.
Confidence floor 70% — anything under that holds for a person instead of guessing.