Development guides / Websites and enquiries

A business website that makes enquiries easier to handle

A customer wants a quote but is unsure what to put in the form. Staff receive the enquiry and need several follow-up messages before they can price the work. Plan both sides when building the website.

A design shop and its work counter after evening rain
AI-generated illustration of the article’s setting.

The website is live. Where do enquiries go?

A business website can look polished while leaving buyers unsure what to do next: request a quote, book a service or describe a project? A generic contact button may leave staff repeatedly asking for the information they need before work can begin.

Before development, complete this sentence: “Once the customer supplies these details, this person takes the next action under these conditions.” The answer shapes page content, form fields and administration, not just button design. The quotation example below can also help you structure booking or payment journeys.

Website builder, connected form or custom development?

For service information, a portfolio and basic enquiries, an existing website builder and form may be sufficient. When each enquiry needs an internal quote, approval or status tracking, also plan the administration interface and connections to existing tools.

For booking and payment, first check whether an existing platform supports your staff, time slots, deposits and rescheduling rules. Consider custom work when those rules do not fit or data must move between systems. Include ongoing website, booking and payment service costs in the comparison.

Informational website

When services are straightforward and one person can handle enquiries, start by evaluating a website builder. Check content editing, form handling and maintenance before adding custom features.

Website plus existing tools

If your CRM or booking platform already works well, the website can be the front door. Confirm field mapping, failed-notification handling and data export before committing to the connection.

Custom enquiry workflow

If you need several staff roles, quote approvals or a status page for customers, assess those features individually. Decide who uses each screen, what they can do and how it will be handed over.

Connect submission, validation, assignment and follow-up. The enquiry list should still show unfinished work when a notification fails.
Illustrative workflowConnect submission, validation, assignment and follow-up. The enquiry list should still show unfinished work when a notification fails.

Follow one quote request all the way through

The example below illustrates an approach. It is hypothetical, not a client case study or a claim of delivered results.

Suppose a service business needs quotation requests. The site collects the service category and required information, creates a request number and assigns an owner. The owner checks the details and sends a quote; the customer can see its status. A failed notification leaves the request on the pending list.

This sample worklist keeps the request number, owner and next action together, so staff do not have to search email threads to identify who is handling it.
Illustrative interfaceThis sample worklist keeps the request number, owner and next action together, so staff do not have to search email threads to identify who is handling it.Sample data and a conceptual interface illustrate the design approach. This is not a screenshot of a client system.

Three design choices that stall enquiries

Asking for everything at once

Ask for enough information to arrange the next step. Someone exploring your service may not yet know detailed technical answers. Begin with their goal, contact details and essential constraints, then collect more as the discussion progresses. If an entry is wrong, identify the field and explain how to correct it.

Treating a sent email as a finished task

Sending a notification does not mean the enquiry has been handled. An absent colleague, a filtered email or a delivery failure can leave work waiting. Keep unassigned and unanswered requests in a list, and agree who checks it. Include that list when reviewing the development quote.

Finding the content owner at the end

Who approves the service names? Can the images be used publicly? When will the copy be ready? These questions affect the launch date. List the materials and name someone who can approve the content, so the website review can focus on whether the enquiry process works.

Test the whole enquiry process before launch

  • Submit on a phone and check required fields, confirmation and request number. Repeated taps should not create confusing duplicate work.
  • Check that the owner receives a notification, can find pending requests, and that unauthorised users cannot view other customers’ data.
  • Check the handover covers content editing, form-data export, account access and what to do when notifications fail.

Compare what each quotation includes

Compare whether quotations include content preparation, mobile layouts, content management, form handling, notifications, migration and handover. Page counts can hide the work that happens after submission. If the existing site is suitable, improving its enquiry workflow may be enough without rebuilding everything.

The launch date also depends on content approval and the readiness of booking or payment accounts. List what needs to be supplied and who will approve it before agreeing the date. After launch, check how many enquiries arrive, whether they contain enough information and whether staff can follow up.

Measure useful enquiries, not just visits

Check service-page visits, completed enquiries and enquiries with enough detail to assess separately. If traffic grows but requests remain vague, improve the service explanation or form. If detailed requests sit unanswered, review the internal handover. The figures help identify where the process needs attention.

Record the figures before making changes, then compare similar periods and traffic sources. Note any promotions or service changes at the same time. A contact-button click is a useful clue, but it is not a received enquiry; the redesign may be only one reason the figures changed.

Write the first brief for your developer

Prepare the service or product list, brand assets, content approver, enquiry owner and an example of a useful enquiry. If there is a launch date, identify what genuinely cannot wait. Complete the main journey first and phase other content separately.

Questions before you start

Can we improve enquiries without rebuilding the site?

Start with an assessment. If the current platform allows form changes, useful integrations and access to the required data, a focused improvement may be enough. Check platform limits, account access and notification records before choosing a rebuild.

Does every company website need a custom backend?

No. Standard content management and a form may be enough. Consider a custom administration system when existing tools cannot handle assignment, approvals, status tracking or the other work your team needs.

ProApp

Want to improve your website or day-to-day work?

Tell us what you want to achieve, how you work today, your budget and target date. We can then agree the scope and schedule.