Clarification Contact

Clarification contact is a quick, targeted outreach to the client during the build phase when your team needs a specific answer to keep moving. It is not a scheduled call, not a progress update, and not a list of 15 questions. It is a focused message asking for one or two pieces of information that the builder cannot proceed without.

Why This Matters

Every build hits a point where the builder needs information that was not on the Onboarding Form or in the Build Nuances. The client listed six services but did not specify which one is their highest-revenue offering. The logo they uploaded is low resolution. The form says they want a booking calendar but does not specify whether it is for consultations, service appointments, or both. These gaps are normal and expected.

What matters is how you handle them. If the builder stops working and sends a long email with every open question, two things happen: the client takes days to respond because the email feels overwhelming, and the builder sits idle waiting. If the builder makes assumptions and keeps building, they risk getting it wrong and creating rework.

Clarification contact solves this by making the outreach fast, specific, and low-friction. A quick phone call, a two-sentence text, or a short email with exactly what you need. The client can answer in 30 seconds, and the builder is unblocked. Done right, clarification contact keeps the build moving without becoming a burden on the client.

How to Think About It

Clarification contact is a surgical instrument, not a catch-all. If you find yourself reaching out to the client 5 times during a build, your Onboarding Form has gaps that need fixing. The form should capture 90% of what the builder needs. Clarification contact handles the remaining 10%.

Batch your questions when possible. If the builder has three unrelated questions, send them in a single message rather than three separate touchpoints. But keep the total scope small. Three short questions in one message is fine. Ten questions means you missed something in your information-gathering process and need to address the root cause.

Choose the right channel based on urgency and complexity. A quick factual question like “Do you want your phone number displayed on every page or just the contact page?” works perfectly as a text or Slack message. A question that requires explanation or context, like “Your form mentions two locations but your Google listing only shows one. Can you clarify?”, might work better as a brief phone call.

Respect the client’s time above all else. They hired you so they would not have to think about this stuff. Every clarification contact should feel effortless to respond to. Write the question so clearly that the client can answer with a single sentence or a yes/no.

Common Mistakes

Sending vague or open-ended questions. “What do you want for the homepage?” is not a clarification question. “Should the homepage hero section feature your emergency service or your full service list?” is. Give the client a decision to make, not a blank canvas to fill.

Reaching out too many times during a single build. If the client hears from you more than twice during the build for clarification, something broke earlier in the process. Audit your Onboarding Form and Build Nuances to find the gaps and fix them for future clients.

Not documenting the answers. The client tells you over the phone that they want the booking calendar to show 30-minute slots. If that answer is not recorded somewhere the builder can reference, it might as well not have been asked. Log every clarification response in the same place your other build information lives.

Asking questions the builder could answer themselves. Before reaching out to the client, check whether the answer is already in the onboarding form, the build nuances, the client’s existing website, or their Google Business Profile. Asking a question the client already answered makes your agency look disorganized.

Using clarification contact for progress updates. This is a common conflation. Clarification contact is inbound to the client for information. Progress updates are outbound from the agency with status. Do not mix them. When you bundle a question with a progress update, the client focuses on the update and forgets to answer the question.

Tools Involved

Clarification contact happens through whatever channel the client prefers. GHL Conversations can centralize phone, SMS, and email communication in one thread, making it easy to reference later. For agencies that track build progress in GHL Pipelines, the clarification and its response can be noted on the pipeline card. Some agencies use GHL Workflows to automate a reminder if the client does not respond within 24 hours, keeping the build from stalling.

Where This Fits

Clarification contact sits in the Information Gathering phase at sequence position 19, but it functionally occurs during the build phase. It depends on the build execution being underway, because that is when gaps in information surface. It connects back to Business Details and Build Nuances as supplementary information. The goal is always to minimize the number of clarification contacts needed by improving the upstream information-gathering elements.

Common Questions

How quickly should the client respond to a clarification request? Set the expectation during quick start that build-phase questions need a response within 24 hours. If the client is unresponsive, send one reminder, then make your best judgment call and flag it for review during the walkthrough. Do not let a single unanswered question hold up the entire build.

What if the client keeps changing their mind during clarification? This is a scope management issue, not a clarification issue. If the client is revising earlier decisions, acknowledge the change, document it, and adjust the build. But if it becomes a pattern, address it directly. Constant changes during the build extend the timeline, and the client needs to understand that trade-off.

Should clarification happen by phone, text, or email? Match the channel to the question. Simple yes/no questions work great via text. Questions that need context or explanation work better on a quick call. Email works for questions where the client might need to look something up. When in doubt, text first. It is the fastest path to an answer for most clients.