Form submissions
What happens when the visitor clicks Send.
A submitted contact form creates a Contact message record in your workspace. Depending on whether the Tickets module is enabled, it may also become a ticket.
The flow
When the visitor clicks Send:
- The fields are validated (required ones present, email looks like an email, message under 5000 chars).
- If you've configured a consent line and the checkbox isn't ticked, the submission is rejected with a friendly error.
- A
ContactMessagerow is created with the visitor's name, email, phone, subject, body, IP, and user-agent. - If the Tickets module is enabled, we also create a
Ticketwithsource: 'web_form', find-or-create aRequestermatching the email, and link the two. The agent sees the new ticket in their queue immediately. - The visitor sees the configured after-submit action — a thanks page or a redirect.
Where to see submissions
- As contact messages —
nura24.com/staff/messageslists all contact submissions across workspaces (super-admin view). Workspace-level views are coming. - As tickets —
<tenant>.nura24.com/admin/tickets, filtered tosource: web_form.
If Tickets is disabled, only the contact-message record exists. You can read it from the admin area but there's no agent-side queue for it.
Spam protection
Two layers:
- Hidden honeypot field — a
<input name="website">rendered withdisplay: none. Bots fill it; humans don't. A non-empty value rejects the submission. - Rate limiting — by default no per-IP cap, but the standard Laravel rate limiter applies to the route at a sensible global level.
We don't use reCAPTCHA. The honeypot catches the vast majority of automated submissions; the few that get through are easier to deal with than the friction reCAPTCHA adds to real visitors.
What gets emailed
By default, nothing. Submissions land in the inbox / message list and you check them when you check your inbox. If you want email notifications, configure your <tenant>.nura24.com/admin notification settings (currently planned, not shipped).
File attachments
Not supported on the public contact form. If a visitor needs to send files, point them at the customer ticket portal instead — files there are planned, though not yet wired either.