Account Notifications
Qu'est-ce que Account Notifications?
Cette entrée n'est actuellement disponible qu'en anglais.
Account notifications are the automated alerts a platform sends to a business account's own users — its operators and admins — about the state of that account: a balance running low, a payment failure, a sender ID decision, a webhook endpoint that stopped accepting events, or a system update. Unlike the customer-facing notifications a business sends to its own end users (order updates, appointment reminders), account notifications stay inside the business, telling the team when something needs their attention before it interrupts service.
More detail
The distinction that matters at setup is direction: account notifications flow from the platform to the business's team, while the messages the business sends onward — order confirmations, delivery updates, OTPs — flow to its end users. A low-balance alert or an auto-paused webhook endpoint is an account notification; the shipping update a customer receives is a transactional customer notification. Platforms that keep the two directions clearly separated let operators subscribe teammates to account alerts without touching the customer-facing traffic at all.
Common account notifications fall into three groups: financial (credits running low, a top-up that failed, spend hitting a configured threshold, a wallet that emptied and paused outbound traffic), compliance and configuration (a sender ID or brand registration decision, a KYC verdict, a phone-number porting status change), and operational (a webhook endpoint disabled after repeated delivery failures, a campaign that finished or failed, a security or system incident). Each is only useful if it reaches the right teammate quickly — an empty wallet or a dead webhook endpoint already costs money by the time someone finds it in a report.
On Devotel Orbit, account notifications land in two places: the in-dashboard Notification Center, which fans account events out to the organization's operators with severity levels and per-kind filters, and the billing-alerts surface, where an admin sets spend and balance thresholds and picks the email list and the on-hit action — notify only, or pause outbound traffic when a threshold trips.
Questions fréquentes
- What counts as an account notification?
- Anything the platform tells the business's own team rather than its customers: low-balance and payment alerts, spend-threshold trips, sender-ID and registration decisions, porting status changes, disabled webhook endpoints, completed or failed campaigns, and system or security notices. Customer-facing traffic — order updates, appointment reminders, OTPs — is a separate, transactional notification class.
- Who receives account notifications?
- Whichever teammates the organization designates. In-app notification centers typically fan events out to all operators with a severity and kind filter to cut the noise, while threshold-based billing alerts email a curated list — a capped set of addresses, not the whole staff directory — so a balance trip reaches finance and operations without paging everyone.
- How do account notifications differ from transactional notifications to customers?
- Direction and consent. Account notifications go from the platform to the business's own team and need no end-user consent — they are operational alerts inside the account. Transactional notifications (order confirmations, delivery updates, OTPs) go from the business to its end users over SMS, WhatsApp, or email, and inherit the recipient-consent and quiet-hours rules of that traffic's regulatory regime.
See also
Build it on Orbit
Voice, messaging, email, video, and AI agents on one platform and one pay-as-you-go bill. Start free — no credit card required.