پیش‌فاکتور صادر شد؛ حالا مشتری دست چه کسی است؟

One question many industrial companies ask too late is this: after a quote is issued, who exactly has the customer? Not their file—the customer themselves. The person waiting for an answer, planning around it, perhaps holding another purchase, and needing to know whether they can rely on our word.

On the surface, the answer seems simple: the salesperson. In practice, however, after the initial inquiry, the salesperson enters a path where much is no longer under their control. Technical confirmation, credit review, inventory, sourcing, production or cutting, loading schedules, and delivery each have their own owners. The problem begins when every department owns its own task, but nobody owns the relationship with the customer.

In steel sales, and in similar industrial sales, customers do not buy price alone. They are managing their own risk around timing, quality, technical specifications, and cash flow. When they hear that an inquiry is under review or an order has entered production, they are not looking for a polished phrase. They want to know what that status means for their decision, what comes next, and who will remain accountable.

Some companies assume this issue is solved once complete information is logged in a CRM or ERP. Recording information is necessary, but it is not enough. A system can show the status of a credit request or when cutting is scheduled. But the system alone does not tell the customer that the plan changed, why a delay happened, or what choices are now available. Data does not replace ownership.

There is an important difference between the person responsible for doing the work and the person who owns the response to the customer. Credit should review credit. Production should build the production plan. Logistics should coordinate the shipment. Yet, at every point, there must be one person the customer can speak with—without being passed from one extension to another for every answer.

This does not mean the salesperson must do every job or be blamed for every operational failure. That model quickly turns salespeople into a center of burnout and promises they cannot control. It means the relationship owner has both the right and the duty to follow through: see the status, escalate ambiguity, demand a response time, and communicate a material change before the customer has to ask.

I understand this model as stage-based ownership. At every process handoff, both the owner of execution and the owner of customer communication must be clear. Sometimes they are the same person, and often they are not. If you do not put that distinction on paper, the organization runs on people’s memory on normal days and abandons the customer on busy ones.

The first point is the gap between inquiry and technical confirmation. Until product specifications, standards, dimensions, tolerances, intended use, or sourcing feasibility are clear, the customer should not be left waiting behind the vague phrase, “It is under review.” The owner of this stage should know the technical response time, translate open questions into language the customer can understand, and avoid silence if the review takes longer. Silence here signals disorder to the customer, even when the technical team is doing careful work.

The second point comes after technical confirmation and before credit is finalized. This is where one of the most dangerous gaps forms. Sales may think the job is done because the customer accepted the price. Credit may see an incomplete file. The customer may assume the order is already in the execution queue. If the owner of communication through this gap is unclear, the first real news usually comes when the customer discovers a delay—not from the company.

At this stage, we do not need to disclose internal credit details to the customer. But we do need a responsible answer: what is required to proceed, who is reviewing it, when the outcome will be communicated, and which part of our commitment remains unconfirmed until then. Hiding uncertainty behind a confident tone is not professional selling. It merely moves the problem to a worse moment.

The third point is the move from credit to sourcing or production. This is where the quote must become an operating plan rather than remain a commercial document. If inventory is not actually reserved, if the supplier is not yet confirmed, or if cutting or production capacity is unavailable, saying “the order has been registered” can be misleading. The customer has a right to understand the difference between a request being recorded, an order being confirmed, and delivery preparation beginning.

The owner at this stage should provide a reliable picture of the commitment, not the most optimistic scenario. If the delivery date depends on inbound material, supplier confirmation, or released capacity, that dependency should appear in the conversation. Industrial customers usually handle early bad news better than vague good news that collapses at the last moment.

The fourth point is the distance between production or cutting and shipment, where many teams assume that because the goods are being prepared, sales follow-up is no longer needed. The opposite is true. Any change in the plan, quantity shortage, quality-control issue, loading restriction, or shift in shipping time directly affects the customer’s schedule. The response owner should communicate that change before the customer calls, and make the available option or next decision clear alongside the update.

A few signs are enough to tell you that this part is broken. The customer does not know whether to call sales, order processing, the warehouse, or transport. The salesperson learns of a production delay at the same time as the customer. Departments say, “Nobody told us,” yet nobody asks who was supposed to communicate it. Or the customer calls several times for a simple answer and ends up hearing several internal statuses rather than one clear response.

The solution does not start with more meetings. It starts with defining handoff points. For each transition, write one simple sentence: what is being handed over, who receives it, who owns the customer response until the next update, what the maximum response time is, and who must be alerted if the work runs late. These are not administrative details. They are a core part of the customer experience.

For example, a handoff from sales to credit should not be merely a message saying, “Documents were sent.” It should include the agreed commercial status, required documents, urgency of the order, the commitment made to the customer, and the remaining uncertainties. Likewise, a handoff from credit to sourcing or production should not simply say, “Approved.” It should make clear what is firmly reserved, what remains conditional, and what next date can reliably be communicated.

One simple rule helps: customers should not have to learn your organizational chart in order to understand their order status. It is fine for them to know which department does what. But they should not be responsible for finding the owner of an answer. That is the organization’s job. The customer sees one buying journey, not a collection of independent departments and internal terminology.

In practice, you do not need a heavy structure for every order. Even a simple table with five columns can be a good start: stage, execution owner, customer-response owner, promised update time, and exit condition for the stage.

The value of that table is not its appearance. Its value is that, in the middle of a chaotic order when everyone is busy doing their own part, that one small sheet blocks the familiar excuse, “I thought that department was going to inform them.” I see it less as a formal checklist and more as a quiet agreement between departments that no one can slip out of without a real signature.

Then focus on exceptions, not only the normal path. Sourcing delays, credit rejection, specification changes, inventory shortages, quality-control returns, and shipment rescheduling are the moments that reveal real ownership. For each exception, define who communicates the news, who assembles the solution, and who has the authority to revise the earlier promise. If those three people are not clear, the customer will hear the news late, incompletely, and through multiple channels.

In many businesses, the quote is treated as the end of a sales conversation. I see it as the beginning of a more serious test: can the organization carry its promise through different departments without making the customer responsible for coordination too? Good selling is not merely obtaining initial approval. Good selling means that until the product and commitment are delivered, the customer knows who owns the answer and why they can trust that person.

If you are going to make just one change tomorrow, do not touch every process. Select five active orders and trace the actual path of each one from inquiry to shipment. At every pause, ask: who is the customer dealing with right now? If the answer is vague, shared by several people, or dependent on guesswork, that is your blind spot. Systems thinking starts with these small, unforgiving questions.

Owning the customer after the quote is not ownership of a file. It is ownership of confidence. Someone must be responsible for ensuring the customer is not left uninformed, unanswered, and unsupported at any stage. When that responsibility is clear step by step, there is no more need for one solitary salesperson to carry everything alone; departments surprise one another less, and the customer can move their own work forward instead of chasing the organization. The system, in that state, does not merely move an order forward; it transfers confidence from one stage to the next.

That is the difference between a process that merely looks correct on a diagram and one that preserves customer trust even on busy days.