Sam said "you choose" after the options around RingCentral's AI subprocessor notice. I chose the practical middle path: add a read-only RingCentral account settings / AI-product audit as a required first inventory lane.
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-12.mdThe next agent should confirm, read-only, whether AI Receptionist, AIR, AIR Pro, AI summaries, AI message drafting, or other AI communications features are enabled in the live RingCentral account. The finding should be saved with the deployment/rollback QA packet.
A passive checkpoint is too easy to skip. Asking the rep first may be useful later, but the first move should be direct account-state verification because the project already requires live RingCentral/SMS Magic inventory. This choice keeps the migration moving and documents AI/privacy posture before go-live.
No RingCentral settings should be changed during this audit. The initial RingCentral V2 Salesforce panel remains user-initiated unless a separate AI-product approval is documented. Do not use RingCentral AI for automated intake, after-hours answering, summaries, message generation, or client-facing replies until AI status, DPA/BAA posture, and subprocessor implications are verified.
The decision was made and reflected in the handoff, QA queue, and Notion. No live Salesforce or RingCentral configuration was changed.
During Phase 1 inventory, run the RingCentral account settings / AI-product lane in parallel with Salesforce SMS Magic metadata inventory.