What this module does
Upendo Contact Form gives website visitors a safe way to send a question, quote request, or contact request. Staff configure the form, choose the fields, set the email destination, and decide whether to use reCAPTCHA.
When a visitor submits the form, the request is sent to the configured recipient email and captured in the site's form submission records. Staff can use the email notification and the Forms management area to follow up.
Who can use it
- Visitors: Can complete and submit the public form. They do not need a website account unless the page itself requires sign-in.
- General content editors: Can manage the module only when website gives them Edit permission on the module.
- Site administrators and portal administrators: Usually have permission to configure the form, but the exact result depends on website module permissions.
- Superusers: Can configure the form and portal-wide reCAPTCHA settings and can recover settings when needed.
The form's settings page requires website Edit permission. A user who can edit page content but does not have module Edit permission may not see the Contact Form settings.
Required setup before publishing
The form stays hidden from visitors until both of these email settings are valid:
- Recipient email: The address that receives contact requests.
- From email: The sender address used by the site's mail system.
If either address is missing or invalid, the module shows a configuration message to an editor instead of showing the public form. Visitors do not see a usable form until the settings are fixed.
The form can include:
- First name and last name
- Company
- Industry
- Role in company
- Product or system of interest
- Company size
- Phone
- Email
- Request
Company, industry, role, product interest, and company size can be shown or hidden. Each shown field can be made required where supported. Name, email, and request are commonly required, but the settings can change those rules.
The Name required rule needs at least a first name. Confirm the displayed labels and required rules together so visitors are not asked for information the team does not need.
Email delivery and saved records
The module sends an email using the configured recipient, sender, and subject. It also saves the submission with the submitted fields and request details. Do not treat the email inbox as the only record.
Because submissions can contain personal information, give Forms management access only to staff who need it. Use approved retention and privacy rules for the site.
reCAPTCHA
The module supports the Google reCAPTCHA v2 checkbox. An administrator enters the site key and secret, then enables the checkbox. The secret is stored as a protected portal setting. The site key and secret are shared by all Upendo Contact Form instances on the same portal.
The checkbox can use the Light or Dark theme and Normal or Compact size. If reCAPTCHA is enabled without a valid site key or secret, submissions may fail. Test the form after changing either key.
Appearance and wording
Staff can change:
- Heading lead and emphasis text
- Field labels
- Submit button text
- Input accent color
- Submit button color
- Submit button hover color
Colors must be safe hex values such as #333333 or #ff4057. Use short, clear labels. Do not put private instructions or secrets in visible text.
The form checks required fields, email format, allowed request origin, reCAPTCHA when enabled, and a hidden anti-spam field. It also limits repeated requests from the same portal, module, and IP address. A visitor who sends too many requests must wait and try again later.
These protections can reject a request before an email is sent. This is expected behavior when a request looks unsafe or exceeds the limit.
What visitors experience
Visitors see the configured heading and only the fields that staff enabled. Required fields show a clear validation message. After a successful submission, the form confirms that the request was sent and clears the form. If the request is rejected, the visitor sees a message asking them to correct the form or try again later.
Safe operating checklist
- Verify recipient and sender email addresses.
- Use a sender address allowed by the site's mail provider.
- Test every required field after changing the settings.
- Test the form with reCAPTCHA enabled if the site uses it.
- Confirm that the email arrives and that the submission appears in Forms management.
- Limit access to saved submissions because they may contain personal data.
- Never place the reCAPTCHA secret in page text, source control, or an email.