← All diaries

Cover image: Forty-Seven People in the Chat, Nobody Who Can Approve

Customer-facingNo. 0043 min read

Forty-Seven People in the Chat, Nobody Who Can Approve

By Ali Kaddoura

Imagine trying to get a beard trim while your phone runs a multinational deal operation. The group has 47 members. The customer asks who can actually approve the request.

Read by 46.

The barber is the only person present with clear authority to make a cut. Everyone else is waiting for someone senior to start typing.

A crowded conversation can hide an empty role

Deal groups can be useful. They connect people quickly, surface a blocker and help colleagues coordinate across a vendor, partner and customer. The problem starts when membership is mistaken for responsibility.

One person understands the requirement. Another can recommend a commercial exception. A third knows the delivery constraints. None may be authorised to approve the actual request. Adding all three to the same conversation does not combine their permissions into a decision.

Sellers sometimes create the confusion themselves. Under pressure to keep momentum, they invite everyone who might help. The group grows faster than the question becomes clear. Soon every notification has an audience and no owner.

A customer should not have to reverse-engineer your internal organisation from the names in a chat. They need a dependable contact who can route the request and return with an authorised answer.

Give the question a route and a return time

Start by stating the decision precisely. Is the customer asking for a price exception, a contract change, a delivery date or additional scope? “Please approve” is hard to act on when the package keeps changing between messages.

Identify who can decide that particular issue and who must provide input. Confirm this with the relevant team; a senior title alone does not establish approval authority. If the request crosses organisations, each organisation may need to approve its own commitment.

Then name one coordinator to carry the answer back.

Try: “I will coordinate this request. We are checking commercial and delivery approval separately, and I will update you by tomorrow afternoon, even if the decision is still pending.” Only offer a checkpoint you can keep.

That response does not pretend approval has happened. It gives the customer someone accountable for progress and stops five colleagues from sending five incompatible reassurances.

After a decision, capture what was approved, by whom, and against which version of the request in the agreed record. A thumbs-up beside an earlier price is a poor reference for a later package containing extra services.

Keep sensitive internal deliberation in the appropriate channel and share the customer-facing outcome through the agreed contact. Coordination should reduce the work the customer has to do, not turn them into the moderator of your internal debate.

The group may still contain 47 people. At least the next question will have somewhere to go.

Yalla takeaway: Name the decision, confirm the authority and give one person responsibility for returning the answer.

Which approval question in your current deal has plenty of visibility but no clear owner?

Yalla. Go sell.