3 of my actual cases.
I do far more than this.
These are three real cases — shared here as proof of work, not as the full picture. Each documents a different compliance risk: caught, controlled, and resolved entirely remotely, entirely independently. Every screenshot is real. Every order number happened. Order numbers and personal data redacted for client confidentiality.
Manual Prescription Verification — CYL Sign Discrepancy Intervention
Situation
Order #28***** — Identified a CYL sign inconsistency during routine pre-production Rx review: OD showed negative (−), OS showed positive (+). In prescription eyewear, this is the difference between lenses that correct vision and lenses that worsen it.
Risks Caught
- Lenses manufactured to incorrect specification — shipped to customer
- Costly lens remake + production delay
- Compliance documentation gap and potential audit exposure
Action Taken
- Placed order on compliance hold — stopped lab advancement immediately
- Reviewed SPH, CYL, AXIS, and PD values for both eyes
- Contacted customer directly — confirmed negative (−) for both OD and OS
- Updated CRM records · authorized lab release only after full confirmation
Return, Upgrade & Authorization Control with Lab Instruction
Situation
Order #28***** — Warehouse received a returned package with only an order number — no prior return request submitted. Without intervention: unauthorized modification, billing discrepancy, and lab production error. The case required immediate identification of the customer's intent, coordination of upgrade authorization, lab instruction documentation, and full CRM closure before production could proceed.
Risks Caught
- Unauthorized frame modification processed without customer confirmation
- Billing discrepancy — upgrade payment not yet authorized
- Lab receiving incorrect or incomplete production instructions
- No return record in CRM — invisible to the next agent
Action Taken
- Identified unannounced return — no prior RMA or return request on file
- Contacted customer to confirm intent: frame upgrade with same lenses (Progressive)
- Documented lab instruction: same lenses, new frame, photogrey/tinted
- Coordinated payment authorization for upgrade difference before releasing to lab
- Logged full case in CRM: return received, upgrade confirmed, lab instructed, payment noted
Multi-Channel Follow-Up & Cross-System Documentation Control
Situation
Order #28***** — Warranty eligibility inquiry on an already-flagged case. Email alone wasn't sufficient — needed outbound phone contact and full cross-system documentation to close the loop cleanly. The case involved a broken frame (customer slept on it), a reserved replacement unit, and a PayPal payment confirmation — all of which required coordination across CRM, email, and a tracking spreadsheet.
Risks Caught
- Warranty resolution left incomplete without phone confirmation
- Reserved replacement SKU not formally tied to case in CRM
- Payment confirmation and RMA instruction not cross-documented
- Lab receiving no formal instruction for exchange/refund
Action Taken
- Reviewed CRM hold note — identified need for outbound phone contact
- Called customer (Linda) to confirm situation and next steps
- Confirmed via email: payment received, RMA# issued, prepaid Canada Post label attached
- Updated tracking sheet: same lenses (Progressive), new frame (TOM OWO), photogrey/tinted
- Documented all three channels (CRM + email + spreadsheet) for full case continuity
"A CYL sign error is invisible to a system. An undocumented return is invisible to a CRM. A phone call that never gets logged is invisible to the next person. I make those things visible — and make sure they can't cause damage."