Give visitors a way to reach you without exposing your email

Route messages, notify your team, and protect the public form

Each message remains a FilaForms submission in your application's database. That record is the intake source, not merely the trigger for an email. A teammate can inspect it when a reply needs context, and your application can attach it to a customer, conversation, or lead record later.

Give one person or queue ownership of incoming messages. A general mailbox can work for a small team. A support queue may need subject-based routing. A sales queue may need a lead record before the first response. Keep the submission identifier on every derived record so the original message stays traceable.

Email notification should alert the team without becoming the only copy of a contact message. The listener below reads this template's email, subject, and message codes. It sends those values to the configured contact recipient, then leaves the submission available in FilaForms.

Set mail.contact_recipient to the inbox that owns contact messages. The fallback uses the configured sender address, which keeps the listener runnable before you add a separate recipient setting. Save the listener as app/Listeners/EmailContactFormSubmission.php. Laravel 12 discovers listeners in that directory automatically.

<?php

declare(strict_types=1);

namespace App\Listeners;

use FilaForms\Core\Events\FormSubmitted;
use Illuminate\Mail\Message;
use Illuminate\Support\Facades\Mail;

final class EmailContactFormSubmission
{
    public function handle(FormSubmitted $event): void
    {
        $data = $event->submission->data;

        $email = $data['email'] ?? null;
        $subject = $data['subject'] ?? null;
        $message = $data['message'] ?? null;

        Mail::raw(
            implode(PHP_EOL, [
                "Form ID: {$event->form->getKey()}",
                "Submission ID: {$event->submission->getKey()}",
                "From: {$email}",
                "Subject: {$subject}",
                '',
                (string) $message,
            ]),
            function (Message $mail) use ($email, $subject): void {
                $mail->to(config('mail.contact_recipient', config('mail.from.address')))
                    ->subject((string) $subject);

                if (is_string($email) && $email !== '') {
                    $mail->replyTo($email);
                }
            },
        );
    }
}

Replace the recipient with the inbox or routing process your team already uses. Keep the reply-to value when email is present. It lets a teammate answer the visitor directly from the notification instead of copying an address into a new message.

Public contact forms attract automated submissions. FilaForms ships a honeypot check for public forms. This template has no CAPTCHA integration, so a contact form under heavy bot traffic still needs a CAPTCHA or rate limiting added in the application. Measure unwanted submissions before adding friction for real visitors.

Use a sales-qualified variant when a sales representative must call or assess a lead before replying. Make phone required when a call is part of the expected next step. Keep that question optional for general support or partnership messages, because a forced phone number can discourage people who only need an email reply.

For a personal-site version, drop company when it does not affect the response. An independent consultant may only need a name, email, subject, and message. Removing company reduces the work for visitors and keeps the review queue focused on the message itself.

The field table below provides the initial structure. Change labels and routing to match the people who answer submissions. Review the FilaForms features for Laravel and Filament if your contact flow needs conditional questions, multi-step collection, or additional notification handling.