Summary

CallRail started producing many per-call summary notifications. Investigation showed normal CallRail call-alert emails are from no-reply@callrail.com to Sam, while extra CallRail Call Summary - ... messages are self-sent from Sam@kylawoffice.com to both Intake@kylawoffice.com and Sam.

Completed

• Confirmed CallRail has no direct notification record for intake@kylawoffice.com.
• Disabled Sam's duplicate tracker-specific CallRail notification 2206589 by setting call_enabled=false and preserving sms_enabled=true.
• Left Sam's all-calls CallRail notification 2221686 enabled so one normal CallRail alert should remain.
• Created Sam mailbox rule CallRail self-sent summaries - file and silence.
• Rule criteria: from Sam@kylawoffice.com, subject contains CallRail Call Summary.
• Rule action: mark read, move to Inbox/CallRail Calls, stop processing.
• Filed 12 existing matching self-sent summary messages from Sam's Inbox.

Findings

• Intake@kylawoffice.com is a Microsoft 365 Unified Group, not a normal mailbox. A mailbox Inbox rule cannot be attached to it.
• The source automation sending the self-sent summaries was not found in local scheduled tasks or local project files.
• The matching self-sent summaries are not saved in Sam's Sent Items, which suggests a cloud workflow or app sends as Sam without saving sent copies.

Artifact Folder

C:\Users\SAguiar\Documents\Codex\Outlook-CallRail

Key files:

• callrail-summary-notification-handoff-2026-04-27.md
• callrail-notifications-before-2026-04-27.json
• callrail-notifications-after-2026-04-27.json