ACS Contact Form

Most contact forms end at “mail sent”. The enquiry then lives in an inbox, next to newsletters and invoices, and the one that mattered gets answered four days late — or not at all.

ACS Contact Form keeps the light, dependency free form of version 1 and adds the part that comes after the send button.

Every message is kept in WordPress

Submissions are stored in your own database and listed in the admin: form name, sender, subject, category, status, when it arrived and how long it has been sitting there. Nothing depends on a mail server that may or may not deliver.

• Status is Untouched, In progress or Done, and starts at Untouched
• Change status and category straight from the list, or open one message for the full detail
• Filter by form, category and status, search the saved text, and export the current view to CSV
• The detail screen shows every field, the attachments, the reply draft and a history of your own notes

Messages sort themselves

Each submission is scored against keyword rules and filed as Estimate, Consultation, Recruiting, Sales or Spam. Anything that matches nothing becomes Consultation, so nothing disappears.

• The rules are plain keyword lists you can edit — the defaults are written for Japanese enquiries
• Subject, body and the sender’s mail domain are all considered
• On a tie, the category that does not suppress the notification wins, so an ambiguous message is never quietly filed away
• Spam signals: the honeypot field, a body full of links, and text with no Japanese in it at all

Sales and spam do not send you a notification mail by default. They still appear in the list, so you can look when you feel like it instead of every time a cold pitch arrives. Which categories notify you is a setting.

A reminder when something is left

If a message is still Untouched after three days, a single daily mail lists everything that has been forgotten, with a link to each one. The threshold is a setting, zero switches it off, and messages marked In progress are left alone.

An optional reply draft

If — and only if — you have connected an AI provider to WordPress itself under Settings > Connectors, the detail screen gains a Write a draft reply button. The draft appears in an editable box; you read it, fix it, and send it from your own mail client. The plugin asks the WordPress core AI Client for the text; it holds no API key of its own and never contacts a provider directly. With nothing connected, the button is not shown. See External services below.

Still the same form

The form builder, the shortcode, the block, the design settings and the auto-reply from version 1 all work exactly as before. Updating from 1.1.2 keeps every form and every setting.

• Drag-free ordering of standard fields, custom fields and the attachment field
• Text, textarea, select, radio and checkbox custom fields
• Colours, radii and required badges per form
• Ajax submission with no jQuery
• Honeypot spam trap, no third-party captcha, no external request

External services

This plugin does not connect to any external service, and it stores no API key.

One optional feature, the AI reply draft, is built on the AI Client that ships with WordPress 7.0. The plugin hands the prompt to wp_ai_client_prompt() and reads the answer back. Which provider that reaches, which model it uses and where the credentials live are decided by WordPress itself, on Settings > Connectors. If no provider is connected there, the draft button is not shown and nothing is ever sent.

When you press “Write a draft reply” (or, if you switch that option on, when a submission arrives), the text handed to the AI Client contains: the subject and the field values of that one submission, the sender’s name, your site name, the name you set as the person replying, and the tone you selected. Nothing else is included, and nothing is sent for messages you do not act on.

Please read the terms of whichever provider you connect to WordPress before switching the feature on, and tell your visitors in your own privacy policy if you enable it.

Privacy

The plugin stores what a visitor typed into your form, plus the page the form was submitted from and, unless you switch that off, the sender’s IP address. Attachments are stored as files inside your uploads directory.

This data stays on your own server. It is registered with the WordPress personal data tools, so an export request includes the stored submissions of that email address and an erasure request deletes them together with their attachments. Individual messages can also be deleted from the list at any time.