The Inquiry Handoff Checklist: Evidence, Owner, Next Action

Why check your handoffs

Some inquiries should go to a person, not to automation. The form answers may disagree. An email address may be broken. The sender may already be a client.

In these cases, your system should hand the inquiry to a person. Check that handoff closely. A vague one only says, "Check this lead." A useful one says what the lead wrote, who owns it, and what happens next.

This guide gives you a checklist for that. Use it to review your own setup, or to brief anyone who builds it for you.

Part 1: Evidence

Evidence means the exact facts the person needs. They should not have to open five tabs to find them.

Check that each handoff includes:

- A short summary: who the lead is and what they want. One paragraph.

- The lead's name, business, and contact details, exactly as submitted.

- The form answers, quoted word for word.

- The notes field, quoted word for word.

- The reason this lead was not handled automatically.

- A plain statement of what was sent to this person. If nothing was sent, it says "Nothing has been sent."

- The date and time of the inquiry.

The summary helps a person read fast. The quotes let them check the facts. Keep both. Do not replace the quotes with the summary.

Part 2: Owner

This part is general advice. It is not a promise of what any particular build includes.

An owner is one named person. A team inbox is not an owner. Neither is "whoever sees it first."

Check these points:

- Each handoff names one person.

- That person knows they own it.

- You have chosen a backup for days when the owner is away.

- You have decided what happens if the owner does not act.

If you set a time limit, write it down. Pick a number you can keep. Test it before you rely on it.

Part 3: Next action

The next action is one sentence. It starts with a verb.

Good examples:

- "Call the lead today. The email address is broken."

- "Ask the lead which revenue figure is correct."

- "Reply to this client about their account question."

Bad examples:

- "Follow up."

- "Look into this."

One more rule. Do not put a draft message in the handoff. A person writes the reply. The handoff gives them the facts and the next step.

Worked example (hypothetical)

This example is made up. The person, answers, and business are not real. It shows how the checklist reads when filled in.

Suppose a coach named "Alex" submits your inquiry form. Alex picks "Under $750" for budget. In the notes, Alex writes, "I will invest whatever it takes."

The two answers disagree. Your rules do not say which one to trust. So the system stops and creates a handoff.

- **Summary:** A coach asking about help with follow-up. The budget answers conflict.

- **Evidence:** Budget dropdown: "Under $750". Notes: "I will invest whatever it takes." Nothing has been sent to Alex.

- **Owner:** The founder. Backup: the operations contact.

- **Next action:** Ask Alex which budget is correct before any booking link goes out.

Notice what is missing. The system did not pick a side. It did not send a rejection. It did not guess.

A second hypothetical. A lead's email address has two @ signs. Your check should catch this before any send. The handoff would carry the phone number and say, "Call this lead today."

What a test plan can and cannot tell you

A good build has a test plan. One plan I wrote sets targets for twelve made-up inquiries. Some are clean. Some are conflicts, existing clients, spam, or broken emails.

The plan targets these outcomes:

- Five of the twelve would go to a person.

- No one would be sent a rejection.

- No existing client would get a cold sales sequence.

- Instructions hidden in a notes field would not be obeyed.

- Each handoff to a person would carry four items: a summary, the evidence used, the actions taken, and a recommended next step.

These are targets. They are not results. I have not run this plan and I am not reporting any outcome from it. Until the tests run and you can see the log rows, treat it as a plan.

Ask any builder to show you the actual log after the run. Twelve test leads would give twelve rows. They would not show how your real traffic behaves.

Your review checklist

Use this list on your own setup:

- [ ] Every handoff has a short summary.

- [ ] Every handoff quotes the lead's own words.

- [ ] Every handoff says what was sent. Or that nothing was sent.

- [ ] Every handoff names one owner. You have chosen a backup.

- [ ] Every handoff has a one sentence next action.

- [ ] No handoff contains a pre-written reply.

- [ ] No lead is told they do not qualify by automation.

- [ ] Conflicting answers go to a person. The system does not pick a side.

- [ ] Existing clients are checked before any sequence starts.

- [ ] Email addresses are checked before any send.

- [ ] Every inquiry leaves a log row, including duplicates and ignored ones.

- [ ] You have seen the log from a test run, not only a plan.

If you cannot tick a box, that is your next fix.

Where help fits

You can build this yourself. The checklist works either way.

If you want help, my install is $1,500 fixed. 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. The target is two weeks after access and scope are agreed.

Care is optional and separate. It costs $500 a month. It includes weekday checks, up to one hour of repair a month, and a next business day initial response. You get a weekly exception digest and a monthly health report. The report shows missing data as missing. It also includes one recommended improvement, with up to one hour of agreed work.

Care does not include unlimited rebuilds or round the clock cover. It does not promise sales. If your workflow has low volume, you may not need it. Your GoHighLevel subscription is separate.

Quick answer

The Inquiry Handoff Checklist: Evidence, Owner, Next Action?

Some inquiries should go to a person, not to automation. The form answers may disagree. An email address may be broken. The sender may already be a client.

In these cases, your system should hand the inquiry to a person. Check that handoff closely. A vague one only says, "Check this lead." A useful one says what the lead wrote, who owns it, and what happens next.

This guide gives you a checklist for that. Use it to review your own setup, or to brief anyone who builds it for you.