The send button starts a process
A visitor has understood the offer and completed the form. Their experience now depends on the team: who receives the enquiry, how they see its information and who prepares a reply. An organised website needs a workflow that can be explained and checked, alongside clear fields and a visible submit button.
This guide proposes a workflow for a business receiving quotation enquiries. Its examples are illustrative, not measured commercial outcomes. Adapt the stages to actual volume: a small team can begin with a simple list, while CRM integration becomes useful when it improves the visibility of work and ownership.
Separate acknowledgement from the business reply
Display an acknowledgement after the application has received and recorded an enquiry according to its implemented workflow. If saving fails, the message should help the person correct the issue or retry. On-page acknowledgement, an email notification and a colleague's reply are different events and deserve separate tracking.
MDN documents sending form data to a server, while the W3C WAI tutorial explains clear success and error feedback. For the team, the practical question is whether an enquiry can still be found if its notification email is delayed. Email can signal new work, while the enquiry record should remain accessible in the chosen system.
A simple workflow with clear ownership
Stage names should describe what is happening and who owns the next action. Avoid a single list where every enquiry is vaguely marked as in progress. The sheet below is an organisational proposal: agree with the team what information is retained and how status changes after each interaction.
| Stage | What to record | Next action |
|---|---|---|
| Received | Internal reference and time recorded | Check required information |
| Assigned | Owner and assignment date | Review the enquiry and choose next steps |
| Clarification | Questions sent and missing information | Customer reply or agreed follow-up |
| Proposal prepared | Proposal version and scope limits | Internal review before sending |
| Reply sent | Time sent and delivery status when available | Next agreed contact |
| Closed | Known outcome or reason for closure | Archive under the agreed rules |
Tests that reveal where an enquiry can be lost
Before activation, prepare fictional data for a full workflow test: form submission, recording, access by the responsible person and preparation of a reply. Also test a mistyped email address, a missing required field, a network interruption and a repeated press of Send. Define the expected behaviour for each case, including how duplicates are prevented.
Test a failed notification separately, along with reassignment when the owner is unavailable. A technical error list is of little use if nobody monitors it. Decide who notices a problem and how it is resolved; do not use real customer data or message outside recipients merely to check whether an integration responds.
Measure ownership and response quality
The number of submitted forms only measures entry into the workflow. For operations, consider time to ownership, unassigned enquiries, outstanding clarifications and replies with failed delivery. Mark test enquiries separately so they do not become commercial results in reports.
Set a realistic response window based on working hours and capacity; do not publish promises the team cannot support. If Analytics is used, keep aggregate visit measurement separate from the information needed to answer an enquiry. To start a discussion with AURENIQ, describe how enquiries arrive today and where they get stuck, without including customers' personal information.
Common questions
Is a form that sends an email enough?
It depends on the workflow. Check where the enquiry is retained, who owns it and how failed notifications are noticed. A small team may only need a simple organised record.
Do I need a complete CRM immediately?
No. Define stages and responsibilities first, then choose tools proportionate to volume and required integrations.
Does an acknowledgement mean the proposal is ready?
No. Confirm only the event the application has verified. Reviewing an enquiry and preparing a proposal are separate steps.
Can AI help with enquiries?
Classification and drafting can be evaluated with permitted data and review. AI integration is a separate decision; a clear enquiry workflow remains useful without it.
Sources and further reading
An AURENIQ editorial guide. Examples are illustrative, not client results. Vendor documentation is checked for the specific implementation.
Services for this topic
What is the next step for your project?
Describe the problem, the people involved and your existing applications. We can clarify a useful first version and its dependencies before preparing a proposal.
Discuss your project ↗