The customer journey between your website and sales team: where enquiries are lost

A visitor submits a form and sees a confirmation. Everything looks correct on the website, but the email never arrives, no one is assigned the enquiry or the sales representative replies in another language. For the customer, this is one unfinished contact; inside the company, it may disappear between several systems.

To find the losses, trace the enquiry from the promise on the page to the next agreed action. The review covers both technology and the team's work.

Choose a specific scenario: a quote request, consultation booking, call or message. Record its sequence:

1. The person understands the offer on the page.
2. They choose a contact method and send the request.
3. They receive confirmation and know what to expect next.
4. The enquiry reaches the working system.
5. A responsible employee receives it.
6. The employee contacts the customer and clarifies the task.
7. Both parties agree on the next step.
8. The outcome and reason for stopping are recorded.

Do not combine every contact method into one diagram. Forms, calls and chats have different technical failure points and handling processes. The sales representative should still recognise when the same enquiry continues in another channel.

Compare the website's promise with what happens after the request. If the button offers an estimate, the customer should understand which information is needed and when a reply will arrive. An automatic “Thank you” message without further expectations leaves uncertainty.

Follow the journey on a phone and in the languages the business uses with customers. Check required fields, input errors, messaging links and submission confirmation.

If the problem occurs before an enquiry, start with the article on website traffic without leads. If submission has already occurred, move on to delivery and handling checks.

Clicking a button, receiving a successful form response, receiving a message and creating a CRM record are separate events. Match them using available identifiers and timestamps. An analytics event does not prove that a sales representative received the enquiry.

For diagnosis, check:

• form and integration errors;
• emails going to spam and access to the inbox;
• creation of the CRM enquiry record;
• preservation of the service, language and contact details;
• assignment of a responsible employee and backup;
• notifications and the queue of unhandled enquiries.

A repeated submission after an error does not always count as a new lead. Find a way to connect duplicates while preserving the history. The tracking basics are covered in the article on connecting advertising with CRM sales.

Record the times of the automatic confirmation, first contact attempt and substantive reply separately. These measures answer different questions. A bot message does not mean a specialist has already taken on the task.

Agree on working hours, the time zone and the promised response time. An overnight request cannot be assessed against the same expectations as one received during working hours unless the company promises round-the-clock support.

Define what happens when the customer does not reply: who follows up, through which permitted channel and when attempts stop. Failure to make contact, rejection and an unsuitable task should have different statuses.

The sales representative needs the offer the customer saw, the selected service, language, information already supplied and promised conditions. When this context is lost, the customer repeats the question and the company may propose a different scope or timeline.

When handing over to a specialist, assign a new owner and record the next step with a date. “Passed to the department” does not explain who will continue the conversation.

After an estimate or proposal, save what was sent, which question remains and when you agreed to return to the discussion. An automatic reminder does not replace an agreement with the customer.

Suppose 30 successful form submissions are recorded during one period and 28 have a corresponding CRM record. After checking duplicates, the team confirms that two distinct enquiries failed to arrive because of an integration error.

Of the 28 received enquiries, five were not assigned to an employee within the promised time. There are two separate problems here: technical delivery and work assignment. They need different fixes.

Before this reconciliation, differences between reports cannot be counted as lost sales. Some discrepancies may arise from duplicates, spam, tracking methods or an incomplete reporting period. Qualification and the later outcome need a separate review.

1. The page makes the offer and next step clear.
2. All contact methods work on a phone and in the required languages.
3. Confirmation describes the actual response process.
4. The enquiry is saved in the working system with the necessary data.
5. There is an owner, backup and oversight of unfinished enquiries.
6. Response time is tracked under agreed rules.
7. Employee handover preserves context and agreements.
8. The next step, outcome and reason for stopping are recorded.

Start with actual enquiries and a few control scenarios, including an error, contact outside working hours and a transition between channels. For each issue, assign a fix, an owner and a way to check it again.

To align the offer, channels and stages of working with the customer, discuss the task through our market research and strategy service. Prepare the journey map, anonymised enquiry examples and team procedures; technical changes and integrations require a separate estimate.