Noor Alseginy
Back to selected work
Legal-tech build · In production

Refund Review Pipeline

Review the lead. Check the rules. Use CRM notes when the answer is unclear. File qualifying refunds and send uncertain cases to a person.

13
Attorney accounts
4
Production refund checks
Human review
For uncertain cases, based on score and severity

Follow the evidence.

Input / Checks / Decision
Synthetic records · Demonstration checks

The examples explain the workflow. Production rule definitions and client data are private.

  1. 01Record
  2. 02Checks
  3. 03CRM context
  4. 04Decision
Ready to follow

Sample lead

SAMPLE-104
Account
Example Account A
Request
Possible duplicate inquiry
Supporting evidence
Matching reference: SAMPLE-081
Record status
Complete, with no conflicting disposition

Demonstration checks

0 / 4
  1. Account matchWaiting
  2. Required detailsWaiting
  3. Refund evidenceWaiting
  4. Record consistencyWaiting

Simplified checks for these examples.

Sample CRM note

If needed

Follow the checks to see whether context is needed.

Illustrated decision

Follow the checks.

The result and its supporting evidence appear here.

Walkthrough only

Three implementation choices

Across systems

Browser automation

Headless Chrome and element-level mapping move the workflow between the lead system and CRM.

Context

Rules first, notes when needed

The four checks handle the initial assessment. Call notes provide context for an unclear record.

Uncertainty

A human review path

Scoring and severity flag uncertain cases for a person to review.

My role and the result

I specified, debugged, and tested the pipeline through production with Claude Code. It now handles the routine checks and refund filing across 13 attorney accounts, with uncertain cases held for human review.

Headless Chrome · Claude Code · GoHighLevel