Sam asked whether SMS is currently attached to SMS Magic, whether the deprecated SMS Magic app should be replaced by RingCentral, and whether it makes sense for RingCentral to take over the Matter/Intake communications surface with iframe functions and chat-bubble style conversations.
admin/handoffs/HANDOFF-ringcentral-matter-tab-important-details-2026-05-01.md.LITIFY_ORG.smagicinteract__smsMagic__c exists live as SMS History.SMS-Magic Converse, namespace smagicinteract, version 1.68.41-Release.rc_sf_package, namespace rcsfl, version 6.43.2.litifyRingCentralPanel and LitifyRingCentralContextController already support Matter/Intake context, Important Details, phone selection, RingCentral iframe, call, text, and dialer actions.Yes, Sam's idea makes sense. SMS Magic should be treated as the legacy/historical SMS record source, not the future staff-facing communications source. RingCentral should become the primary communications surface, but the cutover should be staged because SMS-related Tasks are still being created today and old SMS Magic records need to remain queryable for history.
The best implementation path is a RingCentral Matter/Intake tab beside Case Status, using the existing staged litifyRingCentralPanel foundation. It should show Important Details at the top, then RingCentral actions, then a staff-friendly message/call conversation view. The RingCentral iframe can provide native RingCentral app functions, while a separate Salesforce-rendered conversation layer can make historical messages/calls appear as chat bubbles.
No live changes were made in this session. This was a validation and product-direction check only.