Session overview

Objective: determine whether RingCentral text-message emails were spam, reduce the Outlook inbox noise safely, and produce a sheet with all of the text-message emails.

What was completed

• Confirmed the emails were legitimate RingCentral notifications rather than a spoofed spam run.
• Created Inbox/Vendors/RingCentral/Text Messages in Outlook.
• Created the Outlook rule Auto-file RingCentral Text Messages targeting messages from service@ringcentral.com with New Text Message in the subject.
• Moved the current unread Inbox matches into the new folder.
• Exported the full direct text-notification history to a native Google Sheet with Summary and Messages tabs.

What was tried and did not work

• The Outlook connector write action returned 403 ErrorAccessDenied, so the connector could not create the folder/rule or move mail directly.
• The session switched to the local Microsoft Graph path for mailbox writes.
• A Graph follow-up inbox query briefly hit a URL-encoding bug during verification, but the already-created folder and rule were confirmed and the current-message sweep was completed afterward.

Decisions and reasoning

• The correct action was to organize the RingCentral text notifications, not delete them, because the underlying texts were mixed and at least one looked like a legitimate human/business message.
• The rule intentionally targets only direct text-notification emails from service@ringcentral.com with New Text Message in the subject, so it does not touch RingCentral voicemails from notify@ringcentral.com or coworker-forwarded mail.
• The sheet deliverable covered text-message notifications only, not voicemails.

Files, URLs, source systems, and exact artifact locations

• Source system: Sam Aguiar Outlook mailbox via Microsoft Graph.
• Google Sheet: https://docs.google.com/spreadsheets/d/1hLoS_w0uGnEMWqD5e-HLQRk_FM7yZT_edfKLjSGssg4/edit
• Rule creation artifact: /Users/samaguiar/Documents/Projects/admin/outlook-audits/ringcentral-text-rule-20260525T154304Z.json