Sam reported receiving a RingCentral legal notice that the RingCentral Subprocessor List was updated for RingCentral AI Receptionist and RingCentral AI Representative (AIR Pro). I verified RingCentral's public subprocessor/FAQ sources and added this as a checkpoint to the active RingCentral/SMS Magic handoffs.
RingCentral's public FAQ says subprocessor update notices are legal notices provided as required by law and generally require no customer action. The public RingCentral Subprocessor List recent-changes section shows AI Representative (AIR Pro) added on March 16, 2026, and AI Receptionist standalone updates on January 31, 2026.
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 notice does not block the current user-initiated RingCentral panel by itself. The staged panel embeds RingCentral and lets users initiate call/text actions; it does not enable AI Receptionist or AIR Pro.
It does create a required privacy/vendor-risk checkpoint before RingCentral becomes the primary communications source, especially if the firm later uses automated intake, after-hours answering, call summaries, message generation, or client-facing AI replies.
Before go-live, verify whether AI Receptionist, AIR, or AIR Pro is enabled in the actual RingCentral account. Document whether client communications, call audio, transcripts, SMS bodies, or intake facts may be processed by AI subprocessors. Confirm the applicable DPA/BAA posture before any AI-product use.
The notice was triaged and added to the handoff/QA record. No live Salesforce or RingCentral configuration was changed.
During RingCentral V2 live inventory, add a RingCentral account settings check for enabled AI products and export the result into the same rollback/QA packet as the SMS Magic retirement inventory.