Browser automation
The work spans a lead system and a CRM. I used headless Chrome and element-level mapping to move through the workflow.
Refund Review Pipeline
A lead comes in. The pipeline checks the refund rules, looks at the CRM notes when needed, and files the refund. Uncertain cases get flagged for a person to review.
- 13
- Attorney accounts
- 4
- Refund rules checked
- Human review
- For uncertain cases, based on score and severity
Follow a decision
The workflow crosses the lead system and CRM. Four refund checks handle the initial decision. CRM call notes provide context when the answer is unclear.
Illustrated walkthrough · Sample decisions
Choose a case to follow its path. These samples explain the production workflow without client data or live system access.
01 / Lead record
01 / InputLead record
Review the lead in its attorney account.
02 / RulesFour refund checks
Evaluate the record against the refund rules.
03 / ContextCRM notes + scoring
Check call notes when needed. Assess score and severity.
Outcome AFile the refund
Complete the refund workflow for a qualifying record.
Outcome BFlag for human review
Hold an uncertain decision for a person to review.
Review the lead in its attorney account.
Sample outcome: the record meets the refund criteria. The pipeline files the refund.
The decisions behind the workflow
Rules first, notes when needed
Four refund checks handle the initial assessment. CRM call notes supply context when the answer is unclear.
A person owns the uncertain decision
Scoring and severity determine when to flag a record for human review.
My role
I specified, debugged, and tested the pipeline through production with Claude Code.
Headless Chrome · Claude Code · GoHighLevel
The result
The pipeline is in production across 13 attorney accounts. It handles the routine checks and refund filing, while uncertain cases go to human review.