The notification center is the unified inbox for every event the portal produces — a new invoice, a shipped device, a suspicious login attempt, a plan edit, a crossed usage threshold. Each notification routes through a user's preferred channels (push, SMS, email, portal banner) according to category-level preferences and quiet-hour rules. The goal is simple: every relevant event reaches the right person, and nothing important slips through the cracks.
Administrators set organization-wide default preferences during onboarding. Users customize their personal subscriptions after Verizon Business Login. Critical alerts override quiet hours automatically so a security incident at 3 AM still gets through, while routine billing notifications wait politely for the morning. The notification center also acts as a searchable archive — every notification from the last 18 months is retrievable through the portal.
Configure Preferences Usage Alerts
Every My Verizon Business event maps to one of five categories. Each has its own subscribers, channels, and quiet-hour behavior.
Billing notifications fire on statement-ready, payment-due, payment-posted, and overage events. Device notifications fire on upgrade-eligibility, order-shipped, activation-status, and trade-in-complete events. These alerts typically route to the line user (their invoice, their device) with copies to the administrator and, for billing, the accounting contact. They rarely need push priority — email is the default channel, with SMS reserved for time-sensitive payment-due alerts.
Security notifications fire on new-location login, MFA prompt, password change, and suspicious-activity detection. Plan notifications fire on plan change applied, line added or removed, and pool edit. Usage notifications fire on threshold crossings, roaming connections, and anomaly detections — see usage alerts for the full taxonomy. Security events always route through high-priority channels and override quiet hours by default under CISA-aligned incident response practice.
Each event type has a default channel assignment that balances urgency against inbox noise. Users override defaults per their preference.
| Category | Example Events | Default Push | Default SMS | Default Email | Portal Banner | Quiet Hours |
|---|---|---|---|---|---|---|
| Billing | Statement ready, payment due | Off | On (payment due only) | On | On | Respect |
| Device | Shipment, activation, trade-in | On | Off | On | On | Respect |
| Security | New location login, MFA, suspicious activity | On | On | On | On | Override (critical) |
| Plan | Plan change, line add/remove, pool edit | Off | Off | On | On | Respect |
| Usage — Threshold | 75/90/100% crossings | On | On (100% only) | On | On | Respect |
| Usage — Roaming | Foreign network detected | On | On | On | On | Override (first connect) |
| Usage — Anomaly | 3x baseline spike | Off (admin only) | Off | On | On | Respect |
| Hard-Cap Action | Data suspension triggered | On | On | On | On | Override (critical) |
Default channel settings configurable by administrator at onboarding. Security category defaults align with NIST cybersecurity framework recommendations for alert timeliness.
Quiet hours keep the notification center useful instead of noisy — and preserve the critical-alert override when minutes matter.
Users set quiet hours in the notification preferences panel — typically 7 PM to 7 AM weekdays and all-day weekends. During quiet hours, push and SMS notifications are suppressed. Email and portal banners continue as usual, because they accumulate in inboxes without interrupting the user. Time zones follow the user's profile configuration, so a field engineer in Mountain Time sees quiet hours at 7 PM MT while a head-office administrator in Eastern Time sees quiet hours at 7 PM ET. Organization-wide default quiet hours can be set by the administrator, with users free to widen or narrow the window for themselves.
Certain alerts are too important to defer: a login from an unusual geography, a hard-cap data suspension, a confirmed security incident. These "critical" categories override quiet hours by default, routing push and SMS immediately regardless of the user's window. Users can opt out of critical overrides for specific categories, but the administrator can lock the override for regulated industries — healthcare, finance, public safety — where prompt awareness of security events is a compliance requirement. Lock status appears as a padlock icon next to the category in the preferences view.
Notifications aggregate events from every module in the portal — and every module links back to the notification center.
Threshold crossings, roaming detections, and anomaly flags feed into Usage notifications. See usage alerts for threshold configuration and shared data for pool-level thresholds.
Add Line, Device Upgrade, Line Swap, and International Roaming each emit Plan and Device notifications when their workflows complete. Activation events feed back into the My Biz app push.
Login attempts, MFA prompts, password changes, and suspicious activity feed Security notifications. Critical priority overrides quiet hours. See mobile security.
Every notification lives in the archive for 18 months so nothing is lost and every event is searchable after the fact.
The notification archive in My Verizon Business indexes every event by category, line, timestamp, and channel. Administrators search "device shipment" from the past 30 days to see all activations in flight, or "suspicious activity" across the past quarter for a security review. Archive access respects role-based permissions — line users see their own archive only, managers see their team's archive, administrators see the organization. All archive access is logged per FCC CPNI audit requirements.
Every notification records delivery outcomes per channel — push delivered, SMS delivered, email bounced, portal banner acknowledged. Failed deliveries automatically retry and then fall back to an alternate channel. The delivery log surfaces any channel-level issues (a stale email address, an SMS delivery problem on a specific carrier) so the administrator can correct the user profile before important alerts are missed. Delivery logs export through expense reports as part of the portal activity audit.
Categories, channels, quiet hours, and user-versus-administrator preferences.
Five: Billing, Device, Security, Plan, and Usage. Each subscribes independently. See usage alerts for the Usage taxonomy.
Push in the My Biz app, SMS, email, and in-portal banner. Per-category channel preferences with administrator defaults.
Yes. Quiet hours pause push and SMS during user-defined windows. Email and portal continue. Critical alerts override. Time zones follow the user profile.
Per user by default, with administrator-set organization defaults and optional lock on mandatory categories (security, hard-cap) for regulated industries.
Five minutes after Verizon Business Login is enough to move from default noise to a tuned alert stream. Open Notifications, pick your categories, set quiet hours, and confirm channel preferences.
Login Guide Contact Support