24.1 Autoresponder Overview

AIUNIFY Funnels includes a Landing Page Autoresponder that can send an email after a qualifying Main Page form submission.

The Settings interface states:

All the form in main pages when submit will send a email...

and displays the warning:

Make sure there is an email field in the form!

24.2 Autoresponder Fields

The confirmed Autoresponder controls are:

Message title	The email subject used by the autoresponder.
Sender name	The sender name used when the autoresponder message is sent.
Sender email	The sender email address used when the autoresponder message is sent.
Message text	The HTML message body sent to the qualifying submitted email address.

24.3 Leave the Autoresponder Completely Empty When Not Using It

The Settings update checks whether any Autoresponder values have been entered.

If all Autoresponder values are empty, the Autoresponder-specific required-field rules are not applied.

If you begin configuring the Autoresponder, complete the full set of required fields.

24.4 Validation Requirements

If any Autoresponder field contains a value, AIUNIFY Funnels requires:

Message title	Required, maximum 255 characters.
Sender name	Required, maximum 50 characters.
Sender email	Required, must be a valid email address, maximum 50 characters.
Message text	Required.

24.5 The Form Must Contain an Email Field

The Autoresponder does not simply send to whichever form field looks like an email address visually.

The confirmed submission logic looks for a captured field identified as:

email

and verifies that its submitted value is a valid email address before the Autoresponder is considered eligible to run.

Important: When using the Autoresponder, make sure the Landing Page form includes a properly named email field and test it with a valid email address.

24.6 Recipient Address

For a qualifying submission, the Autoresponder uses the captured value from:

field_values['email']

as the recipient address.

This is why the email field is required for the feature to operate as intended.

24.7 Dynamic Form-Field Placeholders

The Autoresponder supports dynamic placeholders based on captured form field names.

The interface explains that you can use:

%field_name_attribute%

so that content entered by the Lead into the corresponding form field can be inserted automatically into the message.

24.8 Example Placeholder

If the form contains a field named:

name

you can use:

%name%

inside Message text.

When the Autoresponder job processes the captured submission, it searches the Message text for placeholders built from the captured field keys and replaces them with the corresponding submitted values when values are present.

24.9 Placeholder Names Must Match Form Field Names

A placeholder is only useful when its name corresponds to a captured form field key.

For example, %first_name% and %name% are not interchangeable unless the Landing Page form actually submits the matching field name.

Review the form's field names before composing a personalized Autoresponder.

24.10 Message Delivery Structure

When the Autoresponder job sends the message, it uses:

From address	The configured Sender email.
From name	The configured Sender name.
To address	The valid email captured from the submitted form.
Subject	The configured Message title.
Body	The configured Message text after supported placeholder substitution.

24.11 HTML Message Body

The confirmed Autoresponder send operation sets the configured Message text as an HTML email body.

Keep the content clear and verify its rendered appearance with a test submission before using the Landing Page for live traffic.

24.12 The Autoresponder Runs as a Queued Job

The Autoresponder implementation is designed as a queued job.

This separates the email-sending work from the immediate browser form-submission response.

If a form submission is captured but the expected Autoresponder email does not arrive, troubleshooting should therefore include both the Landing Page configuration and the application's email/queue operating environment.

24.13 Autoresponder and Next Action Are Separate

The Autoresponder does not determine where the visitor's browser goes after submission.

The visitor next action is controlled separately by Action after form submission.

You can therefore configure a workflow where the visitor is sent to the Thank You Page or another URL while the qualifying email submission is also processed by the Autoresponder.

24.14 Autoresponder and Mailing Integration Are Separate

The Autoresponder sends a configured message directly to the captured email address.

A mailing integration such as Mailchimp, Acellemail, or Mailwizz is a separate function that can add the captured contact to the selected external mailing system.

A Landing Page can use these functions as separate parts of the same conversion workflow when properly configured.

24.15 Recommended Autoresponder Test

1. Confirm the Main Page form contains an email field.
2. Enter Message title.
3. Enter Sender name.
4. Enter a valid Sender email.
5. Create the Message text.
6. Add only placeholders that correspond to actual form field names.
7. Save Landing Page Settings.
8. Submit the public form using an email address you can check.
9. Verify placeholder substitution, sender identity, subject, and message body.
10. Verify the visitor's separate post-submission next action.

Operating principle: Configure all Autoresponder fields together, use a valid email form field, match placeholders to real submitted field names, and validate delivery with a complete test submission.