Page change detection

This flags visual or text differences on a web page since its last check. A Beam agent watches the pages you register, reads the current version, and compares it against the stored baseline using the sensitivity rule you approved. When a real change appears, the agent records it and notifies the owner or opens a task in your workflow. Purely cosmetic shifts below your threshold are ignored. When a change is large or hard to classify, the agent leaves the page flagged and routes it to a person to decide whether it truly matters for the team.

Alert routing

This decides who hears about a detected change and how. Once the agent confirms a page moved, it reads your routing rule and sends the alert to the right channel, inbox, or ticket, attaching a before and after snapshot. Repeated low-value changes on the same page can be grouped so nobody gets spammed. The agent updates the change log with what was sent and when. If a page keeps changing in ways your rule cannot categorize, the agent escalates the pattern to a person to adjust the monitor or mute it entirely.

Monitoring schedules

This controls how often each page is checked. A Beam agent reads the frequency you set per page, runs the check on that cadence, and stores each result against the page history. When a site starts blocking checks or returns errors, the agent notes the failures and retries within the limits your account permits. It updates the schedule status so you can see which monitors are healthy. Persistent failures, login walls, or pages that need credentials are routed to a person, since the agent will not guess at access it was never given.