How should a business handle enquiries across several channels?

Channels accumulate. A web form, a main phone line, a mobile that customers learned, a business messaging profile, a social account someone set up for a campaign, a review platform with a message function, a chat widget added during a website refresh. Each was added deliberately and each arrived with its own inbox. Nobody ever decided to run seven inboxes, and yet that is what the business now does.

The failure mode is specific and it is not that customers are confused. It is that each inbox is monitored by whoever set it up, at the frequency they happen to check it, until they get busy or leave. There is no moment where monitoring formally stops, so nobody notices when it does. The channel keeps being published, keeps receiving enquiries, and quietly stops producing any. From outside it looks exactly like a working channel.

The correct response is almost never to reduce the number of channels, because the channels are where customers are and removing one removes the customers who prefer it. It is to reduce the number of destinations. Every channel routes into one place — a shared inbox, a help desk, a single messaging platform — where every enquiry is visible to more than one person, carries a timestamp and has an owner. What matters is not which product does this but that a single answer exists to the question of where an enquiry goes.

Ownership has to be a name rather than a team, and this is where the design usually fails. An enquiry belonging to everybody belongs to nobody, and the shared inbox becomes a place where four people each assume someone else has replied. Assignment can rotate, it can be by channel, it can be by time of day, but at any given moment one person is responsible for a given enquiry and knows it.

The response deadline belongs to the destination rather than to the channel, and it should be a single number. Businesses that set different targets per channel end up with a hierarchy in which the fast channel is watched and the slow one becomes the new unmonitored inbox. A customer who chose to message rather than call has not agreed to wait longer, and treating the choice as a signal of patience is how a channel dies.

One property of consolidation is worth wanting for its own sake beyond the operational tidiness: it produces a single arrival log across every channel. That log is what makes response time measurable, what makes an unmonitored channel visible the moment it stops producing, and what any future automation will need in order to know what arrived. Consolidation is worth doing even if nothing else changes, because it is the thing everything else depends on.