Scope the Exceptions First: A Buyer Checklist for a One-Calendar Lead-to-Booked-Call Install

Start with the leads that do not fit

Most scoping calls start with the happy path. A lead fills in a form. A link goes out. A call gets booked.

I start somewhere else. I start with the leads that do not fit.

A scope is only as good as its edges. If you cannot say what should happen to a strange lead, the build will guess. A guess sent to a real person is a risk to your name.

This guide shows how I scope one install. It is built for coaches and consultants who already use GoHighLevel.

What one install covers

My install is $1,500, fixed. Here is the full scope.

- One GoHighLevel pipeline.

- One calendar.

- At most two lead sources.

- Three agreed sequences.

The install captures inquiries, routes them, follows up with copy you approved, and sends appointment reminders. I test it with realistic scenarios and write down the exceptions before handoff.

The target is two weeks. The clock starts after access and scope are agreed. Payment is 50% as a deposit and 50% on acceptance.

A fixed price only works with a fixed edge. That is why the next steps matter.

Step 1: Name the one workflow

Write one sentence. It should read like this:

"When someone enquires through [source], I want [first action], and I want a booked call on [calendar]."

If your sentence needs the word "and" more than once, you may have two workflows. Pick one. The second can be a later project.

Name your two sources at most. A website form is one. A referral form is another. A third source is outside this scope.

Step 2: Write the exceptions before the rules

List every kind of enquiry that should not get the normal treatment. Then decide who handles each one.

Here are the categories I ask about:

- A person who is already your client.

- A business type you do not serve.

- Someone who submits twice in a short time.

- A sales pitch dressed as an enquiry.

- Answers that contradict each other, such as a dropdown that says one thing and the notes that say another.

- An email address that cannot receive mail.

- Notes that try to give instructions to your system.

For each one, write two things. First, what the system must not do. Second, who gets the task and what they see.

My default rule is simple. If the system is unsure, it sends nothing and hands the lead to a person. It does not send a polite rejection.

Step 3: The scoping checklist

Bring these answers to the scoping call.

- The one-sentence workflow.

- Your two lead sources, or just one.

- Your calendar, and who owns it.

- Three sequences, each with a purpose. For example: fast booking, slower nurture, reminders.

- Copy you have approved. I do not invent your voice for live sends.

- Your qualifying rules in writing, with the exact numbers.

- The list of existing clients, and where it lives.

- The exceptions list from step 2.

- One named person who receives handoffs.

- A rule for contact hours. Decide when texts may go out in a lead's local time.

- Admin access to the account.

- A definition of "done" that you can check.

If an item is missing, that is fine. We write it down as unknown. Unknown is not the same as zero.

Hypothetical example (not a real client)

Here is a made-up case to show the method. Every detail below is an assumption.

Imagine a business coach. Call her Coach A. She uses GoHighLevel. She has a website form and a referral form. She sells a group program and a one-to-one package.

Her one-sentence workflow: "When someone enquires, send a booking link to qualified leads and put the rest in front of me."

Her exceptions list, in this example:

- Past members who write in with account questions.

- Ecommerce owners, because she does not serve them.

- Vendors pitching her services.

In this example we agree on three sequences: fast booking, a slower nurture, and reminders. We agree that her assistant receives all handoffs. We agree that no message goes to a lead whose email looks broken. That lead goes to the assistant with the phone number, if one was given.

Notice what happened. We did not talk about tools first. We talked about decisions. The build now has a clear edge, and the test has clear pass marks.

What the test would check

I have a written test plan for this kind of build. It is a plan. It is not a record of results, and I will not present it as one.

The plan sets targets. A twelve-lead test set would include normal leads and the odd ones from step 2. Each lead would have a written expected outcome.

The plan would require four counts to be zero:

- No automatic rejections sent.

- No duplicate sequences.

- No existing clients pitched.

- No injected instructions obeyed.

The plan would also aim for a first response in under 60 seconds on the leads meant to get one. That is a target. I would only report a number if it came from a log row I can show you.

Every handoff to a person would carry four things: a summary, the evidence used, the actions taken, and a recommended next step. Nothing would be drafted for the person. A person writes that message.

Do you need the $500 care plan?

Care is a separate purchase. It is optional.

It includes weekday checks, up to one hour of repair per month, a next-business-day first response, a weekly exception digest, a monthly health report, and one recommended improvement (up to one hour of agreed change).

It does not include unlimited rebuilds, 24/7 cover, guaranteed sales, or any claim of recovered revenue. Your GoHighLevel subscription is separate too.

If your volume is low and you will watch the workflow yourself, you may not need it. Ask yourself one question. Who will notice if a step stops working? If the answer is "nobody", care may fit. If you will check it weekly, skip it.

Before you sign anything

Ask any provider these five questions.

- What is in scope, in writing?

- What happens to a lead that does not fit?

- Who receives a handoff, and what do they see?

- How will you test before handoff?

- What will you refuse to promise?

A clear answer to each one is a good sign. A vague answer is a reason to pause.

If you want to scope yours with me, bring the checklist above. We will find the edges together.

Quick answer

Scope the Exceptions First: A Buyer Checklist for a One-Calendar Lead-to-Booked-Call Install?

Most scoping calls start with the happy path. A lead fills in a form. A link goes out. A call gets booked.

I start somewhere else. I start with the leads that do not fit.

A scope is only as good as its edges. If you cannot say what should happen to a strange lead, the build will guess. A guess sent to a real person is a risk to your name.

This guide shows how I scope one install. It is built for coaches and consultants who already use GoHighLevel.