Operational notifications
Billing, phone-number, Meta-connection, and webhook-endpoint alerts for the people operating your integration. Manage recipients and channel preferences in the dashboard.
Email and dashboard notifications are enabled by default. WhatsApp, Slack, and SMS require explicit configuration.
Repeated alerts
Repeated occurrences of the same event for the same resource in an organization are grouped for each recipient and external channel during a six-hour cooldown. The first eligible occurrence can send immediately. Repeats do not send another email, WhatsApp, Slack, or SMS notification inside that window. A repeat does not extend the cooldown.
The dashboard retains every occurrence. Email digests summarize grouped email occurrences with a count and the first occurrence time, for example: “and 7 more since 2026-09-05T10:00:00.000Z”. This summary is sent even if no further event arrives after the cooldown. Other external channels keep their existing message formats; the detailed history remains available in the dashboard.
Email budget and digests
Each organization recipient can receive up to five individual operational emails in a rolling 24-hour period. Pending sends and failed attempts reserve capacity while they can still be retried. Overflow waits for one end-of-day email digest, due at the next midnight UTC. That summary is additional to the five individual emails. Quiet hours delay a due digest until sending is allowed.
If you choose daily digest explicitly, delivery is scheduled for 09:00 in the configured timezone, or UTC when none is set. There is at most one digest per recipient per UTC day; arrivals after its contents have been prepared wait for the following digest. Large digests show the first 100 entries and the exact number of remaining occurrences, with the complete history in the dashboard.
A queued digest checks current recipient and channel preferences before sending. Changing its recipient address or disabling an included notification suppresses that prepared summary. Provider failures are retried with the same contents.
Transactional exceptions
The signup welcome and rental funding-required, release-scheduled, and released-for-non-payment notifications bypass cooldowns, the individual email budget, digest cadence, quiet hours, and the emergency email ceiling. Their existing recipient and channel settings still apply.
A platform emergency ceiling may suppress operational emails, including digests, during a notification storm. It alerts Tyxter operators and leaves the dashboard history available. These controls do not change customer webhook subscriptions or the WhatsApp messages sent through the messaging API.