Sam selected B for now and asked to build C: make the Litify RingCentral panel clearer today and build a real in-panel texting path.
Open in RingCentral instead of Open Text.LitifyRingCentralSmsSender.cls and LitifyRingCentralSmsSenderTest.cls under the Litify Salesforce metadata source.Account.SMS_STOP__c is checked, calls the RingCentral SMS endpoint through callout:RingCentral_SMS, and logs successful sends to SAIL_SMS_Message__c with Direction Outbound, Platform RingCentral, Message Type SMS, body, from number, to number, timestamp, response payload, and Matter or Intake link.litifyRingCentralPanelV2 source so it includes a Reviewed and ready checkbox plus a Send Text button. The direct-send button only enables when the draft is valid, the selected number is a record-backed phone option, and staff checks the confirmation box.RingCentral_Panel_User.permissionset-meta.xml to grant access to the sender class.verify-ringcentral-panel-static.mjs to verify the V2 panel keeps team-friendly labels, removes the old Open Text label, and includes the reviewed-and-ready send gate.0AfUV000001YJdx0AG, one LWC bundle, no component errors.0AfUV000001YJfZ0AW, one LWC bundle, no component errors.0AfUV000001YJZ70AO, 5 of 5 tests passing.0AfUV000001YJaj0AG, components validated: LitifyRingCentralSmsSender, LitifyRingCentralSmsSenderTest, litifyRingCentralPanelV2, and RingCentral_Panel_User; 5 of 5 tests passing; no component failures.node salesforce-metadata/scripts/verify-ringcentral-panel-static.mjs.git diff --check passed on the touched files.RingCentral_SMS Named Credential. Existing Named Credentials are AttorneyShareRestApi, AttorneyShareRestApiProd, LitifyMDAPI, OpenAI Call Logs, OpenAI Treatment Summaries, and Zipliens.Only B is live. Staff should see Open in RingCentral instead of Open Text after Salesforce client-side cache refresh.