What it does

mam-contact-form adds a Contact Us form to a MAM mobile app. The form can be placed on the main tab bar or in the left menu, and submissions trigger a configurable admin email notification.

The default form ships with six logical fields — Name, Email, Phone, Contact Reason, Subject, Description. Name, Email, and Phone are auto-populated from the signed-in user’s WordPress profile. Developers can add custom fields via filter without modifying core files, and a Contact Reason field lets a single form route different submissions to different notifications.

The plugin is no-code first and low-code where it matters. Most installations only need a notification email and a placement in App Setup; everything else is optional. The same person typically wears both hats — admin to configure, developer to extend — so the recipes and hook references in this codex are designed to hand off to one another.

Setup paths

mam-contact-form supports two ways to define the form. Pick one based on your customization needs.

Default path — built-in form handler. The plugin ships with a built-in handler that mirrors the Gravity Forms structure. No external plugin is required. The default fields are pre-configured, including the correct mobile keyboards for Phone and Email. Custom fields can still be added programmatically via PHP filter. Use this for most installations. See Recipe: Setting up a contact form (default path).

Gravity Forms path. If you want to design the form in Gravity Forms — drag-and-drop fields, conditional logic, the full Gravity Forms feature set — install Gravity Forms and the MAM Gravity Forms plugin. Submissions then flow through Gravity Forms instead of the built-in handler. See Recipe: Setting up a contact form with Gravity Forms.

The hooks listed below work identically on both paths. The same is true for admin features like Contact Reason routing.

Where it appears in the app

The form is rendered by vc_form_manager on iOS and the equivalent form activity on Android. It is reached from:

• A main navigation tab item (when configured as a tab)
• A left menu entry (when configured as a menu item)

Both placements are configured in Mobile App Manager → App Setup. The same Gravity Forms form ID is reused regardless of placement; you do not need to define the form twice.

Requirements

• WordPress 6.3+
• PHP 8.1+
• MAM Suite with mam-main activated
• MAM Suite plugin entitlement for mam-contact-form

The Gravity Forms path additionally requires:

• Gravity Forms (any current version)
• MAM Gravity Forms plugin — the bridge between Gravity Forms and the MAM form handler

If mam-main is not active, the plugin silently exits in its constructor (entitlement guard). If mam-gravity-forms-manager is missing, mam_gf_get_form returns an empty array and submission processing returns an error response.

Default fields

On the default path, Phone and Email fields are pre-configured with the correct mobile keyboards. On the Gravity Forms path, you must manually set special_handling on each field — see Recipe: Setting up a contact form with Gravity Forms.

The Contact Reason field is optional in practice. If the Reason field ID option (mam-contact-formcontact_form_reason) is not stored, the routing UI is hidden and submissions flow to a single notification.

Hooks exposed

Each hook has its own dedicated article. See Related articles.

Mobile JSON contract

mam-contact-form does not write directly into the top-level mobile JSON payload. Instead, it contributes to the Gravity Forms-shaped form structure that mam-gravity-forms-manager exposes to the app. The keys it sets are part of the frozen mobile contract — renaming them will break deployed apps.

Submission responses use this shape:

WordPress options used

The plugin reads and writes a small set of options. These are stored in client databases — Tier 1 frozen, do not rename without a migration.

The leading prefix mam-contact-form and the body (e.g., contact_form) are concatenated without a separator. This is consistent within the plugin but easy to misread.

Common tasks

• Set up the form using the built-in handler → Recipe: Setting up a contact form (default path)
• Set up the form using Gravity Forms → Recipe: Setting up a contact form with Gravity Forms
• Route different submissions to different notifications → Recipe: Enabling multiple contact reason types
• Add address fields (Street/City/State/ZIP) → Hook: mam_gf_get_form_settings_fields_contact_form
• Send submissions to a CRM after processing → Hook: mam_contact_form_contact_processed
• Pre-fill custom fields with values from the user profile → Hook: mam_contact_form_populate_contact

Verification

This article was last verified against:

• Plugin: mam-contact-form v2.1
• Source: mam-contact-form/mam-contact-form.php
• Source: mam-contact-form/includes/admin-settings.php
• mam-main (required)
• mam-gravity-forms-manager (required for the Gravity Forms path)

Re-verify whenever a hook is added or removed, the default field list in get_fields() changes, the option-key naming scheme above changes, the submission response shape returned by process_contact_form() changes, or either setup path’s admin UI is reorganized.

Related articles

• Recipe: Setting up a contact form (default path)
• Recipe: Setting up a contact form with Gravity Forms
• Recipe: Enabling multiple contact reason types
• Hook: mam_gf_get_form_settings_fields_contact_form
• Hook: mam_contact_form_contact_processed
• Hook: mam_contact_form_populate_contact

Metadata