Contact Form
Members fill in your Contact Form 7 forms on a native screen. Each message goes through Contact Form 7 on your site, so it gets the same checks and the same email as the same form on your website. With Flamingo active, Contact Messages shows members the messages they sent from the app, and shows the people who manage your inbox everyone’s.
Before you start
Section titled “Before you start”| Plugin | Contact Form 7 5.9 or newer. Contact Messages also needs Flamingo |
| Endpoint groups | Contact Form 7, and Contact Form Messages for Contact Messages |
| Plan | Every plan |
Placing the features switches their groups on for you when your site is connected. Otherwise turn them on under Memberside → REST API.
Add it to your app
Section titled “Add it to your app”Drag Contact Form onto a navigation bar or into the side drawer, then open its settings and tick the forms it offers. With one form, the screen opens straight into it. With several, members see a list and tap one to open it.
To put a form on a screen you design, use the Contact Form block instead.
Settings
Section titled “Settings”| Setting | What it does | Default |
|---|---|---|
| Title, Description | Shown at the top | Empty |
| Forms | Which of your forms the screen offers, in the order you tick them | None |
| Who can send | The roles that may send the forms. Signed-in members means every role; Visitors lets people who are not signed in send them too | Signed-in members |
| Ask visitors to pass Turnstile | Cloudflare’s challenge before a signed-out message is sent. Shown when Visitors can send | Off |
| Restrictions | Who can open the screen | Everyone |
Who can send, and how your site enforces it
Section titled “Who can send, and how your site enforces it”Your site keeps the rules for each app: a form is closed to anyone not on its Who can send list, and closed altogether to an app you have not placed it in. Saving the app sends the rules to your site. Removing the last screen or block that offers a form closes it again.
People who can edit forms in Contact Form 7, such as administrators, can always
send one. A form with subscribers_only: on in its Additional Settings still
refuses visitors, whatever the app allows.
What members see
Section titled “What members see”Fields are drawn natively with your app’s typography and colours. The label
above each field is the text your form template puts in front of it, so
<label> Your name [text* your-name] </label> shows Your name.
A field that fails a check shows the same message under it that your website would: a missing required field, an email that is not an email, a number or a date outside its range, text over its maximum length, a file of the wrong type or size. Your site checks the message again when it arrives, so a check another plugin adds to Contact Form 7 still applies.
After a message is sent, the form clears and shows your form’s own Thank you for your message text.
Fields the app draws
Section titled “Fields the app draws”Text, email, URL, telephone, number, range, date, text area, drop-down menu
(including multiple choice), checkboxes and radio buttons (including
free_text), acceptance, quiz, file and hidden.
A form that also uses a field the app cannot draw — a Stripe payment, a Really Simple CAPTCHA image or a field from another plugin — shows a notice instead of the form, because half a form would send the wrong thing. Keep those forms on your website.
Spam protection
Section titled “Spam protection”Contact Form 7’s reCAPTCHA and Turnstile need a browser to make their token, and the app has none. A member who is signed in, or a visitor who passed the app’s own Turnstile challenge, is let past those two checks for that one message. Akismet and your Disallowed Comment Keys still check every message.
A visitor the app has not checked meets reCAPTCHA or Turnstile exactly as on the website, and fails it. So if your form uses either and you let visitors send it, turn on Ask visitors to pass Turnstile and add the Turnstile keys under Memberside → API Keys.
Contact Messages
Section titled “Contact Messages”Contact Form 7 keeps nothing it sends; it only emails. Install Flamingo to keep every message on your site, then drag Contact Messages onto a navigation bar or into the side drawer and tick the forms whose messages it lists.
Members see the messages they sent from the app, newest first, and tap one to read every answer. People who manage Flamingo’s inbox on your site also get a Mine | All switch, which lists everyone’s messages for those forms, including ones sent from your website, and can delete a message. Delete moves it to Flamingo’s trash, where you can restore it.
| Setting | What it does | Default |
|---|---|---|
| Title, Description | Shown at the top | Empty |
| Forms | Whose messages the screen lists | None |
| Restrictions | Who can open the screen | Everyone |
When something goes wrong
Section titled “When something goes wrong”| What you see | Why | What to do |
|---|---|---|
| Sign in to fill in this form. | The form is not open to visitors | Add Visitors to Who can send |
| A visitor’s message is refused as spam | The form uses reCAPTCHA or Turnstile in Contact Form 7, and the app did not check the visitor | Turn on Ask visitors to pass Turnstile |
| There was an error trying to send your message. | Contact Form 7 could not send the email. Flamingo still kept the message | Check your site’s mail settings |
| A message sent from your website is missing from a member’s list | Contact Form 7 sends website messages without saying who sent them | Nothing to fix: members see what they sent from the app. Inbox managers see website messages under All |
| This site is not keeping messages yet. | Flamingo is not active, or the Contact Form Messages endpoints are off | Activate Flamingo and turn the group on under Memberside → REST API |
| A file a member attached is not in the message | Contact Form 7 deletes uploaded files once the email is sent | The file arrives with the email. The app shows its name |