Troubleshoot a contact form that is not delivering
Separate form submission, notification delivery, and support-ticket creation.
Identify which part is failing
A successful form submission, a sent notification, and a created support ticket are separate outcomes. Tell the team whether the visitor sees an error, the submission is stored but no email arrives, or a notification arrives without the expected ticket.
Run one labeled test
- Use a clearly synthetic subject such as “Website form test.”
- Record the page, submission time, and confirmation message.
- Check the intended recipient mailbox and junk folder.
- Check the form's submission record if you are authorized to view it.
- Report the result without repeatedly sending the same test.
Avoid putting real customer details into troubleshooting submissions.
Explain the current integration
Include the form product, configured recipient, and current delivery provider if known. A Brevo notification does not automatically become a support ticket. Connecting a form to a support workflow requires agreed field mapping, requester identity, product routing, and duplicate handling.
Before changing the sender
Ask the team to review the sending mailbox and its authentication requirements. Changing a From address alone does not grant an application permission to send as that mailbox. Microsoft 365 delivery also depends on a configured connector and appropriate permissions. Keep any existing working notification route until the replacement has been verified end to end.
Include this guide and what you tried in your ticket so we can pick up from there.
Contact support