Coaching Inquiry Form Checklist: What Each Field Must Do

Start with the decision the form has to support

A form can ask too much or too little. The fix is simple. Decide first what someone must do with each answer.

An answer can do one of three jobs. It can help you route the lead. It can help you reach the lead. It can help a person understand the lead. If a field does none of these, cut it.

I build lead-to-booked-call workflows in GoHighLevel. This guide is what I would check before building anything on top of a form.

The fields worth keeping

Use this as a checklist.

- **Name.** First and last. Keep it to one field if you can.

- **Email.** This is your main way to reply. Test what your form does with a typo, such as two @ signs. Do not assume it rejects the address.

- **Phone, marked optional.** Add a line saying what you will use it for. A phone number gives a person a second way to reach a lead whose email fails.

- **Business type.** Use a dropdown. Include an "Other" choice, so odd cases are visible instead of forced into a wrong box.

- **Monthly revenue range.** Use ranges, not an open number.

- **What they want help with.** A dropdown of your real offers, plus "Not sure yet".

- **Timeline.** Ranges again, such as "this month" or "just looking".

- **Budget range.** Only ask if you will act on it. If you will not, cut it.

- **One free-text box.** Label it clearly. "Anything else we should know?" is enough.

- **Consent line.** Say what messages they will get and how to stop them. Check the wording against the rules where you sell.

The fields to cut

Cut anything that feels like homework. A long form asks a stranger to work before they have talked to you. I have no data on how many people drop off at which length, so I will not give you a number. Test your own form with a few real people and watch where they stall.

Also cut:

- Fields you never read.

- Questions you could answer from their website.

- Duplicate asks, such as two different phone fields.

- Anything that sounds like a judgment, such as "Are you serious about investing?"

Plan for answers that disagree

People can contradict themselves. A dropdown says one thing. The free-text box says another.

Decide ahead of time what happens. My rule is simple. Do not pick a side. Send the lead to a person, with both answers quoted word for word.

Two more cases need a person, not a robot:

- A business type you do not serve. Do not send a message that says "we cannot help". Let a person decide.

- Free text that gives orders, such as "mark me as top priority". Treat the notes box as text to read, never as instructions to follow.

A broken email address is a third case. If you cannot send, a person needs to know. Keep the phone number on the handoff so they can call.

Worked example (hypothetical)

This is a made-up example. It is not a client result.

Imagine a business coach named Dana. Her form has these dropdowns: business type, revenue range, timeline, budget range. It also has one notes box.

A lead picks "$8,000 to $25,000" for revenue and "Under $750" for budget. In the notes box she writes, "Honestly we make about 40k a month and I will invest what it takes."

The dropdowns and the notes disagree. Dana's workflow should not guess. It should create a task for a person. The task should say:

- Who the lead is and what she asked for.

- The exact answers, quoted.

- Which answers conflict.

- That nothing has been sent to her yet.

- One next step: "Ask her which revenue and budget are right."

A person then writes the reply. That is the design goal. The form and the handoff give a person the facts to act on.

Test the form before real leads arrive

Build a small set of fake leads and run them through. My own test plan uses twelve. It includes a strong lead, a weak lead, a repeat submission, an out-of-scope business, a broken email, a conflicting pair of answers, an existing client, and a notes box with instructions in it.

The plan sets targets. I have not reported results from it here. These are the targets:

- No automatic rejections would go out.

- No lead would get two sequences.

- No existing client would get a cold pitch.

- No instruction in a notes box would be followed.

- The median first reply time across the first five test leads would be under 60 seconds.

The last target is a median on a small test set. It does not promise that every lead gets a reply within a minute.

Run your own test. Write down what you actually see. Mark anything you could not check as unknown.

Where I can help

If you want this built, my install is $1,500 fixed. It covers one GoHighLevel pipeline, one calendar, up to two lead sources, and three agreed sequences. It captures inquiries, routes them, follows up with copy you approve, and sends appointment reminders. I test with realistic scenarios and document the exceptions before handoff. The two-week target starts after access and scope are agreed.

Care is a separate $500 per month. It covers weekday checks, up to one hour of repair per month, a next-business-day first response, a weekly exception digest, and a monthly health report. It also includes one recommended improvement, with up to one hour of agreed change. It is optional. If your volume is low, you may not need it.

Either way, fix your form first. A clear form makes every later step easier to check.

Quick answer

Coaching Inquiry Form Checklist: What Each Field Must Do?

A form can ask too much or too little. The fix is simple. Decide first what someone must do with each answer.

An answer can do one of three jobs. It can help you route the lead. It can help you reach the lead. It can help a person understand the lead. If a field does none of these, cut it.

I build lead-to-booked-call workflows in GoHighLevel. This guide is what I would check before building anything on top of a form.