Business workflows
Website enquiries get lost after submission: how to fix the handoff
A visitor fills in your form, sees a success message and waits. Inside the business, the notification may reach a shared inbox without becoming anyone's next task. Start by tracing one request through the actual process. Find where it is saved, who should respond and how that person knows what to do. That small exercise gives you a clearer starting point than buying another tool.
Separate delivery from responsibility
Ask two different questions: did the request arrive, and did someone accept responsibility for it? Test with an enquiry clearly marked as a test. Find its saved details, the notification and the person expected to reply. Write down any point where staff must guess or search another system.
For example, an urgent maintenance request and a new website brief may arrive through the same form but require different owners. A service choice can route them appropriately. Keep the initial questions focused on what the first responder needs. W3C recommends clear instructions for required fields and expected formats.
Choose one place for the working status
Your existing CRM or a small dashboard can hold the current state. Agree a stable enquiry reference that the form, notification and replies can share. The aim is to make the request traceable when an email is forwarded or another colleague takes over.
Sketch one useful record: reference, received time, service, owner, status, next action and due time. Add fields only when someone will use and maintain them. Decide when a new message updates an existing request and when it represents a separate enquiry; matching a name alone may not express that distinction.
Define what happens while the request waits
Give the unassigned queue a named reviewer and agree who covers an absence. Set response expectations around the team's actual working hours. If a request needs a specialist, record the transfer so the original owner can see whether someone has picked it up.
Make statuses explain the work. 'Awaiting customer brief' should identify the missing information and a follow-up date. 'In progress' should have an owner and a next action. Review the oldest unresolved requests and ask what must happen for each to move forward.
Test the failure path before trusting automation
In a test environment, submit a request while the CRM connection is unavailable. Confirm where the enquiry remains stored and how a responsible person learns about the failed handoff. Restore the connection and check that retrying produces the intended record without duplication.
Repeat the relevant checks after a form, email setting or integration changes. Keep a short record of the request reference, expected owner, observed result and unresolved problem. A useful acceptance test is whether the next person can continue the customer's conversation from the saved information.
Your next step
A practical checklist
- A test enquiry is saved and can be found by its reference.
- The receiving person can identify the requested service.
- One system holds the current status.
- Unassigned requests and absences have a responsible owner.
- A failed integration is visible and can be retried safely.
- The oldest open requests have a specific next action.