Before buying more traffic: test your website inquiry-to-appointment handoff

Choose the customer promise you are testing

A website can attract a suitable prospect and still lose the opportunity between a submitted inquiry and an agreed appointment. Before increasing advertising spend, trace that narrow handoff. This exercise asks whether a willing customer can reach the next promised step; it does not estimate how much traffic you should buy or how many sales a campaign will produce.

SBA's marketing guidance recommends describing the customer's sales steps and comparing marketing costs with results. BGA's original check below applies that principle to a website request. Write the actual promise first: a callback, a review of the request, or a confirmed booking. Those are different outcomes. A page that promises only a callback should not imply that a submitted form reserves a time.

Define evidence at each handoff

Create a short checklist with four columns: customer step, expected evidence, responsible person and recovery action. For submission, evidence might be a uniquely identified inquiry stored in the approved system. For staff handling, it is an assigned record with an acknowledgement or next action. For an appointment, it is an agreed date, time zone and service detail recorded through the normal booking process.

Keep the customer-facing confirmation and the downstream record separate. A success banner shows what the visitor saw; it does not prove that staff received the inquiry. An internal record does not prove a message was delivered or that the customer accepted an appointment. Save the relevant receipt or status for each outcome without copying unnecessary personal information into a general tracker.

Run a controlled test with an owner and a backup

Have the person responsible for the system authorize a clearly labeled test using approved fictional details and a contact channel the business controls. Identify any automated messages, calendar holds, billing or external routing before starting. Use an approved test environment where available. Do not create a real charge, message an unrelated person or consume a genuine customer slot just to complete a checklist.

Test the actual path a customer encounters, including a small screen and the advertised service choice. Check missing required information, an unavailable appointment and a repeated submission. State the expected result before each attempt. A duplicate should have a defined handling process; do not assume the software prevents it merely because the button became disabled.

Name a backup for an absent staff member and an escalation point for a failed notification. A request stored safely but left unassigned is an operating failure even if the form works. Record the time of the test, the observed outcome and who will fix the specific break. Keep test records clearly separated from sales reporting.

Use a cohort to locate the gap

Consider a fictional weekly cohort of 20 genuine website inquiries. Assume 16 have usable service and contact details, 10 receive the promised staff response, six become confirmed appointments and four appointments are completed. These are invented figures for teaching, not BGA results, industry benchmarks or a forecast.

In that example, 10 of 16 usable inquiries received the promised response, or 62.5%. Six of those 10 became appointments, or 60%. Four of the six appointments were completed, about 66.7%. Each ratio has a different denominator and suggests a different question. Review the six usable inquiries without a recorded response before concluding that the advertising audience is the problem.

Allow enough time for the cohort to progress and distinguish pending requests from failures. Do not mix this week's new inquiries with this week's appointments from older inquiries. Count unique genuine requests consistently, explain exclusions and keep cancellations visible. These measures identify questions; they do not establish why an individual customer did not proceed.

Collect only what the next step needs

FTC security guidance supports limiting collected information and restricting access to people who need it. For this exercise, ask whether each form field is necessary for the promised next action. An initial callback request may not need documents or detailed financial information. Use the business's approved retention and access process for the records you keep.

If staff must ask the same missing question repeatedly, improve the relevant field or instructions. If customers abandon a long form, test a shorter, truthful intake step without promising an appointment you cannot confirm. Review privacy, accessibility and other applicable requirements through the appropriate process; a successful handoff test is not a compliance certification.

Repair one break before increasing the load

Choose one observed failure, assign a fix and repeat the same controlled check. Then review actual completed customer outcomes over a defined period. Pair this exercise with BGA's capacity-planning and customer-acquisition-cost guides: a functioning handoff still needs available service capacity and affordable acquisition economics.

The owner should finish with a clear customer promise, evidence for every handoff, a named backup and a dated repair record. Increase traffic only as an intentional decision supported by those observations. Do not report extra revenue, delivered messages or completed appointments until their separate downstream evidence exists.

Original sources

• SBA — Marketing and sales; customer sales steps and measurement context checked November 13, 2026
• FTC — Start with Security; data minimization and access guidance checked November 13, 2026