PRACTICAL GUIDE • U.S. BUSINESSES
A checklist to connect your website to inquiry follow-up
Your website can collect inquiries while your team struggles to follow up. Use this checklist to inspect the full journey: offer, form, acknowledgment, human response, next step, and useful measures. Written for owners and managers of small and medium-sized U.S. businesses.
Choose one journey to start: a quote request, a school visit, or a service appointment. Write down what the person needs and which next step your team can handle. Connecting every channel at once makes it harder to locate the first journey's weak point.
You can use this checklist with your current website, a shared inbox, and a spreadsheet with restricted access. Responsibilities come before tools. This guide is open: no signup, download, or purchase is required.
BUSINESS TECHNOLOGY
Eight checks before you automate
- 01
Make the offer understandable
On the page you choose, explain the problem you solve, the area you serve, what is included, and the next step. Ask someone outside your business to explain the offer back to you. State business hours and the time zone; make language choice clear if you serve customers in English and Portuguese.
- 02
Test the whole journey on a phone
Open the page, find the button, fill out the form, and check the confirmation screen. Test keyboard navigation and invalid fields too. Have someone else repeat the journey. Label test records and exclude them from metrics; avoid sending test messages to real customers.
- 03
Ask for what you actually need
Collect a way to respond, the service of interest, and the information needed to route the request. Explain how you use the data. Keep documents, student details, and sensitive information out of an initial inquiry form. Each qualification question should support a specific decision.
- 04
Separate acknowledgment from response
An automatic acknowledgment explains that the request arrived and when to expect a reply. Claim receipt only after the system confirms delivery. Choose a human-response target your business can meet during its operating hours and explain how after-hours requests are handled.
- 05
Assign every inquiry to a person
Name the queue owner, the backup for absences, and the point when an unanswered inquiry gets escalated. Record received, assigned, responded, next step, and closed. A request should not go missing just because it leaves one person's inbox.
- 06
Build in a human handoff
Every flow needs a monitored way to ask for help. Route exceptions, questions, and replies the automation cannot handle to a person with context. Stop appropriate reminders after a reply, cancellation, or closure; agree on an attempt limit and honor contact preferences.
- 07
Record the next step
Each open opportunity needs an action, an owner, and a due date: call, request information, send a quote, or confirm a visit. Booked, attended, and sold are different stages. When closing a request, record a simple reason instead of letting it disappear from the queue.
- 08
Test failures and changes
Check what happens when delivery fails, someone repeats a request, or an appointment moves. Verify recipients, team access, and failure alerts. Repeat the test after changing the form, inbox, calendar, or integration. If a channel fails, provide a working contact alternative.
Create a minimal record and remove duplicates
For each inquiry, record an ID, date and time zone, known or unknown source, service, owner, stage, first human response, and next action with a due date. Keep contact details in the authorized operational system; analytics events do not need names, email addresses, phone numbers, or message text.
Agree on a repeat-request rule. An example to adapt: the same person asking about the same need within a short period creates one opportunity with multiple interactions. A new need may create a new opportunity. Do not merge different people just because they share a household email or phone number. Exclude spam and tests, keep the history, and document the rule.
Choose up to five measures that inform a decision
Valid unique inquiries: opportunities received in the period after deduplication, excluding spam and tests. Separate known channels from unknown sources. A phone-button click shows intent; count a request only when you can confirm it.
First human response: elapsed time from receipt to a person's first reply, separate from the automatic acknowledgment. Choose elapsed clock time or business hours and keep that rule consistent. Report the median for answered requests and the number still waiting separately; a median alone would hide the forgotten ones.
Booking rate: unique opportunities with a first booking ÷ eligible opportunities received in the same cohort. Define eligibility in advance and allow the agreed follow-up window. Do not divide all bookings this month by this month's inquiries when some bookings came from earlier inquiries.
Attendance: completed appointments ÷ appointments scheduled to occur in the period. Define how cancellations and rescheduling are treated and count each appointment once. Sales conversion: opportunities with a confirmed sale or enrollment ÷ eligible opportunities from the same cohort after the follow-up window. If you lack those records, report the gap instead of estimating sales.
Show counts alongside rates. With few inquiries, a change may reflect chance, seasonality, or a different mix of demand. Attribution has limits too: forms, calls, calendars, and a CRM do not automatically share the same record.
Illustrative example: a school visit
A family requests a visit on the website. The system acknowledges receipt, the assigned person checks the request, and the team offers available times. Once confirmed, a reminder explains how to reschedule or contact the team. The owner records the completed visit and the next step. Enrollment counts as an outcome only after it is confirmed in the school's system.
If the family submits the form and then calls about the same visit, connect both interactions to one request. If a reminder receives a question, hand it to the team and pause the appropriate automatic sequence. This is a process illustration, without client data or a promise of results.
Copy this worksheet for your next review
Journey and audience: __. Page and next step: __. Owner and backup: __. Hours, time zone, and response target: __. Human help channel: __. Duplicate rule: __. Stages and closure condition: __. Full journey last tested on: __.
Period or cohort: __. Valid unique inquiries: __. Still waiting for a human response: __. Recorded next steps: __. Data limitation: __. Hypothesis about the bottleneck: __. One change to test: __. Owner and review date: __. Change one stage at a time to make the result easier to interpret.
Further reading and your next step
April Dunford provides a way to think about your audience, your offer's value, and customer alternatives. Traction, by Gabriel Weinberg and Justin Mares, is a reference for exploring acquisition channels. Testing Business Ideas, by David J. Bland and Alexander Osterwalder, guides hypothesis testing. The checklist and examples above are EAGLE BS's original application, rather than a reproduction of those books.
Once you find the bottleneck, decide whether organizing the current process is enough or connecting tools would help. For support with your website, inquiry follow-up, and measurement, explore Websites & Business Automation. Setup, capacity, and usage costs are defined in a proposal for your U.S. operation.
RELATED U.S. SERVICE
Websites & Business AutomationCONTINUE WITH ANOTHER GUIDE
Business technology
How to evaluate an AI tool before you buy it
Compare alternatives, total cost, quality, and human review. An open guide with a test hypothesis, experiment limits, and a decision worksheet for U.S. businesses.Read article ↗EAGLE BS
Want to organize this journey for your business?
Tell us where inquiries arrive and where follow-up gets stuck. We can assess your website and define a scope for your U.S. operation in English or Portuguese.