Two different emails
A form usually sends two things, and they have different jobs.
The internal notification tells your team something came in. Its job is to get the right person to act, so put the useful details in the subject line — form name, and where sensible who submitted it — so it is triageable without opening it.
The acknowledgement goes to the person who filled in the form. Its job is to confirm the message arrived and set an expectation. "Thanks, we have your enquiry and will reply within two working days" prevents most duplicate submissions and chaser emails.
Sending to the right place
Send internal notifications to a shared address rather than an individual. People change roles and take leave; an enquiries address does not.
Where different submissions need different teams, route on a field in the form — an enquiry-type dropdown — rather than having one person forward everything by hand.
Deliverability
Notification email is ordinary email and lands in spam like any other. Two things help:
- Send from your own domain, properly configured, rather than from the visitor's address. Sending as the submitter is a classic cause of messages being rejected outright.
- Put the submitter's address in reply-to, so hitting reply just works.
Beyond email
Where a form feeds a process rather than an inbox, the platform can post submissions onward to another system — a chat channel, a CRM, a ticketing tool. That is a configuration job rather than an editorial one, but it is worth knowing it exists before building a manual re-typing habit.
Check it still works
Notifications fail quietly. An address changes, someone leaves, a filter gets added. Submit a test through the live form every so often and confirm it arrives where it should.