Sam asked to keep pushing the RingCentral replacement so staff can call and text from the Matter, see call summaries/transcripts cleanly, keep SMS Magic data without keeping the old staff UI, and make mobile better than a standalone RingCentral app.
This session continued the staged hybrid A + C path. The production Matter sidebar now has RingCentral before Case Status, the old SMS tab is removed from the visible menu, and SMS Magic records/package/automation were not deleted, uninstalled, disabled, or altered.
The RingCentral panel now has a staff-facing workspace: Summaries, Call, SMS, Templates, and History. Summaries stay as the home view and show clean call cards such as Call with Leslee Ahrend, source label Call Summary, date/time, cleaned summary text, and real buttons for Summary, Transcript, and Open Note. The Matter name is not repeated inside the panel, and the phone target is simplified to the full Matter phone number.
A mobile-focused parallel read-only agent reviewed the architecture. Its recommendation matched the implementation direction: desktop/tablet should use RingCentral Embeddable, while phone form factor should use a Salesforce-native command hub and RingCentral mobile app deep links for actual telephony. The LWC now declares Large and Small form factors. On Salesforce phone form factor, Call opens rcmobile://call?number=..., SMS opens rcmobile://sms?number=..., History opens rcmobile://history, and Templates stays native in Salesforce.
A Quick Text-backed template hook is live. Apex loads up to 25 insertable QuickText records into the panel, and the LWC renders template cards with copy actions when templates exist. Live org count is currently 0 QuickText rows, so the feature is ready for a seeded firm/personal template library but does not invent content yet.
Playwright QA exposed RingCentral's FOR DEMO PURPOSES ONLY banner in the embedded app. Official RingCentral Embeddable docs say the production fix is to use a registered app clientId. The existing RingCentral client ID was found in the local vault and wired into the iframe URL. Only the client ID was used, not the client secret. After a fresh Salesforce route load, Playwright verified the iframe source includes clientId=... and the screenshot no longer shows the demo banner.
0AfUV000001Wlxh0AC; components deployed 3; tests completed 3; test errors 0.0AfUV000001Wm2X0AS; components validated 1; errors 0.0AfUV000001Wm490AC; components deployed 1; errors 0.clientId and SMS template flags: Repos/sail-litify/Litify_AI_Integration_Project/salesforce-metadata/tmp/ringcentral-clientid-live-verify-2026-05-14/.Repos/sail-litify/Litify_AI_Integration_Project/salesforce-metadata/tmp/ringcentral-clientid-2026-05-14/rollback/.Repos/sail-litify/Litify_AI_Integration_Project/salesforce-metadata/tmp/ringcentral-mobile-hub-2026-05-14/rollback/.ringcentral-panel-final-summaries-2026-05-14.png, ringcentral-panel-clientid-templates-2026-05-14.png, ringcentral-panel-mobile-web-2026-05-14.png.SAIL_SMS_Message__c = 351, inbound 187, outbound 164, QuickText = 0.admin/_qa-queue/2026-05-14.md.The core UI/mobile foundation and demo-banner correction shipped to production with rollback points and fresh validation. The remaining work requires controlled real-world communication tests or seeded staff template content rather than more blind UI polish.