Use one standard recipient dropdown on the Matter RingCentral panel instead of cluttering the panel with multiple contact cards. The dropdown should let staff pick the person or number they want to call or text, then merge that selection into RingCentral Dialer or SMS compose.
At the top of the RingCentral panel, show the Matter communication target as a compact selector. Default order should start with the client, then secondary contact, then adjusters, then other matter-linked contacts with usable phone numbers. Each option should show the person's role, name, and formatted phone number, for example Client: Tanner Hobbs - (502) 492-7300 or Adjuster: Leslee Ahrend - (502) 822-4456.
Below the selector, keep the action buttons simple: Call, SMS, History, Summaries, and Templates where Templates belongs naturally under the SMS workflow. The selected dropdown value becomes the target for Call and SMS. The RingCentral iframe/dialer should open with that selected number, and the logging pipeline should tie activity back to the Matter.
litify_pm__Insurance__c or linked role records after live schema verification.The selector should only include valid phone numbers, format them consistently, and make the chosen recipient visible before staff click Call or SMS. Calls, messages, summaries, transcripts, and inbound replies still need to prove Matter-level logging before this becomes the everyday staff workflow.
When possible, Sam should review Playwright or Browser evidence for every RingCentral Matter panel build so the interface is judged for staff-facing user-friendliness, not only technical pass/fail. Each build pass should still be checked against at least one real example Matter page. The target flow should include opening the Matter, selecting the RingCentral tab, verifying the recipient dropdown options, selecting a non-default recipient when available, opening Call or SMS, confirming the selected number merges into RingCentral, and capturing screenshot evidence. If Browser is unavailable or times out, use Playwright MCP or local Playwright and state the fallback reason.
The intended selector is one flat dropdown of actual Matter contacts, not a category picker with another layer of selections. The visible options should be direct people or organizations with their role and phone number, for example Samantha Jones - Bodily Injury Adjuster - (502) 813-8900. The fallback row should live at the bottom as Other / N/A / Create new... for cases where the person is not already on the Matter. Mock files were created at /Users/samaguiar/Documents/Projects/admin/mockups/ringcentral-recipient-selector/index.html and /Users/samaguiar/Documents/Projects/admin/mockups/ringcentral-recipient-selector/expanded.html; screenshots were captured at /Users/samaguiar/Documents/Projects/admin/mockups/ringcentral-recipient-selector/ringcentral-recipient-selector-mock.png and /Users/samaguiar/Documents/Projects/admin/mockups/ringcentral-recipient-selector/ringcentral-recipient-selector-expanded.png.
Continue with live read-only validation in Litify before implementation. Confirm actual source fields for client, secondary contact, adjusters, and other matter-linked people. Preserve SMS Magic history and rollback safety. Do not delete SMS Magic records, uninstall the package, or disable automation. RingCentral remains the live action surface, and Litify Notes/history remain the durable record trail.