Summary

Sam noticed duplicate recipient phone numbers in the RingCentral Matter panel dropdown. The fix was to dedupe exact callable endpoints globally by normalized phone plus displayed extension, instead of preserving duplicates by field/source label. This keeps distinct extensions, different people, and the Other option available, while collapsing rows like Client and Client Mobile when they point to the same exact number.

What Shipped

• Updated LitifyRingCentralContextController.cls so phoneOptionKey uses normalized phone plus display phone/extension.
• Updated LitifyRingCentralContextControllerTest.cls with a regression assertion that exact duplicate recipient numbers collapse to one call target.
• Kept SMS Magic data and automation untouched.
• Kept RingCentral as the staff-facing communications surface and preserved the record-trail direction.

Verification

• Check-only deploy 0AfUV000001Wwhp0AC: succeeded, 3 tests run, 0 failures, 0 component errors.
• Production deploy 0AfUV000001WwjR0AS: succeeded, 3 tests run, 0 failures, 0 component errors.
• Live Apex context check against Matter a0LUV00000BBjTJ2A1: returned 19 recipient options, duplicateDisplays empty, preferred phone +15027955105, party name Natalia Cross.
• Playwright visual QA on the real Matter page confirmed the RingCentral tab opens and the dropdown shows the deduped list: Client once, Client Home once, Daniel Long, State Farm carrier, State Farm work extension, Optum, Passport, Molly McAndrews, provider/records contacts, KORT, and Other / enter another number.

Artifacts

• Screenshot: /Users/samaguiar/Documents/Projects/ringcentral-dedupe-dropdown-open-2026-05-17.png
• Closed-panel screenshot: /Users/samaguiar/Documents/Projects/ringcentral-dedupe-panel-closed-2026-05-17.png
• Snapshot: /Users/samaguiar/Documents/Projects/ringcentral-dedupe-dropdown-open-depth16-2026-05-17.md
• Rollback retrieve: /Users/samaguiar/Documents/Projects/Repos/sail-litify/Litify_AI_Integration_Project/salesforce-metadata/tmp/ringcentral-recipient-dedupe-2026-05-17/rollback-live

Reason For Ending

The scoped duplicate cleanup is deployed and verified. The broader RingCentral panel work remains ongoing, but this specific dropdown duplicate issue is complete.

Suggested Next Steps