Add A Contact Form And Read Messages
Goal: Let visitors write to you, and know where their messages land.
Time: 4 minutes
You need: A page, and someone who should receive the mail
Steps
- In the Main slot, select Add Block, then choose Contact Form.
- Fill in the copy: Heading, Intro Text, Submit Label, and the Success Message shown after sending.
- Under Delivery Settings, leave Send email notification on. Use Recipient Email Override only when this one form should go somewhere other than the site's usual address.
- Under Consent, turn on Require a consent checkbox if you need one, and write the Consent notice next to it.
- Select Save New Block. Messages arrive in Contact Messages.
- Open one to read it in full, mark it read, replied, spam, or archived, and see whether the email notification actually went out. Mark real campaigns spam so later copies are recognized; restore a false positive to a normal status.
Where The Mail Goes
The recipient is resolved in order: the block's Recipient Email Override, then the site's contact recipient, then the installation's configured fallback.
Set it on the site, not on every block. Overrides are for the one form that genuinely belongs to someone else — a jobs page going to a different inbox.
Notes
- The message is stored whether or not the email arrives. The detail screen separates the two, so a delivery problem never means lost enquiries.
- Forms carry signed timing and honeypot checks. A submission made faster than the hard minimum is silently discarded.
- Valid submissions are also scored locally. Suspicious messages are retained as Quarantined or Spam, but their email notification is suppressed. The filter shares repetition, sender, exact-IP, network-prefix, and learned reputation signals with Comments and compatible plugin forms on the same site.
- Archive does not train protection. Use Spam for actual abuse and restore false positives to New, Read, or Replied.
- Write the Success Message as a promise you keep.
- The consent notice is your text, not boilerplate the CMS writes for you.
Choose Notification Privacy And Frequency
On CMS 1.95.0 or newer, open Sites → Edit → Contact and choose Alert only to keep visitor details inside the authenticated CMS inbox. This policy also applies to supported plugins such as Live Chat 0.7.0. Recipient routing remains separate.
Choose First alert immediately, then batches for a first alert followed by ten-minute batches, or Daily for one count-only daily notification. The optional daily pending-message summary distinguishes unread work from work awaiting a reply. Its hour follows the site timezone. Laravel’s scheduler must run every minute for batches and summaries.
New sites use alert-only notifications by default. Existing sites retain their previous full/immediate behavior during upgrade, so change their policy explicitly if needed. Reading a message does not resolve it: mark it replied or archive it when the work is complete.
On CMS 1.95.1, check the scheduler status on the Dashboard or the site’s Contact settings after choosing batched/daily delivery. Not yet verified or Delayed requires your server administrator or hosting provider to check the background scheduler. The screen shows the last scheduled signal and completed notification run. See scheduler setup for the setup owner and verification steps.