Session Objective

Answer why a drafted client text in Litify cannot be pushed and sent directly from the visible Litify panel.

What Was Checked

• Loaded litify-workup and followed the required live-org grounding step.
• Confirmed LITIFY_ORG is connected through Salesforce CLI.
• Ran a live Matter query to ground the session in Salesforce.
• Queried live QuickActionDefinition metadata for SMS and RingCentral actions.
• Queried live LightningComponentBundle metadata and confirmed both litifyRingCentralPanel and litifyRingCentralPanelV2 are deployed.
• Checked current communication object counts: SAIL_SMS_Message__c, smagicinteract__smsMagic__c, and RingCentral SMS Tasks.
• Checked the relevant client Account record at a high level and confirmed the SMS stop flag is false, with the expected phone/mobile value present.
• Reviewed local source for the visible panel: litifyRingCentralPanelV2.html and litifyRingCentralPanelV2.js.

Answer

The screen is intentionally built as an opener/bridge to RingCentral, not as a direct Litify SMS sender. The Open Text button calls handleOpenRingCentralText(), which passes the draft to openRingCentralAction(WORKSPACE_SMS, this.smsDraft). That then builds a RingCentral web app URL under /r/sms with query parameters for the phone number and message content and opens it in a new browser window. There is no Apex or RingCentral API send call in that button path.

Why This Matters

This behavior preserves final human review inside RingCentral, keeps the send under the logged-in RingCentral user/session, and avoids an outbound API-send path from Litify. Prior RingCentral/SMS work also maintained a safety floor against outbound API sends/replies without explicit approval. It is not a Sondra-specific opt-out issue based on the live record check.

Current Evidence

• sf org list --all: LITIFY_ORG connected.
• Live QuickActionDefinition: SMS with RingCentral exists for Account, Contact, and Lead. No Matter-specific RingCentral SMS quick action was shown in that query.
• Live component metadata: litifyRingCentralPanel and litifyRingCentralPanelV2 both deployed.
• SAIL_SMS_Message__c: 361 rows.