Guide
Business website enquiry checklist: what to agree before the build
Prepared · Cenqora Labs
A business website needs a clear offer, a useful route to enquiry and a reliable handoff to the person who follows up. Before choosing a design or a platform, agree what visitors should understand, what information you need and how the team will know a request was received.
This checklist is for service businesses, including teams in India working with customers remotely. It helps define a website project; it does not promise search traffic, enquiries or sales.
Start with one buyer and one next step
Describe the person the page serves and the question that brings them there. A founder comparing workflow automation services needs different detail from a customer seeking support for an existing project.
State the service, who it suits, the deliverables and the limits of the engagement in plain language. Explain the next step before asking for information. Use a specific action such as requesting an assessment when that is the actual process.
Separate examples from completed client work. A concept illustration can explain a proposed workflow, but it cannot demonstrate a result that has not happened.
Choose the information needed for a useful reply
Every required field should have a reason. Decide which information is necessary for the first conversation and which can wait. Explain how visitors can contact the team if the form does not work for them.
| Decision | Question to resolve before building |
|---|---|
| Offer | Can the visitor explain what the service covers? |
| Enquiry fields | Which fields are needed to route and answer the request? |
| Receipt | What confirms that the server accepted the enquiry? |
| Ownership | Who follows up, and who covers an unavailable owner? |
| Integration | Which system stores the request, and what happens if the next connection fails? |
| Measurement | Which accepted enquiries can be measured after consent? |
Keep personal details out of analytics. Form field values, names, email addresses and message text belong in the agreed enquiry process, not in page-view or marketing event parameters.
Define received, notified and followed up separately
A success message should follow an accepted server response. Clicking a submit button is not proof of receipt. Sending a notification is a separate step, and a notification is not proof that someone has replied.
Consider this illustrative sequence: a valid request is stored, a reference is returned, an owner is assigned and a notification is attempted. If the notification fails, the stored enquiry should remain recoverable. These are design decisions for a sample workflow, not claims about a client's system.
Agree what visitors see when validation fails, when a connection is unavailable and when the result is uncertain. Avoid inviting repeated submissions without a way to recognise duplicates.
Check the published pages, not just the design preview
Open the important service pages directly on the public domain. Check that the main copy is readable on a phone, navigation works with a keyboard, and the enquiry action is easy to find.
Review each page's title, description and canonical address. Confirm that real public pages load, missing pages return a proper not-found response and private pages stay out of the sitemap. These checks support discovery; they do not guarantee Google will index or rank a page.
Use the lead follow-up launch checklist to plan checks for valid, invalid and repeated requests, failed handoffs and unavailable owners. Run submission checks in an isolated environment first. Coordinate any live delivery check with the people receiving the request.
Set the handover and measurement rules
Agree who can update content, who maintains integrations and what support is included. Record access responsibilities without placing credentials in a public brief.
Define an accepted enquiry before reporting conversions. Review qualified enquiries, follow-up completion and known commercial outcomes separately. If a visit's source is unavailable, keep it unknown rather than crediting SEO.
Cenqora Labs scopes business websites and enquiry journeys alongside lead follow-up and CRM workflows. Request an assessment with the current handoff and the part you want to improve.
For the next step, read how to automate website enquiry follow-up.
