GDPR requirements for contact forms – the complete checklist
Consent, storage, deletion and data processing agreements – what the law actually requires, point by point.
Read the guideMost guides stop at “install a plugin”. But the real question is what happens after the customer hits send. Here are all three routes – with honest pros and cons.
The default choice. You install a plugin, build the form in an editor and paste in a shortcode. It works – but be honest about what you get:
wp_mail) often lands in spam – without an SMTP setup the inquiries never arrive at all.For developers: a form in the theme plus a handler that sends the mail or hits an API. Full control, no plugin maintenance – but now you own spam protection, validation, error handling and the GDPR details yourself. Realistically only a good idea if a developer is already on the project.
The third route moves the focus from the form to the flow: the messages land not in an inbox but in a system with categories, ownership and response times. With Telenoa's WordPress plugin it takes no code:
[replied] and [replied_form].Without the plugin, you can paste the widget's script before </body> in the theme. You'll find the code under Sources → Widgets:
1 <?php wp_footer(); ?>2 <script src="https://app.telenoa.com/api/widgets/<widget-id>/embed"></script>3</body>
Create an account, add the form to your website and connect your inbox. Noa handles the rest.