A website enquiry journey starts before someone presses Send and continues after a message reaches the business. For an Albany startup commissioning a site, the contract should explain that whole journey. An attractive contact page is only one part of a working service.
Use these steps to prepare questions for a website provider before committing. The aim is to understand the proposed work, what staff will receive and how the journey will be tested. This is a planning process, not a review of any particular local agency.
Step 1: describe the enquiry you want to receive
Choose one ordinary customer task. For example, a new business offering appointments might want a visitor to ask whether a service is suitable before discussing an available time. That is different from accepting a confirmed booking or taking payment.
Write what the visitor needs to know first: the service offered, the area served, the type of request accepted and any limitations. Then ask the provider which parts of that explanation are included in the work. Avoid describing every button as a conversion without agreeing what it actually means.
Step 2: trace the proposed journey on paper
Ask to see the route from a relevant page to the enquiry form, the confirmation shown and the destination staff will use. Include what happens when a required field is missing or someone wants to correct an entry.
Separate the visitor’s confirmation from the internal notification. A screen saying a request was submitted does not prove someone in the business has read it. Ask how staff will identify a new message and how the customer will understand the next step.
- Identify the information page and enquiry action.
- Describe the fields and useful error messages.
- Follow the request to its receiving location.
- Define the staff response and any handover.
Step 3: decide which information belongs in the form
Ask why each field is needed at this stage. A simple availability enquiry may not require a full street address, identification document or detailed personal history. Distinguish information needed to reply from details that can be discussed later through an appropriate channel.
Clarify who handles the information, which services receive it and what wording visitors will see. The OAIC’s small-business guidance explains that Privacy Act coverage varies and provides a checklist. Do not assume every startup is exempt, or that a provider’s generic privacy page settles your particular obligations.
Record who will obtain appropriate advice and supply approved wording. Ask whether the provider’s proposal includes implementing that wording, changing fields and explaining the relevant settings to your staff.
Step 4: turn the journey into a written scope
List the pages, form behaviour, notifications and receiving arrangements you expect. Ask which integrations are included and which require another service or subscription. If staff need to see enquiries in a shared system, identify whether that connection is part of the quoted work.
Business.gov.au’s quoting guidance highlights clear work descriptions, itemised costs, variations and dates. Use those categories to compare written proposals. A low headline build price is difficult to assess when message storage, revisions or staff training are undefined.
Step 5: agree on realistic acceptance checks
Before signing, ask how you and the provider will demonstrate that the agreed journey works. Include an ordinary mobile visit, an incomplete entry, a successful test request and staff finding that request in the intended place.
Use approved invented test details rather than real customer information. Agree how test messages will be marked and removed where appropriate, so they are not mistaken for customer demand. A screenshot of the form is not equivalent to evidence that the receiving process worked.
Ask who records defects, who decides a correction is satisfactory and what happens if a connected service behaves differently from the original assumption. Keep those questions separate from an unsupported promise that every visitor will enquire.
Step 6: define responsibility after launch
Clarify who checks the receiving inbox or system during ordinary operations, including when the usual person is away. Ask which technical faults the provider will investigate, how to report them and whether support is included or separately charged.
Discuss changes such as a new staff member, a changed contact address or a revised service area. Find out which changes staff can make themselves and which require assistance. Record the agreed limits; a maintenance arrangement should not be assumed to include unlimited redesign or guaranteed customer response times.
Step 7: check continuity before committing
Ask who controls the domain, website account, receiving service and relevant exports. Understand the handover material, recurring charges and steps involved if another provider takes over. An export is useful only if its contents and the receiving process are understood.
The government’s contract-ending guidance recommends checking obligations, notice and money payable, with legal advice where needed. Settle unclear terms before accepting the arrangement. Your startup should finish the comparison knowing how an enquiry travels, who acts on it and how that work can continue.