Route sales enquiries to the right rep with budget and timeline upfront

Route sales enquiries into an accountable follow-up process

The field table below groups contact information with the details that shape a sales conversation. That order lets a prospect identify their organisation before they explain the request. It also gives a representative a compact briefing before they open a message or schedule a call.

Assign a clear owner to each new submission. A smaller team may send all enquiries to one sales inbox. A larger team may route by account segment, territory, or product line. The template does not decide that policy. Your Laravel application should make the assignment where it already understands users, accounts, and permissions.

Keep the first follow-up tied to the submitted context. A representative can acknowledge the stated timeline, ask about an unclear budget, and address the company by name. That is more useful than a generic confirmation. It also gives the sales team a consistent source record when several people discuss the same enquiry.

The settings block controls the form behaviour in your panel. Change it there when your sales process changes, instead of maintaining a hand-written Filament schema. This keeps the form visible to the people who own lead collection and prevents configuration from drifting away from the working sales process.

Adapt the template for a fixed-scope package

For an agency selling one fixed-scope package, drop budget and team_size. Add a preferred_start_date field instead. A fixed offer already defines the commercial range, so a start date gives the team a more useful signal about delivery planning.

Keep the company and email details in that variant. They still give the agency a contact point and a way to match a request to an existing client. Ask only for details that change the next action. A fixed-scope package does not need a budget question when the price is already clear.

You can use the same approach for other focused offerings. If a consultant only accepts work in one region, add a location only when it changes availability. If a service requires a decision-maker, add a role question only when it changes who receives the follow-up. Each extra question needs an owner who will use the answer.

Route submissions inside Laravel

FilaForms emits FormSubmitted after a prospect submits this template. A Laravel listener can read email, company, and budget from the submission data. The example writes the submission context to the application log, which gives you a runnable starting point for a notification or review workflow.

Save the listener as app/Listeners/LogSalesContact.php. Laravel 12 discovers listeners in that directory automatically.

<?php

namespace App\Listeners;

use FilaForms\Core\Events\FormSubmitted;
use Illuminate\Support\Facades\Log;

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

        $email = $data['email'] ?? null;
        $company = $data['company'] ?? null;
        $budget = $data['budget'] ?? null;

        Log::info('Sales contact received', [
            'form_id' => $event->form->getKey(),
            'submission_id' => $event->submission->getKey(),
            'email' => $email,
            'company' => $company,
            'budget' => $budget,
        ]);
    }
}

Replace the log call with the action your application needs. You might notify the representative who owns the account, create an internal lead record, or place the enquiry into a review queue. Keep the original submission as the source record. Derived records should retain its identifier so a teammate can inspect the complete response later.

This template captures budget and timeline as text. It does not score or qualify the lead, so routing beyond a notification email remains your responsibility. Add lead scoring only after you define the signals, outcomes, and review process that make a score useful for your team.

Know when this template is the wrong tool

Choose this template when developers already operate the sales application and want enquiries close to the account data that informs follow-up. Review the FilaForms features for Laravel and Filament when your workflow needs conditional questions, multi-step forms, notifications, or submission analytics.