Your website gets enquiries. Why aren’t they becoming sales conversations?
Someone has taken the time to explain a project and ask whether you can help. If their message sits in a shared inbox, reaches the wrong colleague or loses its details on the way to your CRM, they may be left waiting while your team assumes someone else has replied.
You can end up paying for more traffic while an enquiry you already earned goes unanswered. The prospective customer may try another supplier, and your team may spend time recovering details instead of answering the request.
Follow one recent enquiry from Send to a useful human answer. Include the website, marketing tools, CRM and shared inbox wherever they take part. These may be separate tools or parts of one platform. Check the request, its history, its owner and the reply, then make unanswered work visible.
Check what arrived after Send
Compare the original submission with what reached the CRM and the person expected to respond. Use only records your team is authorised to access.
Can you see what the person asked, when it arrived and which form or channel they used? Is the full message available, or has the notification reduced it to a name and email address?
Check the difference between the website accepting the request and the CRM receiving it. A thank-you page can appear before a later integration finishes. Someone needs to be able to confirm whether that next step succeeded.
If delivery fails, decide where the request waits, who sees the failure and how to recover it. Keep enough information for recovery without copying personal details into unnecessary logs. The website should report success only after the request has been safely accepted for handling.
Keep the request and its history together
For example, an existing customer asks about a new project. The person is already in your CRM, but this request needs its own next action.
Replacing their previous message can hide useful history. Creating another contact every time they submit a form can leave colleagues working from different records.
Keep each genuine request with its message, time, source and status, attached to the appropriate contact where you can match reliably. Your current CRM may support this through an activity, ticket or another suitable record type. You do not need to turn every enquiry into a sales opportunity immediately.
Distinguish a retry of the same submission from a genuinely new request. A stable submission reference can help prevent repeated delivery from creating repeated work. Do not merge people just because they share a company, name or general inbox.
Make the reply someone’s responsibility
A small team may need only a shared queue, a named owner and a visible next action. Agree who covers when the owner is away and who checks requests that remain unassigned.
Set a response target that fits your service and working hours. If the website promises a response time, make sure the team can meet it. A technical quote may first need a human reply that confirms the request and asks one necessary question.
Keep the routing rules simple:
- Existing customer: check who already manages the relationship
- Clear new enquiry: assign someone who can take it forward
- Unclear request: give someone responsibility for asking the missing question
- Unassigned or overdue: show it to the person responsible for the queue
An alert needs someone to act on it. Test the absence cover and the overdue route as well as the normal assignment.
From a submitted request to a useful response
- 01SubmittedWhat the person asked
- 02ReceivedSafely accepted and recorded
- 03MatchedAppropriate contact and request history
- 04AssignedOwner, useful context and next action
- 05Human replyRelevant response recorded
- 06OutcomeConversation, later action or reason closed
When a step fails Missing information or failed delivery needs visible review or a safe retry, with a named person responsible.
Marketing choice stays separate Record the optional choice and check campaign eligibility. An unchecked box does not block handling the enquiry.
Each checkpoint answers a different question. A thank-you page or automated acknowledgement does not show that a person has replied.
Give the owner enough context to answer
Useful context for the person replying
- Source
- Where the request came from, with its date
- Question
- What the person actually asked
- Relevant history
- Useful interactions and what remains unknown
- Next action
- Who will reply and what they need to do
Keep stated needs and observed behaviour distinct from assumptions about intent.
The owner should see the original question, relevant history and any reply already sent. Bring over useful marketing context too: the offer they responded to, what information they asked for and any need or timing they stated. Keep the source and date available. If the person also emailed, bring that conversation into view before another colleague answers.
Prioritise using what the person actually supplied: their problem, stated deadline and requested next step. A vague message may need clarification. A job title or page visit does not establish budget or readiness to buy.
Try the handoff with a sales rep. Can they understand the request, find the relevant details and take the next step without searching several tools or entering the same information again? Ask what helps and what creates extra work. Useful context, less copying and clear next actions give reps a reason to use the CRM as part of selling. Management visibility should come from a workflow that helps them do that work.
For the existing customer asking about a new project, a useful reply might confirm the service they need and ask for the detail required to assess fit. Avoid making them repeat information already in the request.
Some people need an answer or more time before a sales conversation makes sense. Record that next step. Where appropriate and permitted, marketing can provide relevant information while sales keeps the agreed follow-up visible.
Automation can route the enquiry, create a task and flag overdue work. Keep the sales conversation in human hands. Define when automated reminders should pause or stop after a reply, handover or closure, so they do not collide with an active conversation.
Before you switch on the workflow
Use test records to check:
- A new person and an existing customer making a new request
- The same submission arriving twice, including a retry after failure
- One person using both email and the form
- An unavailable CRM, absent owner or overdue reply
- Useful marketing context arriving late or missing from the rep’s view
- An enquiry with the optional marketing box unchecked
- A human reply that should stop a pending reminder
For each test, inspect the saved request, assignment and customer-facing result. Know who will handle exceptions and how the team can continue manually if the connection is unavailable.
Review the work still waiting
Keep a short view of unassigned enquiries, requests awaiting a first human reply and conversations with an agreed next action. Check it at a rhythm the team can sustain.
Separate an automated acknowledgement from a useful human response. Keep unanswered requests visible when reviewing response times, and define how working hours are counted.
Record a simple outcome: conversation started, information requested, unsuitable, no current need or closed without a response. Identify tests, spam and support requests separately. This helps you see whether the problem is follow-up, fit or something else.
Start with one dependable route
Choose one enquiry source and repair its first unclear handoff. Your existing website, marketing tools, CRM and shared inbox may already have what you need. A setup can have limitations and still do this job reliably. Add or replace something only when a specific gap justifies the effort and ongoing cost.
ExactWork can help check the setup, connect the missing pieces and test the path to a useful human response.
If you’re weighing a larger change, compare keeping, repairing, extending or replacing your marketing and CRM tools using the decision worksheet.
If the gap starts before the enquiry, read the guide to bringing suitable visitors to your website. For incomplete forms and reminder stopping rules, see the B2B note in the cart automation guide.
Tell me what’s stuck.
Where does follow-up become unclear: saving the enquiry, assigning it or knowing whether someone replied? Tell me what happens today and which tools you use.