Contact Form 7

Contact Form 7 has no built-in AI features -- form validation, spam filtering (via Akismet or reCAPTCHA), and mail routing are all rule-based configuration, not machine learning, and that's unlikely to change given the plugin's minimalist, extension-based philosophy.

Practical Details

Any AI capability (smart spam scoring beyond Akismet/reCAPTCHA, AI-assisted field suggestions, sentiment analysis on message content) has to come from a separate service you wire in yourself, typically through the wpcf7_before_send_mail hook calling an external API, since core CF7 won't do this natively.

Actionable Considerations

1. Don't expect native AI spam scoring beyond what Akismet and reCAPTCHA already provide -- that's the practical ceiling in core CF7.
2. Use the wpcf7_before_send_mail hook if you want to route submission content to an external AI service for analysis.
3. Weigh whether a form plugin with more built-in intelligence is a better fit before building custom AI integration on top of CF7's minimalist core.

After installing the plugin, you build a form using form tags in the Form tab (or the tag-generator UI above it), then configure the Mail tab so submissions actually get emailed somewhere, and finally paste the generated shortcode (e.g. [contact-form-7 id="123"]) into a page or widget.

Practical Details

The Mail tab is the part most new users get wrong -- if a mail-tag in the Subject or From field doesn't match an actual form field name exactly, the placeholder just gets sent as literal text instead of the submitted value, and there's no error thrown to warn you. Testing an actual submission end-to-end (not just previewing the form) is the only reliable way to catch this before it reaches real users.

Actionable Considerations

1. Match mail-tag placeholders in the Mail tab exactly to your form field names, since a mismatch fails silently rather than throwing an error.
2. Submit a real test entry after setup, not just a visual form preview, to confirm mail actually arrives.
3. Install Flamingo before launch if you'll need a record of submissions beyond what lands in an inbox.

By default, Contact Form 7 doesn't create a database record of submissions at all -- data is captured, emailed per the Mail tab configuration, and then discarded from CF7's own memory, which is a meaningfully different model than form plugins that store every submission automatically.

Practical Details

If you need submissions retained and searchable inside WordPress, Flamingo (the free companion plugin) stores them as a custom post type, at which point standard WordPress role capabilities govern who can view or delete that data. Without Flamingo, data retention for CF7 really means whatever your email provider retains -- worth being explicit about for any GDPR-style data request.

Actionable Considerations

1. Decide explicitly whether you need Flamingo for submission storage, since CF7's default behavior is to not retain data at all.
2. Document where submitted data actually ends up (which inbox, and Flamingo if installed) so you can answer a data-access or deletion request accurately.
3. Apply WordPress role-based access control to Flamingo's stored messages the same way you would any other sensitive content type.

Contact Form 7 itself is lightweight and handles typical WordPress traffic fine, but because it doesn't store submissions by default, scale for CF7 really means the reliability of your mail delivery pipeline under submission volume, not database load -- a high-traffic form with unreliable mail sending will silently lose submissions long before CF7 itself becomes a bottleneck.

Practical Details

If you add Flamingo for storage, that data lives as a custom post type in wp_posts, and a very high submission volume over time can meaningfully grow that table -- worth monitoring on shared hosting. For complex, multi-step, or high-volume forms, some teams eventually outgrow CF7's shortcode-based, non-conditional-logic core and move to a more full-featured form plugin.

Actionable Considerations

1. Prioritize a reliable SMTP-based mail pipeline over server default mail() as submission volume grows, since that's CF7's real scaling bottleneck.
2. Monitor Flamingo's stored message table size on shared hosting if you're retaining a high volume of submissions long-term.
3. Reassess whether CF7's core feature set (no conditional logic, no native multi-step forms) still fits once form complexity grows significantly.

The most common real-world issue is mail simply not arriving -- often not a CF7 bug at all, but the hosting server's mail sending being unreliable or flagged as spam, which is why many CF7 sites end up needing an SMTP plugin (like WP Mail SMTP) to route mail through a real mail provider instead of the server's default mail() function.

Practical Details

The second most common issue is a mail-tag mismatch (a placeholder in the Mail tab that doesn't match an actual form field name), which fails silently -- the form submits successfully, but the resulting email has literal placeholder text instead of the customer's actual input. Plugin or theme JavaScript conflicts can also break the AJAX submission, usually visible as a form that never confirms success despite the page not reloading.

Actionable Considerations

1. Install an SMTP plugin (like WP Mail SMTP) if mail delivery is unreliable, since server default mail() is a common silent failure point.
2. Double-check every mail-tag placeholder in the Mail tab matches an actual form field name exactly.
3. Check the browser console for JavaScript errors if the form doesn't show a success/error message after submission, since that usually points to a plugin or theme conflict.

Contact Form 7 is a free WordPress plugin (by developer Takayuki Miyoshi) with millions of active installs, built around form tags -- shortcode-style placeholders like [text* your-name] and [email* your-email] typed directly into a form editor, rather than a drag-and-drop builder like newer competitors offer.

Practical Details

The plugin's defining limitation is that it doesn't store submissions anywhere by default -- it only emails them, using the Mail tab's To/Subject/Body fields with mail-tag placeholders like [your-name]. If you need a searchable submission history inside WordPress, that requires Flamingo, a free companion plugin from the same developer, since core Contact Form 7 has no database storage.

Actionable Considerations

• Install Flamingo alongside Contact Form 7 from the start if you'll need to review past submissions, since core CF7 doesn't store them.
• Get comfortable with the shortcode-based form-tag syntax, since there's no drag-and-drop builder in core CF7.
• Confirm your hosting's outbound mail delivery works before launch, since a broken mail configuration means silently lost submissions with no stored backup.

Because Contact Form 7 only emails submissions by default (no dashboard, no submission count, no built-in analytics), the practical way to know if a form is actually working is to monitor whether expected mail volume matches actual usage -- a form that looks fine but has broken mail delivery produces zero visible symptoms in WordPress itself.

Practical Details

Installing Flamingo gives you at least a basic submission log inside wp-admin, which is the closest thing to native engagement visibility CF7 offers -- without it, you're relying entirely on inbox activity to gauge whether the form is being used and successfully delivering.

Actionable Considerations

1. Install Flamingo if you want any visibility into submission volume from within WordPress itself, since core CF7 provides none.
2. Periodically send a real test submission to confirm mail delivery is still working, since a silent failure produces no visible error in WordPress.
3. Pair CF7 with server-side or email-provider logging if submission volume needs to be tracked reliably over time.

Core Contact Form 7 has no native webhook or third-party API connector -- getting submissions into a CRM, email marketing platform, or Slack requires either a dedicated add-on (several exist for specific services) or custom code, since this isn't built into core.

Practical Details

For developers, CF7 exposes action hooks like wpcf7_before_send_mail and wpcf7_mail_sent that let custom code intercept a submission and push it elsewhere programmatically, which is the most flexible integration path if no off-the-shelf add-on covers your target system. This distinction (core has no native automation, but is genuinely extensible via hooks) surprises teams expecting Zapier-style native connectors out of the box.

Actionable Considerations

1. Check for a dedicated CF7 add-on for your specific target system before assuming you need custom code.
2. Use the wpcf7_before_send_mail or wpcf7_mail_sent hooks for custom integrations if no existing add-on fits.
3. Test integration reliability under real submission volume, since a failed API call in custom hook code can silently drop data with no default retry.

Contact Form 7 includes built-in Akismet spam-filtering integration and native Google reCAPTCHA support (configured in its own settings tab), which cover most spam without a third-party plugin, though newer bot-driven spam sometimes still gets through reCAPTCHA v2/v3 depending on your threshold settings.

Practical Details

Because core CF7 doesn't store submissions in WordPress by default, the biggest practical data-handling question is what happens to submitted data in transit and in your email inbox, not in a CF7-managed database -- if you add Flamingo for storage, that data then lives in wp_posts and needs the same access controls (via WordPress roles) as any other content.

Actionable Considerations

1. Enable reCAPTCHA in Contact Form 7's own settings tab as your first line of spam defense before reaching for a third-party plugin.
2. Treat email inboxes receiving form submissions as sensitive data storage, since that's often the only place submission data persists without Flamingo.
3. Limit WordPress editor/admin access to whoever actually needs to modify forms, since form-tag mistakes can silently break mail delivery.