How email, SMS, and push notifications are queued and drained by the mail-cron-manager subsystem. Covers the wp_mam_mail_queue and wp_mam_sms_queue tables, the per-tick batch sizes (50 email / 20 PN+SMS), and…
How wp_mam_notification_history records every dispatch, how the in-app notification center reads it, and the opt-out tables (per-user email opt-out, SMS STOP, push permission revocation).
How replacement tokens (e.g., [user_login], [passwordcode], [order_id]) work in notification templates: per-type token list declared in mam_notification_list, supplied at fire time, substituted by the channel sender.
MAM_Phone_Data_Pipeline is the canonical builder of the mobile app’s JSON payload. 4 phases (auth → settings → content → finalize), state carried by MAM_Phone_Data_Context, ~70 sibling-plugin subscribers via the legacy…
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.
Can’t find the answer you’re looking for? Don’t worry we’re here to help!