As a project manager, how can we deal with the relationship between different types of customers?

As a project manager, it is very important to deal with the relationship with the customer. But how can we deal with customer relationships? What types of customer personnel are there? Are the responses of different types of customers the same? Next, let's look at the customer types that we often encounter in our daily work. How should we deal with the relationship with them?

Type	Features	Response Policy
Authoritative decision-making	Such customers often have authoritative technical, business, and management capabilities, and have decision-making power on the affairs themselves.	Positive Response to Technical Support
Typical decision makers	Has business decision-making power, but is not an expert in business and technology.	Express technology and business in plain language to Minimize formal conflicts. The effect will be better as follows:
Technical Experts	Focus only on technical implementation, details, and technical feasibility and focus on technical implementation and quality.	Directly respond positively, explaining technical feasibility and Solutions
Confused management type	It is the manager of Party A and has certain decision-making power and influence, but is not knowledgeable about project management. Sometimes it is troublesome to intervene in the project from time to time.	Politely refuse and take the initiative. Once he has the initiative, he will guide your project to fail.
And mud	Do not take responsibility, but do not offend any party and do not solve the problem, but do not make trouble belongs to the Old Man-type	Don't count on solving your problems. You can use them to make things easier. Maintain harmony
Hypocritical expert	There is a certain understanding of technology and business, but it is not very deep. Most of the new business and technical backbone, or those who have been "buried" for many years, like to sell their technical capabilities on the point, lack of overall picture.	You can also be an object of use, or keep it away from your project. You can also consider the overall situation, leave it blank, and consider it in depth from the technical perspective.