Sam asked whether the handoff removes the SMS tabs and rows and adds RingCentral. I clarified that the intent is to add/finish RingCentral and retire SMS Magic staff-facing UI only after RingCentral QA, while preserving all SMS Magic data.
Yes, the planned end state is that RingCentral becomes the active Matter/Intake communications surface. Old SMS Magic staff-facing surfaces can be hidden or removed from the active workspace after QA, including tabs, send/conversation components, active related-list placement, and layout fields that invite SMS Magic sending.
No, the handoff does not delete SMS Magic records or historical rows. It does not uninstall SMS Magic. It does not disable SMS automation until current writers are traced and RingCentral replacement logging is verified. Historical SMS history must remain queryable and available through read-only archive/report/timeline access.
admin/handoffs/HANDOFF-ringcentral-matter-tab-important-details-2026-05-01.mdadmin/handoffs/HANDOFF-sms-magic-retirement-ringcentral-v2-2026-05-12.mdadmin/_qa-queue/2026-05-13.mdIf the smsmagics__r related list or SMS Magic tab is removed from active Matter/Party UI, a read-only historical route should remain. RingCentral should be the active call/message workflow, while legacy SMS Magic is treated as archive/history.
The ambiguity was clarified and persisted in the handoffs and QA queue. No live Salesforce metadata or records were changed.
During implementation, keep the SMS Magic related list visible until a verified archive/report/timeline route exists, unless the team explicitly accepts report-only history access.