Sam approved a refined QA standard for RingCentral Matter panel work. The key point is that Browser or Playwright evidence is not just technical validation. When possible, Sam should review the proof so the build is judged for staff-facing user-friendliness on an actual Matter page.
Recommended QA gate: when possible, Sam reviews Playwright or Browser evidence for every RingCentral Matter panel build to ensure staff-facing user-friendliness and to confirm it works on an actual Matter page.
The existing Notion decision page RingCentral Matter Recipient Selector Decision - 2026-05-17 was updated under the Browser QA Requirement section with the revised standard.
For the next RingCentral build pass, validate the UI on at least one real Matter page with Browser or Playwright. The proof should show the Matter page, RingCentral tab, recipient selector, selected recipient behavior, Call or SMS action, and whether the chosen number merges into RingCentral. Share the screenshot or Browser evidence for Sam review when possible. Preserve SMS Magic records and history. Do not uninstall SMS Magic, delete SMS Magic data, or disable automation. RingCentral remains the live action surface; Litify Notes/history remain the durable record trail.
Proceed with live read-only field discovery for the flat recipient selector, then implement the selector behind a reversible deployment path and validate it with Playwright or Browser evidence on a real Matter page.