How mam-main talks to APNs: HTTP/2 transport via MAM_IosPushSender, .p8 key + JWT auth via MAM_ApnsTokenProvider, payload building via MAM_IosPayloadBuilder, and the separate VoIP path via MAM_IosVoipPushSender.
How mam_forms_manager_phone_manager normalizes phone numbers, validates them via SMS-delivered codes, and ties into both Gravity Forms phone fields and the user-roles phone-code login flow.
How notifications work in MAM Suite: a single mam_notification_send_message action routed by MAM_Notification_Dispatcher to email/SMS/push channels, driven by a notification-type registry with 68+ subscribers.
How sibling plugins register notification types via mam_notification_list. Each type declares its slug, replacement tokens, default-on channels, and description. The dispatcher resolves the message_type to one of these entries.
How each of the three notification channels is sent: wp_mail or queue for email, the global $sms object for SMS, and APNs/FCM via MAM_PushDispatcher for push. Covers the per-channel sender…
Can't find the answer you're looking for? Don't worry we're here to help!