Lead Forms

One clean intake path, ready for Knox's pipeline.

This keeps lead capture honest. Knox has one canonical inquiry form today, and it stays intentionally lightweight while still collecting the context needed for the pipeline, proposal path, and one-event control center.

Back to dashboard

Active forms

Intake fields

Conditional rules

Supported tracks

Live intake form

Keep this surface simple and truthful. Knox has one canonical inquiry endpoint today.

Knox Inquiry Form

knox-inquiry

active

The single canonical intake path for all Knox leads. Lightweight, intentional, and feeds the pipeline immediately.

Submission path

POST /api/inquiries

Website, Facebook, Perspective

Tracks

WeddingCorporate

What this form should do

Capture the minimum context Knox needs without turning lead intake into a long questionnaire.

Preserve one shared intake path for both wedding and corporate, while keeping the commercial track separate behind the scenes.

Feed the pipeline and one-event workspace immediately so the team can move from inquiry to quick call without re-entering context.

Field groups

Grouped the way an operator expects to scan them, not the way a generic form builder would.

Contact

4 fields

Lead Name

Required

lead_name

Partner Name

Optional

partner_name

Required

Phone

Required

phone

Routing

2 fields

Source

Required

source

Event Type

Required

event_type

Event

3 fields

Venue

Optional

venue

Event Date

Optional

event_date

Notes

Optional

notes

Knox rules

The form stays simple, but it still enforces the rules Knox asked us not to lose.

Partner name for weddings

Partner name field is surfaced when event_type is wedding. For corporate, it stays hidden.

Wedding baseline pricing

Wedding inquiries default to $6,500 baseline (cocktail + reception). Ceremony is a modular add-on.