WordPress has forty form plugins, and the endpoint makes most of them unnecessary.

The case for no plugin

A form plugin exists to give an editor a UI for building forms. If the form is fixed, designed, and posts to an endpoint, that UI is a liability: an update surface, a set of scripts on every page, and a database table of submissions that duplicates the record you actually use.

<form action="https://freelyform.com/f/FORM_ID" method="POST">
  <input type="hidden" name="_subject" value="Enquiry — WordPress site">

  <p>
    <label for="wp-email">Email</label><br>
    <input id="wp-email" name="email" type="email" autocomplete="email" required>
  </p>

  <p>
    <label for="wp-message">Message</label><br>
    <textarea id="wp-message" name="message" rows="5" required></textarea>
  </p>

  <p><button type="submit">Send</button></p>
</form>

The three things that go wrong here

• The block is stripped. Some role and configuration combinations remove form elements from post content. If that happens, move the markup into a template part.
• The success page is cached. A page cache that stores the POST response serves a stale thank-you to the next visitor. Exclude the path, or redirect.
• Two forms, two plugins, two inboxes. The common end state of plugin sprawl. One endpoint per form keeps recipients and rate limits legible.

When the plugin stays

Conditional logic, multi-step flows, and a UI an editor genuinely uses are real reasons to keep a plugin. In that case configure it to post to the endpoint and disable its own storage, so the record has one home rather than two that disagree.