Send a thoughtful confirmation to the person completing your form, using your workspace’s logo, colors and voice.
Availability
Branded autoresponders are included with Developer and Pro. Developer emails retain a small “Powered by FormBastion” footer; Pro can remove it. Paid upgrades are coming soon. Workspaces already on an eligible plan can use the feature. Existing forms have autoresponders turned off.
1. Set your workspace brand
Open Notifications → Email branding. A workspace owner or administrator adds the business name, HTTPS website, accent color, optional logo and footer. Each workspace has its own brand. PNG and JPEG logos can be up to 250 KB and 2,000 pixels wide or high. Logos are public email images; never upload private information. Uploading requires a verified customer account, a verified workspace owner and an active workspace. Up to 100 immutable logo versions are retained per workspace so earlier emails keep their images.
Emails use the shared responsive layout with your identity and a plain-text alternative. The sender is your business name via FormBastion, from [email protected], with no Reply-To. The address does not accept replies. Your own sender domain is not supported.
2. Configure a form
Open the form’s Autoresponder tab. Enable confirmations and choose a required Email field containing the submitter’s address. Optionally choose a Text field for their first name; an unsuitable value falls back to “Hello”.
Write the subject, heading and confirmation message. Add an expected response time or next steps and an optional HTTPS website button. Content is plain text, safely formatted by FormBastion. A receipt reference is included automatically. Submitted messages, URLs, attachments and private inbox links are never inserted into the confirmation.
3. Protect the connection
Active website sources must use Enhanced protection before publishing an enabled autoresponder. Add the CDN script to your website and enable Enhanced protection in the source settings. A browser response without verified Enhanced protection receives no autoresponder. Trusted-server sources continue to require their secret authentication.
Rejected and quarantined submissions do not receive confirmations. Releasing a quarantined response does not trigger an autoresponder. Keep confirmations focused on receipt and next steps; this feature is not for newsletters, promotions or campaigns.
4. Preview, test and publish
Save draft & update preview refreshes the desktop and phone previews with example data. Links are disabled in the browser preview. Send test to my account queues your current entries to your own active, verified customer email address. You cannot enter an arbitrary test recipient. Tests use one email delivery, with limits of three per workspace per hour and six per account per day.
Publish the form from its overview to apply the message and current workspace brand. Saving branding or a draft does not modify the published version. Publish each affected form after changing its brand. Already accepted responses retain the message and branding from their published version.
Usage and delivery outcomes
Team notifications and autoresponders share the workspace’s monthly email allowance. One team notification plus one autoresponder uses two deliveries. Tests also use the allowance. Recipient permission invitations and account/security emails are outside this allowance.
See Notifications → Autoresponder history for tests and live confirmations, or open an individual submission. Accepted means the relay accepted the email, not proof of inbox placement or reading. Confirmed failures retry up to five attempts. Unknown outcomes are held without replay. Plan-limited, capacity-limited and rate-limited confirmations are not sent as a delayed backlog, and cannot be manually replayed.
An active verified workspace owner and an active Developer or Pro plan are required at delivery time. A downgrade to Free stops queued confirmations. A Pro-to-Developer downgrade restores the Powered by FormBastion footer on queued emails. Changing plans does not delete submission data.
Recipient protection and stopping
Across all forms and workspaces, at most one confirmation per hour and three per UTC day is queued to the same email address. These limits reduce repeated unwanted messages; they do not prevent the form response from reaching its inbox. Permanent mailbox rejection also stops future confirmations to that address.
Every confirmation includes a link to stop submitter confirmations across FormBastion. Opening the link does not change preferences; the recipient must confirm the action. This does not stop account-security emails or separately confirmed team notifications. An email already in flight cannot be recalled.
Storage and API
Submission confirmation records follow submission retention and deletion. Test records expire after 30 days. Email copies already delivered are outside FormBastion’s deletion controls. Keyed recipient rate records expire after 90 days of inactivity; suppression hashes remain to honor stopped confirmations.
The authenticated GET /v1/submissions/{id} response includes an autoresponders array with id, status, attempt_count and last_error. Public ingestion receipts do not expose email destinations or delivery records. API draft updates preserve existing autoresponder settings; use the portal to configure branding and preview your message.