Custom sound alerts

This plays a chosen sound on a device so an alert is heard, not just seen. A Beam agent watches for the event you tied to a Vybit alert, reads the incoming data, and fires the matching sound notification when your rule is met. Different events can map to different sounds so people know the meaning by ear. Each fire is recorded so you can audit what went out. Events that arrive too fast, or that your rule cannot classify, are held and passed to a person to avoid alert fatigue.

Notification triggers

This defines what conditions raise a Vybit alert. A Beam agent reads a stream of events from your connected tools, applies the trigger rules you approved, and sends a notification only when the conditions truly match. Thresholds, quiet hours, and priorities you set are honored. The agent writes a record of which trigger fired and why. When events are contradictory, or a new kind of event appears that no rule covers, the agent notifies a person to decide whether a fresh trigger is needed rather than staying silent.

Event subscriptions

This manages which sources a Vybit alert listens to. A Beam agent reads your subscription settings, links each source to the right sound and rule, and updates subscriptions as tools are added or retired within the permissions your account allows. Duplicate or noisy sources can be muted per the rules you set. Changes are written back so the whole setup stays auditable later. A source that starts sending unexpected data, or one that needs access the agent does not currently hold, is flagged for a person to configure safely by hand.