How to Establish a Reliable Enquiry Management Process

Introduction: Receiving an enquiry is not the same as managing it

When a business publishes a contact form, displays an email address or invites prospective customers to request a quotation, it creates an expectation: someone will receive the enquiry, understand what is needed and respond appropriately.

Yet receiving an enquiry and managing it reliably are two different things.

An enquiry may arrive successfully without reaching the person responsible for handling it. An employee may respond without recording the interaction. A quotation may be sent without a follow-up being scheduled. Another employee may contact the same prospect without knowing that a conversation has already taken place.

Individually, these situations can appear to be small administrative mistakes. Collectively, they reveal a more fundamental weakness: the business lacks a dependable mechanism for moving an enquiry from arrival to a defined outcome.

The distinction matters because an enquiry-management process must work under ordinary operating conditions, not only when the business owner is personally monitoring every message.

The real question is not whether a business has a contact form, shared inbox or customer relationship management (CRM) system. It is whether the business can consistently establish what happened to every enquiry, who is responsible for it and what needs to happen next.

Reliable enquiry management is therefore not simply a matter of choosing software. It is a matter of designing, implementing and maintaining a process that people can follow consistently.

1. What does the evidence tell us?

Research into online sales enquiries has examined the gap between generating potential customers and responding to them effectively.

In March 2011, James B. Oldroyd, Kristina McElheran and David Elkington published The Short Life of Online Sales Leads in Harvard Business Review.

Their research reported that 23% of the companies studied never responded to an online sales enquiry. Among companies that responded within 30 days, the average response time was 42 hours.

These findings are historical, not a measurement of present-day business performance. They should not be used to suggest that the same proportions apply today. Nevertheless, the study illustrates a fundamental operational distinction: making an enquiry possible does not guarantee that an organisation will handle it consistently.

More recent evidence offers another perspective.

In March 2026, Workato published B2B Lead Response Times: What We Learned from 114 Companies. Its researchers submitted demo requests to 114 B2B companies and examined how those companies responded.

The report found that only one company sent a personalised email within five minutes. The average time to receive a personalised email response was 11 hours and 54 minutes. Nearly one in five companies did not respond by email at all.

The phone results revealed another gap: only 31% of the companies responded by phone, and the average response time among those that did was 14 hours and 29 minutes.

These results provide a recent, directly observed example of response delays. However, the scope and methodology matter. The study examined demo requests submitted to a particular sample of B2B companies, not all businesses, industries or enquiry types. Workato also sells automation software, so its findings should be understood as vendor-produced research rather than an independent, representative industry survey.

Taken together, these studies provide a useful starting point. Businesses can invest in attracting potential customers while still experiencing weaknesses in the process that should turn an incoming enquiry into a meaningful conversation.

The evidence does not establish that every business needs the same response target or software. It raises a more practical question:

What must a business put in place to ensure that incoming enquiries are captured, assigned and progressed consistently?

Answering that question requires examining the process itself.

2. Why ordinary ways of working become unreliable

Many businesses begin with a straightforward arrangement. Enquiries arrive by email, telephone, website form or direct message. The owner or an available employee handles them as they appear.

This can work when volumes are low and one person has visibility over almost every conversation. The weaknesses become more apparent when enquiries arrive through several channels, responsibilities are shared or employees are unavailable.

Four recurring failure mechanisms deserve particular attention.

Enquiries arrive, but responsibility remains unclear

A shared inbox can make messages visible to several employees without establishing who must act on each one.

One employee may assume a colleague has replied. Another may believe the enquiry belongs to a different department. Both may see the message, yet nobody takes responsibility for progressing it.

Visibility is not ownership.

A reliable process should identify one accountable owner for each active enquiry. Other employees may contribute, provide expertise or take over, but responsibility should be explicit rather than inferred from who happens to be available.

The process should also define what happens when an enquiry cannot be handled by its initial owner. Without a clear reassignment or escalation rule, an apparently assigned enquiry can become inactive without anyone noticing.

Responses happen, but the record is incomplete

An employee might reply directly from an email account, make a telephone call or exchange messages through another channel. If that interaction is not recorded in the agreed system, the business may have no dependable overview of what has already happened.

The next employee must reconstruct the history from individual inboxes or ask colleagues for updates.

This creates unnecessary work and makes continuity dependent on access to the right people and conversations.

The solution is not necessarily to record every possible detail. It is to establish a minimum useful record: the enquiry, its source, its owner, its current status, the latest meaningful interaction and the next action.

Follow-ups depend on memory

A prospect receives a quotation and says they will consider it. The employee intends to check back in a few days, but another priority intervenes.

Without a recorded next action and due date, the intention can disappear from view.

This is different from forgetting to send the original response. The enquiry was received, acknowledged and progressed, yet the process failed at the point where continued attention was required.

A reliable workflow makes the next action visible and gives the responsible person a practical way to identify overdue work.

It should also distinguish between a follow-up that is due, one that has been completed and one that has been rescheduled. Otherwise, a task can remain apparently active without anyone knowing whether it still requires attention.

The system becomes an additional administrative burden

CRM software can improve visibility, but implementation alone does not guarantee reliable behaviour.

In a discussion among CRM practitioners about whether low adoption is a user or system-design problem, participants discuss issues such as excessive fields, misaligned processes and systems that do not provide enough value to their users.

Such discussions help illustrate practical frustrations, but they are anecdotal and cannot establish how prevalent these problems are across businesses.

When maintaining the system feels disconnected from doing the actual work, employees may create informal alternatives: private spreadsheets, personal reminders, separate notes or conversations that never reach the shared record.

The organisation then has multiple versions of the truth.

The underlying issue may not be a lack of features. It may be that the process is too complicated, poorly defined or insufficiently integrated into everyday work.

A system should support the work employees need to perform, not require them to maintain a parallel administrative process that provides little practical value.

3. Define reliability before selecting the tools

A useful starting point is to describe what must be true of every enquiry, regardless of the software used.

At a minimum, a reliable process should make it possible to establish:

Capture: Has the enquiry entered the agreed tracking system?
Ownership: Who is accountable for the next action?
Status: What stage has the enquiry reached?
Response: Has the appropriate initial response been sent?
Continuity: Is the relevant communication history accessible to authorised colleagues?
Next action: What must happen next, and by when?
Outcome: Was the enquiry converted, declined, lost, withdrawn or otherwise concluded?

These are operational requirements rather than a prescribed software configuration.

A small business might manage them in a carefully controlled spreadsheet. A larger team may need a CRM, automated routing, integrated communications and reporting. A business receiving enquiries through several channels may need a way to bring those enquiries into one consistent tracking process.

The appropriate tools depend on the business. The underlying requirements do not disappear when the business changes tools.

A useful test is whether another authorised employee could open an enquiry record and understand its current situation without reconstructing the history from separate conversations.

If the answer is no, the process may still depend too heavily on individual memory.

Reliability also requires distinguishing between the existence of a record and the existence of an actionable record. A contact name and email address may prove that information was collected, but they do not necessarily reveal who is handling the enquiry or what should happen next.

The goal is not to collect the maximum amount of information. It is to maintain enough accurate, accessible information to support the next appropriate action.

4. Establish clear rules for each stage

A process becomes more reliable when employees share the same understanding of what each stage means.

Consider a simple enquiry-to-outcome workflow:

Received → Assigned → Contacted → In progress → Follow-up due → Won, lost or closed

This is an illustrative model, not a universal pipeline. Some businesses will need fewer stages; others will require qualification, appointments, quotations, approvals or additional handovers.

The important point is that each stage should represent a recognisable condition.

For example, does “contacted” mean an employee attempted to make contact, or that the prospect actually received a response? Does “in progress” mean someone is actively working on the enquiry, or merely that nobody has closed it?

If employees interpret the same status differently, reports become unreliable and managers cannot confidently distinguish active opportunities from neglected ones.

For each stage, define three things:

Entry condition: What must have happened before an enquiry can enter this stage?
Required action: What responsibility or activity applies while the enquiry is in this stage?
Exit condition: What must happen before the enquiry can move to the next stage?

Next, establish the rules that prevent enquiries from remaining indefinitely in an ambiguous state.

An open enquiry should have a responsible owner and a clear next action. Where a next action cannot yet be scheduled, the reason should be recorded and the record reviewed according to an agreed rule.

Closure also needs a definition. An enquiry should not disappear simply because it has become inconvenient to pursue. The record should indicate what happened, where appropriate, and whether further action is required.

These rules make the workflow understandable to employees and testable by managers. They also make it easier to identify where a process has failed, rather than relying on vague descriptions such as “the team needs to follow up better.”

5. Set response and follow-up standards that fit the business

There is no single response-time target that is appropriate for every type of enquiry.

A request for emergency assistance, a routine quotation request and a complex business-to-business enquiry have different expectations and operational requirements.

Instead of adopting a generic target without context, businesses should define response standards based on customer expectations, service commitments, working hours, staffing and the nature of the enquiry.

The standard should distinguish between acknowledgement and substantive response.

An automated acknowledgement can confirm receipt, but it does not necessarily answer a question or resolve a customer's immediate concern. A business should be clear about what its response target measures and should not count an automated message as a meaningful response unless that is explicitly appropriate for the service being offered.

The process should also specify what happens when the normal response target cannot be met. Depending on the business, this might involve reassignment, escalation or a clear communication about when the customer can expect an answer.

Follow-up standards require similar clarity.

A quotation sent to a prospect may need a different follow-up sequence from a service request awaiting additional information. The business should determine when follow-up is appropriate, how it is recorded and what happens if the prospect does not respond.

The aim is not to contact every prospect repeatedly regardless of circumstances. It is to ensure that planned actions are deliberate, timely and consistent with the relationship.

Standards must also be realistic. A target that cannot be achieved with available staffing, working hours or enquiry volumes will encourage workarounds and make reporting less useful.

Once a standard is introduced, actual performance should be reviewed. If the team repeatedly misses the target, management should investigate whether the cause is workload, routing, unclear responsibilities, inadequate tools or an unrealistic expectation.

A response-time target is valuable only when it leads to better operational decisions.

6. Make the process easy enough to use consistently

A process that is theoretically comprehensive but impractical during a busy working day is unlikely to remain reliable.

This is why simplicity should be treated as an operational requirement.

Start with the information needed to move an enquiry forward. Avoid requiring employees to complete fields that do not support a real decision, action, reporting need or compliance obligation.

Use standard statuses and agreed definitions rather than allowing everyone to invent their own terminology. Make ownership visible. Provide a simple way to identify overdue actions and enquiries without a recorded next step.

Where possible, reduce repetitive manual work through integrations and automation. A website form might create a record automatically, assign an owner and trigger an acknowledgement. A follow-up reminder might be generated when a quotation is sent.

However, automation should support a defined process rather than conceal an undefined one.

If nobody has decided who should own a particular enquiry, automated assignment may simply distribute confusion more quickly. If the business has not agreed what constitutes a completed response, an automated notification cannot reliably determine whether the customer has actually been helped.

Automation can also introduce new failure points. A form integration may stop working, an assignment rule may direct enquiries to the wrong person or a notification may fail to reach its intended recipient.

Consequently, automated steps need to be tested and monitored. The business should know how it will detect failures and how enquiries will be handled when the normal workflow is unavailable.

The process should be understood first, configured second and tested before it becomes dependent on automation.

7. Test the workflow instead of assuming it works

One of the most useful ways to assess enquiry management is to test it with controlled scenarios.

Consider a fictional business that receives an enquiry through its website.

The form is submitted successfully. An acknowledgement appears. A contact record is created. The enquiry is assigned to an employee.

At first glance, the workflow appears successful.

Now test what happens when the assigned employee is unavailable. Does another person know the enquiry needs attention? Is reassignment possible? Does the record preserve the relevant communication history?

Next, simulate a quotation being sent. Is a follow-up action created? Can the responsible employee see when it is due? Can a manager identify that the action has become overdue?

Finally, submit the same fictional enquiry twice. Does the process create duplicate records, recognise the existing contact or provide a way to reconcile the two entries?

These tests reveal weaknesses that a successful form submission alone cannot expose.

A useful test set should include:

A normal enquiry arriving through each supported channel.
An enquiry received outside working hours.
An enquiry that remains unassigned.
An enquiry whose owner becomes unavailable.
A quotation requiring follow-up.
An enquiry that receives no response from the prospect.
A duplicate submission or an existing contact making a new enquiry.
An enquiry that must be closed with a documented outcome.
An integration or notification failure, where relevant.

For each test, record the expected behaviour, the actual result and any manual intervention required.

If an enquiry is supposed to be assigned automatically, verify that assignment occurs. If a follow-up is supposed to generate a reminder, check that the reminder appears and reaches the intended person. If duplicate handling is part of the design, test the conditions under which the system recognises an existing record.

A demonstration should be described accurately. A controlled test can establish that a particular workflow behaves as configured under specified conditions. It cannot, by itself, prove that a business has improved its conversion rate, eliminated missed enquiries or achieved consistent performance across an entire organisation.

Those outcomes require evidence from actual usage over time.

The distinction is important: testing verifies whether the process behaves as expected, while ongoing measurement determines whether it remains effective in daily operations.

8. Measure whether the process remains reliable

Once the workflow is operational, the business needs a way to determine whether it is being followed.

Useful measures include:

Enquiry capture rate

What proportion of enquiries received through supported channels appear in the tracking system?

This requires a trustworthy count of incoming enquiries against which records can be reconciled. Without that comparison, a business may know how many enquiries it has recorded but not how many it has missed.

Time to first response

How long does it take to respond after an enquiry arrives?

Define which events count as a response and report typical performance alongside significant delays. Where relevant, distinguish automated acknowledgements from meaningful responses.

Unassigned enquiries

How many enquiries remain without an accountable owner, and for how long?

This measure helps identify failures in assignment rules, routing or the handover between teams.

Overdue follow-ups

How many open enquiries have passed their next-action date without the action being completed or rescheduled?

The figure becomes more useful when examined alongside the age of overdue tasks and the reasons they remain unresolved.

Record completeness

How many active enquiries have the required owner, status and next action?

Completeness should be measured against the fields that are genuinely necessary. A record filled with unnecessary information is not automatically a reliable record.

Documented outcomes

How many enquiries have a recorded result, and how many remain unresolved or have disappeared from active tracking?

A clear outcome makes it possible to distinguish a concluded enquiry from one that has simply stopped progressing.

These measures should be interpreted together.

A business might improve its initial response time while allowing follow-ups to accumulate. Another might show excellent record completeness because employees update fields mechanically, while customers still wait for meaningful responses.

No single metric demonstrates reliability.

The purpose of measurement is to identify where the process breaks down, investigate why and determine whether corrective action has worked.

For smaller businesses, this does not necessarily require a sophisticated reporting platform. A periodic review of incoming enquiries, open records, overdue tasks and documented outcomes may provide a useful starting point, provided the underlying information is sufficiently accurate.

9. Treat reliability as an ongoing operating discipline

Enquiry management does not become permanently reliable on the day a workflow is launched.

New communication channels appear. Team responsibilities change. Enquiry volumes fluctuate. Employees develop workarounds. Integrations fail, and previously sensible rules become unsuitable as the business grows.

A reliable process therefore needs periodic review.

Managers should examine overdue enquiries, unassigned records, duplicate contacts, missing next actions and unexplained differences between incoming messages and tracked records. Exceptions should lead to investigation rather than simply being counted.

If enquiries repeatedly remain unassigned, the answer may be clearer ownership rules or better routing.

If employees maintain private spreadsheets, the official workflow may be too difficult to use or may not provide the information they need.

If follow-ups are regularly overdue, the business may have unrealistic workloads, inadequate reminders or unclear expectations.

If duplicate records repeatedly appear, the issue may involve form design, contact-matching rules or the way employees enter new information.

The goal is not to blame employees for every process failure. It is to understand whether the workflow, responsibilities, tools and working conditions make the expected behaviour achievable.

A practical review should ask three questions:

Where did the process fail to behave as expected?
What underlying condition caused the failure?
What change would prevent or detect the same problem in the future?

This approach moves improvement beyond reminders to “be more careful.” It allows the business to address the conditions that make mistakes likely and verify whether changes improve performance.

Conclusion: Reliability is designed, tested and maintained

An enquiry-management process is reliable when the business can account for incoming enquiries, identify who is responsible for them, understand their current status and determine what should happen next.

Achieving that requires more than a contact form, a shared inbox or a CRM subscription. It requires clear definitions, practical ownership rules, consistent records, appropriate response standards and a way to identify exceptions before they become forgotten opportunities.

The process should be simple enough to use, structured enough to provide accountability and flexible enough to accommodate the realities of daily work.

Most importantly, its effectiveness should be demonstrated rather than assumed.

A business does not need to begin with an elaborate system. It needs a dependable process that works under ordinary conditions, exposes its own failures and can be improved as the business develops.

The starting question is straightforward:

If a new enquiry arrived right now, could the business establish who owns it, what has happened so far and what must happen next — without relying on someone remembering?

If not, the first improvement may not be a new tool. It may be defining the process the tool is supposed to support.

Research and further reading

1. Historical research into online sales enquiries

Oldroyd, J. B., McElheran, K., & Elkington, D. (2011). The Short Life of Online Sales Leads. Harvard Business Review. Read the original article.

This study provides historical evidence of delays and non-response in online sales enquiries. Its statistics should not be interpreted as current industry-wide benchmarks.

2. Recent observational research into B2B response times

Kuppahally, A. (19 March 2026). B2B Lead Response Times: What We Learned from 114 Companies. Workato Read the original study and methodology.

Workato documents its test of demo-request responses across 114 B2B companies. Because Workato sells automation software and the study has a limited sample, its results should be interpreted as vendor-produced observational evidence, not as a representative survey of all businesses.

3. Practitioner perspectives on CRM adoption

[Is low CRM adoption really a user problem, or a system-design problem?] (https://www.reddit.com/r/CRM/comments/1srebto/is_low_crm_adoption_really_a_user_problem_or_a/)

This discussion explores practical concerns around system usability, process alignment and employee adoption. It provides qualitative perspectives rather than representative research findings.

Why do so many small-business CRM rollouts fail?

This discussion offers further practitioner perspectives on CRM implementation and workflow design. As with any online discussion, individual claims should not be treated as independently verified evidence.

Evidence note: The sources above differ in date, scope and methodology. Historical studies, vendor-produced observational tests and individual practitioner accounts should be distinguished clearly. None establishes a universal response-time target or proves that a particular CRM configuration will improve business outcomes.

All insights