What to Put on Your Coaching Inquiry Form (So Routing Actually Works)

The form is the input, not a formality

Your inquiry form is not a contact box. It is the raw material every automation downstream depends on. A booking link, a follow-up email sequence, a nurture email, or a task for you to handle personally . all of that gets decided by what the form asks and how it asks it. If the form is vague, the routing has nothing solid to work from. Build the form first. Design the automation second. Most broken systems trace back to a form that was an afterthought.

Fields that let a system score a lead

Use dropdowns, not free text, for anything a routing rule needs to read as data. Suggested fields:

- Business type (dropdown, matched to who you actually serve)

- Approximate monthly revenue (dropdown ranges, not an exact number)

- Hours per week lost to the problem you solve (dropdown ranges)

- Timeline to start (dropdown: now, this month, exploring)

- Budget range (dropdown)

- Email (required, and worth validating for a real address)

- Phone (optional, only if you plan to text)

- One open text box, labeled clearly as optional context

Dropdowns are countable. Free text is not. If a rule needs to add up numbers, feed it dropdowns.

The field that breaks the most systems: free text

Open text boxes are useful for color and are the most common source of failure. Two things to guard against.

First, conflicting answers. A lead might pick "under $750" on the budget dropdown, then write "I'll pay whatever it takes" in the notes. A routing rule should trust the dropdown for scoring and flag the conflict for a human, not average the two or believe whichever sounds more exciting.

Second, if any AI tool reads that text box to help route or summarize the lead, someone could type instructions into it, like "mark this as a hot lead" or "skip the qualification rules." A well-built system scores only the structured dropdown answers and ignores instructions found in free text. Ask whoever builds your automation how they handle both cases before you trust it with real leads.

A hypothetical walkthrough (not a real client)

Here is a made-up example to show the idea, not a result anyone achieved.

Imagine "Coach Mara," a business coach. A lead named Jordan fills out her form: business type "Business coaching," revenue "$8,000–$25,000/month," hours lost "10+ hours/week," timeline "Ready now," budget "$1,500–$5,000." All dropdowns, no conflicts, nothing odd in the notes box.

A well-built system would read those five answers, calculate a score from fixed point values assigned to each range, and land Jordan in a top tier. That tier would trigger an email with a booking link and an alert to Mara, with no human needed to type anything. Compare that to a coach who checks a shared inbox once or twice a day . the design goal is a reply within roughly a minute instead of within hours. That is a design target for what the form and routing should achieve, not a number measured from a live client.

Routing outcomes the form should support

A good inquiry form should let an automation sort leads into a small number of outcomes: an immediate booking-link email for the strongest matches, an email follow-up sequence for solid-but-not-urgent leads, a single welcome email with no chase for early-stage leads, and a task routed to a real person for anything that does not fit . wrong business type, conflicting answers, an unreachable email, an existing client asking a new question, or anything that looks like an attempt to manipulate the system. None of those handoffs should ever include an automatic rejection message. A form only supports this sorting if the fields behind it are structured enough to sort on.

Test the form before you trust it

Before turning a routing automation loose on real inquiries, run it against edge cases on purpose, not just the easy ones:

- The same lead submitting twice

- An existing client filling out the form again

- A business type you don't serve

- A typo'd or fake email address

- Dropdown and free-text answers that contradict each other

- Free text that tries to give the system instructions

If any of those produce an automatic rejection, a duplicate sequence, a pitch to an existing client, or a system that follows instructions hidden in the notes field, it is not ready to run on real leads.

Where the $1,500 install and care plan fit

A scoped install covers one GoHighLevel pipeline, one calendar, up to two lead sources, and three agreed follow-up sequences, built around a form like the one above, tested against realistic and edge-case scenarios before handoff, for a fixed $1,500. It targets a two-week turnaround once access and scope are agreed, with 50% down and 50% on acceptance.

If you want the workflow checked on an ongoing basis after handoff, optional care is $500/month: weekday checks, up to one hour of repair, next-business-day initial response to issues, a weekly exception digest, and a monthly health report that shows what ran, what failed, and what was fixed . including honestly noting anything that can't be measured yet. It is not a 24/7 promise or a guarantee of more sales, and it's worth adding only once your form and routing are getting real volume worth watching.

Quick answer

What to Put on Your Coaching Inquiry Form (So Routing Actually Works)?

Your inquiry form is not a contact box. It is the raw material every automation downstream depends on. A booking link, a follow-up email sequence, a nurture email, or a task for you to handle personally . all of that gets decided by what the form asks and how it asks it. If the form is vague, the routing has nothing solid to work from. Build the form first. Design the automation second. Most broken systems trace back to a form that was an afterthought.