Coaching Inquiry Form Fields That Let a Person Rescue the Hard Leads

By Roxli Cahayag · 2026-09-25

Why most forms fail on the hard leads

Most advice about inquiry forms is about getting more submissions. This guide is about something else. It covers what your form needs so a follow-up workflow can handle the easy leads and pass the odd ones to you.

I build lead-to-booked-call automation in GoHighLevel for coaches and consultants. The easy lead is rarely the problem. A strong fit gets a booking link. A weak fit gets one useful email and no chase. Nobody is told they do not qualify by a robot.

The trouble comes from the leads in between. A typo in an email address. A person who already pays you. Answers that disagree with each other. Your form decides whether those cases are visible or lost.

Start with one question

Ask yourself what a person needs to see to decide in ten seconds. If a field does not help a rule or a human decide, cut it.

Every field should do one of three jobs.

- Let you reach the person.

- Let a rule sort the person.

- Let you understand the person when a rule cannot.

The checklist: fields to include

Use this as a build list.

- Full name. A person reading a handoff needs to know who this is.

- One email field. Ask for it once and validate the format. A mistyped address is a lost lead, and nobody ever finds out.

- Phone number. Make it required if you want a backup route. When an email is broken, a phone number is the way to rescue the lead.

- Business or program name. It gives a person context when they read the lead.

- Business type as a dropdown. Use a short list of the types you serve, plus "Other". Do not use free text here.

- Monthly revenue range as a dropdown. Use ranges, not exact numbers.

- Hours per week lost to manual work, as a dropdown.

- Timeline to start, as a dropdown.

- Budget range, as a dropdown. Include a low option so people can be honest.

- Time zone. You need it to hold a text until a polite hour.

- Consent to be contacted by email and, separately, by text.

- One optional notes box, with a clear label.

What to leave off

Skip anything you would never act on.

- Do not ask for a company address, a birthday, or a social handle you will not check.

- Do not ask five versions of the same question.

- Do not add a "How did you hear about us" field with 30 choices. Keep it to five or fewer, or drop it.

A long form loses people. A short form with the right dropdowns gives a rule enough to work with.

Treat the notes box as words, not instructions

The notes box is where people explain themselves. It is also where things go wrong.

Someone may write a number that contradicts their dropdown. Someone may write text that tries to give orders to your system. Automated tools read that text, so it must never change how a lead is scored or routed.

My rule is simple. Sort on the ticked answers only. Show the notes to a human. If the notes and the dropdowns disagree, do not pick a side. Send both to a person, word for word.

Hypothetical example

This is a made-up scenario, not a client story.

Imagine a coach called Jo. Her form has a revenue dropdown, a budget dropdown, and a notes box. A visitor ticks "$8,000 to $25,000" for revenue and "Under $750" for budget. In the notes, they write that they earn about 40k a month and will invest whatever it takes.

There are two easy mistakes. If the workflow believes the notes, it sends a booking link to someone who may not fit. If it believes the dropdowns, it puts a possible strong lead on a monthly newsletter.

A better workflow does neither. It creates a task for Jo. The task quotes both sets of answers. It says nothing has been sent. It suggests one next step, which is to ask the person which answer is true. Jo writes that message herself.

Checks to run before any message goes out

Some checks must happen before the workflow acts. Build these in.

- Email check. Confirm the address is deliverable before any send. If it is not, create a task with the phone number and send nothing.

- Existing client check. Compare the email against your client list before any tag is applied or any sequence starts. If it matches, create a task, not a sales sequence.

- Duplicate check. If the same person submitted recently, stop and log it. Do not start a second sequence.

- Scope check. Run it before the score. If the business type is outside what you serve, create a task, even when the score is high.

Every lead gets a log row, including duplicates and ignored senders. Nothing should vanish.

How I would test it

I use a test plan with twelve invented leads. The plan has not been run as evidence yet. It covers clean leads, a borderline lead, a duplicate, a broken email, an existing client, a conflicting lead, and an injection attempt in the notes.

If the build is right, the plan targets these outcomes.

- No one would receive an automatic rejection.

- No duplicate would start a second sequence.

- No existing client would get a cold pitch.

- No instruction in a notes box would be obeyed.

- The median first email time across the five leads that route themselves would be under 60 seconds.

Those are targets, not results. A text to a lead who writes at 2 AM would be held until morning. I would only report numbers I can point to in a log row. With twelve test leads, I would say twelve.

Where the install and care fit

My scoped install is $1,500. It covers one GoHighLevel pipeline, one calendar, up to two lead sources, and three agreed sequences. I test with realistic scenarios and document the exceptions before handoff.

Care is optional at $500 a month. It includes weekday checks, a weekly exception digest, a monthly health report, and up to one hour a month of repair or agreed improvement. I give an initial response by the next business day. If your volume is low, you may not need it.

Either way, start with the form. Pick your dropdowns, add the phone field, and write the notes label. Then check what a person would see when a lead does not fit the rules.

Book a discovery call

See the demonstration builds