When Everyone Is Involved, but Nobody Owns the Enquiry

How unclear responsibility, departmental handoffs and disconnected systems create gaps in enquiry management — and how established businesses can regain control.

An enquiry arrives through the company website. Sales reviews it and asks the technical department for additional information. The technical team has other priorities, so the request waits. Meanwhile, the customer follows up with the sales representative, who assumes the internal request is already being handled.

Several employees are involved. The enquiry has been seen, discussed and passed between people.

But the customer is still waiting.

No one necessarily decided to ignore the enquiry. Each department may have completed its own part of the work. Yet the overall process has failed to move the customer's request forward.

This is an operational problem that can emerge as businesses grow: responsibility becomes harder to maintain when work crosses teams, departments and systems.

The problem is not always a lack of effort, communication or technology. It can be a gap between individual tasks and accountability for the complete customer journey.

The difference between handling a task and owning an enquiry

In a smaller business, the owner may see most incoming messages and personally decide what happens next. As the business grows, that arrangement becomes difficult to maintain.

Sales representatives qualify enquiries. Technical teams provide specifications. Operations confirms capacity. Finance checks commercial terms. Managers approve exceptions. Customer service handles subsequent questions.

Dividing the work is often necessary. Specialist teams allow businesses to handle more complex requests and serve more customers.

The difficulty begins when the work is divided but responsibility for the overall outcome is not clearly maintained.

One employee may be responsible for preparing information. Another may need to approve it. A third may be expected to communicate with the customer.

Every individual task can have an owner while the enquiry as a whole remains unmanaged.

The critical question is not whether every department has a role. It is whether someone is accountable for ensuring that the enquiry progresses from beginning to end.

What recent research tells us about fragmented business processes

The problem of coordinating information across systems is documented in recent business research, although it is important not to confuse that problem with a measured rate of missed enquiries.

The UK Department for Science, Innovation and Technology commissioned Ipsos to conduct the second wave of its Business Data Use and Productivity Study. Its quantitative survey collected responses from 3,796 UK businesses during December 2024–February 2025. The accompanying qualitative research involved 40 businesses across different sizes and sectors.

The qualitative report describes businesses dealing with inconsistent records, manual data entry, outdated systems and software that does not integrate properly. One larger business described using numerous departmental systems that did not all communicate with one another. A smaller business described having to duplicate information because its marketing database did not integrate with its CRM.

These interviews are illustrative rather than representative: they identify real operational challenges but do not establish how frequently those challenges occur across all businesses.

Sources: UK government statistical report, technical report and qualitative research report, updated 28 January 2026.

Software adoption also varies considerably by business size. According to Eurostat, 24.69% of EU small enterprises used CRM applications in 2025, compared with 65.43% of large enterprises. The figures cover enterprises with at least 10 employees or self-employed persons in the specified economic sectors. Small enterprises have 10–49 employees, while large enterprises have 250 or more.

Source: Eurostat — Larger enterprises used more e-business apps in 2025, published 20 May 2026.

This does not mean that businesses without a CRM necessarily have poor processes, or that businesses with one manage enquiries well. It shows that dedicated customer-management software is not used equally across enterprise sizes.

A further perspective comes from Salesforce's seventh State of Service report, based on a double-anonymous survey of 6,500 service professionals across 40 countries, conducted from April to June 2025. Among service leaders whose organisations used AI, 44% said technology silos had delayed or limited their AI initiatives.

This finding concerns AI implementation, not enquiry ownership. It nevertheless illustrates a related challenge: separate systems can make it harder to coordinate work that depends on shared information.

Source: Salesforce — State of Service, Seventh Edition.

Together, these sources provide context for the problem. They do not establish a universal percentage of enquiries lost through poor handoffs. That question needs to be investigated using evidence from the business itself.

Five places where enquiry ownership can break down

1. The shared inbox creates visibility without accountability

A shared sales inbox gives a team access to incoming enquiries. Team members can read messages, respond to customers and cover for colleagues.

But visibility is not the same as ownership.

When several people can respond, employees may assume someone else has already taken responsibility. Alternatively, two people may reply independently because neither can see that the other has taken the enquiry.

The risk is greater when the team has no explicit assignment process, no consistent status conventions or no agreed way to handle unassigned messages.

The solution is not necessarily to abandon the shared inbox. It is to establish how an enquiry becomes someone's responsibility, how that assignment is recorded and how unassigned or overdue enquiries are identified.

2. The handoff happens, but acceptance is never confirmed

Consider a sales representative who needs technical information before preparing a quotation.

The representative sends a request to the technical department. From their perspective, the task has been passed on.

The technical department receives the request but cannot complete it immediately. The request remains in an email thread, a queue or an individual's task list.

Sales assumes the information is being prepared. Technical staff have not necessarily agreed that the request can be completed within the expected timeframe.

The handoff has occurred, but the next step has not been secured.

A dependable handoff should establish:

● What information, decision or action is required.
● Who is responsible for completing it.
● When it is due.
● How completion will be recorded or communicated.
● What happens if the task cannot be completed on time.

Where the request is urgent or commercially important, the receiving person or team should acknowledge responsibility.

Without these controls, work can disappear from one person's attention before entering another person's priorities.

3. Departmental priorities do not automatically align

Sales may prioritise customer response times. Technical staff may prioritise accuracy and feasibility. Operations may prioritise existing commitments. Finance may need to verify commercial terms before a proposal can be approved.

These priorities can all be legitimate.

The difficulty arises when no shared process establishes how competing priorities are resolved for a particular enquiry.

A request may be important to sales without appearing urgent to another department. If there is no agreed service expectation or escalation route, the delay may continue until the customer asks again.

This is not necessarily an individual performance problem. It can result from managing departments separately without maintaining oversight of the complete customer process.

The business needs to distinguish between the person responsible for completing a task and the person accountable for ensuring that the customer's enquiry continues to progress.

4. The CRM shows activity, but not the complete situation

An established business may already have a CRM, shared inboxes, a project-management tool and departmental spreadsheets.

The existence of these systems does not guarantee a consistent view of an enquiry.

Sales may record that a quotation is being prepared. Technical staff may track their work elsewhere. Operations may communicate a delivery constraint through email. Finance may maintain approval information in another system.

Each record may be accurate within its own context, yet the business may struggle to establish the current overall status without consulting several sources.

The issue is not simply that information exists in different places. Different systems can serve legitimate purposes.

The issue is whether the people responsible for progressing an enquiry can obtain the information they need, understand its current status and identify the next action without excessive manual reconstruction.

A CRM should support that process. It should not become another location where employees duplicate information without a clear operational benefit.

5. Responsibility disappears when an employee is absent or changes roles

An enquiry may depend on an employee who knows the customer, understands the technical details or remembers an informal commitment.

When that employee is absent, changes role or leaves the company, the business may discover that essential context was never recorded.

The problem can extend beyond access to the original email. The company may not know what was promised, what remains outstanding, which colleague was consulted or when the customer expected an answer.

This exposes the difference between a process that works because an experienced individual remembers everything and a process that remains reliable when people change.

A robust system records the relevant context, the current owner and the next action so that responsibility can transfer without requiring the entire situation to be reconstructed.

A practical demonstration: trace one enquiry across departments

Consider a fictional company supplying equipment to commercial customers.

A prospective customer requests a quotation for 40 units, including installation and delivery within a specified timeframe.

The enquiry follows this path:

Sales → Technical → Operations → Finance → Sales → Customer

Each department has a defined contribution. But who ensures that the complete sequence finishes on time?

If the answer is unclear, trace the enquiry through every handoff.

For each stage, establish five things:

Control	Question to answer
Input	What information or decision is required?
Owner	Who is responsible for the next action?
Deadline	When must it be completed?
Completion signal	How does the next person know the task is finished?
Escalation	What happens if the deadline is missed or the task cannot proceed?

For example, a technical request might require a configuration decision by Wednesday. The technical owner records the decision in the agreed system and updates the enquiry status.

If the decision cannot be made on time, the delay is flagged to the person accountable for the customer-facing enquiry. Sales can then communicate an accurate expectation to the customer rather than waiting indefinitely or making an unsupported promise.

The purpose is not to introduce unnecessary approvals. It is to make each transition dependable.

The control that matters most: one accountable owner for the whole enquiry

A useful distinction is between task ownership and enquiry ownership.

Task ownership concerns a specific action: preparing a specification, checking stock, approving a discount or confirming delivery.

Enquiry ownership concerns the overall progress of the customer's request.

These roles can belong to different people.

For example, a sales representative may remain accountable for progressing the enquiry while the technical department owns a configuration task. The sales representative does not need to perform the technical work, but should be able to see whether it has been completed and what happens if it is delayed.

This avoids two extremes.

The first is expecting one person to perform every task, even when specialist input is required.

The second is dividing the work between departments and assuming the customer journey will manage itself.

A clear model preserves specialist responsibilities while ensuring that one accountable person or explicitly designated role maintains oversight of the complete enquiry.

Where ownership genuinely changes, the transfer should be recorded and accepted rather than assumed.

How to diagnose ownership gaps in an established business

A business does not need to redesign every department to understand where enquiries stall. Start with a sample of recent enquiries and examine how each one progressed.

Include enquiries that were completed successfully, delayed, lost or left unresolved. Pay particular attention to those that crossed several departments.

Then investigate five measures.

1. Time between handoffs

Record when a task was passed to another person or department and when the receiving party began or completed the required action.

This helps distinguish time spent performing work from time spent waiting for work to begin.

2. Unassigned and overdue actions

Identify enquiries with no clearly assigned owner, no next action or an overdue commitment.

A record may look active because several employees have commented on it, even when nobody is responsible for moving it forward.

3. Repeated requests for the same information

Look for situations in which employees ask customers or colleagues to provide information that has already been supplied.

This can reveal gaps in record quality, system integration or access to existing information.

4. Reconstructed conversations

Identify cases in which employees must search multiple inboxes, spreadsheets or systems to understand the current status.

The time spent reconstructing the history is an operational cost, even when the customer ultimately receives the correct answer.

5. Enquiries that become inactive without a recorded outcome

Look for enquiries that have stopped progressing but remain open, or have been abandoned without a clear reason being recorded.

This helps establish whether the business can account for its incoming demand and investigate why opportunities do not proceed.

These measures are diagnostic, not universal performance benchmarks. Appropriate targets depend on the business model, enquiry complexity, customer expectations and agreed service commitments.

The first objective is to establish where delays and ownership gaps occur. Once a baseline exists, the business can determine which changes would make the greatest difference.

Build controls around the failures you actually find

The right intervention depends on the problem.

If enquiries remain unassigned: introduce a clear assignment rule and a regular review of unassigned records.

If handoffs are delayed: define what the receiving team must acknowledge, the expected completion time and the escalation route.

If information is fragmented: identify the authoritative record for each important piece of information and determine whether existing systems can exchange it reliably.

If tasks become overdue without anyone noticing: introduce a way to surface overdue actions and assign responsibility for resolving them.

If employees repeatedly reconstruct conversations: improve the recording of relevant decisions, commitments and customer context.

These changes do not all require a new software platform. Some require clearer responsibilities, better operating rules or more consistent use of existing tools.

Technology becomes valuable when it reinforces a defined process: assigning work, recording changes, reminding responsible people, escalating delays and making the current status visible.

The sequence matters. Define the process first, identify which controls are missing, and then decide what should be automated.

What good enquiry ownership looks like

A well-managed enquiry does not require every employee to see every message or every department to use the same software.

It requires a dependable way to establish:

• Who is accountable for the customer's enquiry overall.
• Who owns each outstanding task.
• What information or decision is needed next.
• When the next action is due.
• How a completed task is communicated to the next person.
• What happens when the process stalls.
• Where the current status and final outcome can be found.

When these controls exist, managers can identify where work is waiting, employees can understand their responsibilities and customers are less dependent on internal coordination working perfectly by chance.

The business can also investigate performance using actual process information rather than relying exclusively on individual recollections or departmental reports.

Conclusion: organise accountability around the customer journey

As a business grows, distributing work across teams is both necessary and beneficial. The mistake is assuming that dividing responsibilities automatically creates an effective end-to-end process.

An enquiry can pass through several competent people and still fail to progress because no one maintains oversight of the complete journey.

The answer is not to blame employees, demand constant updates or automatically introduce more software. It is to establish clear accountability, reliable handoffs and visibility of unfinished work.

For an established business, the essential question is no longer simply whether someone has answered the enquiry.

It is whether the business can reliably move that enquiry through every required decision, department and action until its outcome is known.

When everyone contributes, someone must still be accountable for the whole.