2026-03-02
Technology Options for Morning Star

A modern replacement for unreliable email-to-SMS alerts — designed for fast rollout, reliable delivery, and operational visibility.

Executive summary

Carrier email-to-SMS gateways are increasingly unreliable. Option 1 replaces the SMS delivery step with a simple, mobile-first web app employees install to their Home Screen. Alerts are delivered as push notifications and also stored in an in-app inbox for review and acknowledgment. This is the fastest path to reliable delivery without an app store rollout.

Recommendation: Start with Option 1 for speed (Home Screen Alert Inbox + Push). If Morning Star needs maximum delivery guarantees, upgrade delivery to Option 2 later without losing the platform investment.

Options overview

Option 1 (Recommended)
Fast rollout
Home Screen inbox + push
Option 2
Most reliable
Native apps + APNs/FCM
Option 3
Command Center
Dashboards + permissions + config
Click an option pill below to switch views. ↓

Option 1 (Recommended): Home Screen Alert Inbox + Push

What it is

  • A secure, mobile-first “Alert Inbox” web app optimized for phones.
  • Employees add it to their Home Screen once (iPhone/iPad/Android).
  • Alerts arrive as push notifications and are also written to the inbox (so nothing is lost).
  • Managers get visibility: sent status, acknowledgments, and basic reporting.

How it works

1. Morning Star’s existing system continues to generate an email alert (no workflow disruption).

2. We ingest the email, parse key fields, and create an alert record.

3. The system routes the alert to the right recipients (team, role, or rules).

4. Push notifications are sent to subscribed devices.

5. The alert appears in the inbox where the employee can open and acknowledge it.

6. Managers can view “sent” and “acknowledged” status by user/team.

Timeline (v1)
4–6 days
Inbox + push + basic admin
Timeline (v1.1)
4–6 days
Roles + audit + quiet hours
Field test
~3 weeks
Rollout + enrollment + feedback

Complexity

  • Email variability: different alert email formats require additional parsing rules.
  • Routing rules: “who gets what” can be simple (teams) or detailed (subject/region/on-call).
  • Device enrollment: the smoother we make enrollment, the faster adoption happens.
  • IT/security constraints: SSO, allowed domains, device policy, and access controls.

Next steps

  • Share 10–20 sample alert emails (or screenshots) representing common alert types.
  • Confirm device mix (iOS/Android) and any other device types if needed.
  • Confirm routing: which teams/users should receive which alerts.
  • Confirm success criteria for v1 and any SSO/infrastructure constraints.


© 2026 iQueueRM. All rights reserved.