Automated Quote Intake & Sales Routing
A website quote request is not merely captured by a form. The system validates the submission, evaluates business and geographic routing rules, assigns the opportunity to the appropriate salesperson, and generates the necessary notification.
EasyForms
PHP
Webhooks
Brevo
Business Rules
What had to be decided
- What is the customer requesting?
- Is delivery involved?
- What state and county apply?
- Which territory owns the opportunity?
- Which salesperson should receive it?
- Is a fallback rule required?
The Business Problem
Website quote requests had to reach the correct salesperson. The right destination could depend on multiple factors, including product responsibility, geographic territory, and the nature of the request.
Without a consistent routing layer, every request depended on someone manually reviewing it and deciding where it belonged. That created unnecessary handling and made the result dependent on whether the current rules were remembered and applied correctly.
Operational Friction
- Quote submissions needed to be reviewed quickly.
- Routing consistency had to follow the company’s operational rules.
- Sales responsibility had to match the right territory and product context.
- Manual review created delay and inconsistency.
Before / After
Before
After
How the System Works
Capture
Customer submits a quote request through the WordPress and EasyForms interface.
Validate
The webhook checks and normalizes the information needed for routing.
Evaluate
Business rules determine which routing logic applies to the submission.
Geographic Lookup
Where relevant, state and county information is evaluated against territory and fallback rules.
Assign
The request is assigned to the responsible salesperson or the appropriate fallback route.
Notify
The system sends the necessary notification through Brevo so the correct person receives the opportunity.
Business Rules Are the Application
The difficult part was not merely receiving a webhook. The real work was encoding the company’s actual business knowledge into a system that could consistently apply it.
Rules in practice
- Salesperson responsibilities
- Territory ownership
- County assignments
- Statewide fallback behavior
- Product and request distinctions
- Delivery and pickup conditions
Why the structure mattered
Routing configuration was separated from the main webhook logic so the system remained easier to maintain. That meant territory or responsibility changes could be handled through configuration instead of requiring the central intake process to be rebuilt for each update.
Evidence / Screenshots
The customer-facing quote request that begins the workflow.
Business and territory rules maintained separately from the main webhook processing.
Validation of salesperson and territory assignment behavior.
Example of the resulting routed notification with sensitive information removed.
Technology
EasyForms
PHP
Webhooks
Brevo
County / FIPS reference data
Configuration-driven business rules
Production implementation: Big Drainage (November 2026)
The live Big Drainage workflow was implemented as a dedicated WordPress form plugin paired with a county-territory management plugin. It handles Half Tank, Full Tank and Flatcar inquiries rather than attempting to route every product category through one rule set.
Routing safeguards
- County-based territory assignment for Oklahoma and Texas.
- Explicit manual-review fallback for missing or unmapped locations.
- Salesperson notifications for confirmed routes and review notifications for exceptions.
- Duplicate-send protection and staging-mode email suppression.
Validation
Staging scenarios exercised known counties, missing county information, unmapped territories and routing outcomes. Production checks confirmed thank-you handling, manual-review behavior and successful routing to the responsible salesperson.
Additional state-level routing rules were tested separately; coverage is not described as universal.
Status: production routing is active for the scoped Big Drainage workflow; remaining legacy form replacements and customer-facing refinements are ongoing.
Result
The workflow turns a website submission into a routed business event. Instead of relying on someone to inspect every request and decide where it belongs, the system applies the company’s routing rules consistently.
Changes in territory responsibility can be maintained through configuration rather than requiring the intake process to be rebuilt from scratch every time business rules change.
What This Project Demonstrates
This project demonstrates the kind of automation I build most often: connecting an existing business system to a small layer of custom software that understands the company’s actual operating rules.
- Existing software did not need to be replaced.
- The automation was built around the existing process.
- Business knowledge was converted into repeatable rules.
- The resulting system performs work rather than simply storing information.
Have a process that still depends on someone reading, deciding, and forwarding?
I build small systems that turn those decisions into reliable workflows.