Email, Text & Push Notifications
Types of messages
Authentication and account-security emails support account access. Work-related alerts may concern messages and confirmed arrangements. Marketing permissions must remain separate from operational alerts; do not treat account creation as blanket marketing consent.
Text alerts
The approved publication flow requires a verified mobile number and affirmative acknowledgement of work-alert texts. Telnyx activation remains pending. Final sender identity, message frequency, carrier-charge disclosure, STOP/HELP instructions and consent records must be validated before live texting. Marketing-text rules require separate review.
Installed-app notifications
Adding GIGtrunk to the home screen does not itself grant push permission. The user must approve notifications. The intended routing prefers an enabled installed-app subscription and suppresses duplicate texts after a successful push-provider acceptance, with existing consent and STOP protections applying to fallback texts. Push readiness and real-device tests are still pending.
Choices and delivery
Browser/phone settings control push permission. STOP must suppress texts; changing notification channels must not undo an opt-out. Alerts can be delayed or missed and are not an emergency channel. Marketing unsubscribe and operational preference controls must reflect actual available functionality.