I was going to write a long intro to this explaining how important it is to keep your customers happy. In second thought I realized its pretty obvious. So I'm going to simply list a few guidelines and insights I gave our project managers:
1.
Setting expectation from the beginning
and along the way, will result in better flow and understanding on both sides.
2.
Calling a customer is hardly
ever a wrong move
3.
Being early for a call is much better
than being late. Most conference bridges allows you to be on the call
early while continuing to do your emails
4. It's recommended to use social networks to make the personal bond. Adding a picture in skype is also recommended.
6.
Try to gain as many access points to
the customer as possible, this comes very handy at times of a crisis. (ie: Email; skype; phone; mobile; phone of employee sitting close by; receptionist
contact details).
7.
Whenever the customer
is criticizing, try to take his side and blame the system, policy,
process, industry, world, ...
8.
Answering an email with a phone call
is very often a smart move. This is especially true when:
a)
You don't understand something the
customer said - phone call can solve the misunderstanding in seconds
b)
The customer is criticizing you
and there is audience in the cc list
c)
The customer is angry due to a
misunderstanding
d)
The email thread
becomes unnecessarily long
9.
The customer contact is not making
your life hard on purpose. Try to understand his challenges in
getting you the information/approval you need. Once you understand
his challenges you may be able to help him solve them.
10. Whenever
a crisis occurs the best thing to do is to increase the communication with the
customer as much as possible, come with a plan.
11. Notify
the customer when he is misbehaving - simply let him know - don't make a fuss
over it.
12. Support
issues:
a)
Notify the customer that you received
his request.
b)
Let the customer know that you understand
the severity/urgency/business-implications of the situation and that you will
apply special effort / taking the problem very seriously.
c)
Communicate the process.
d)
Communicate to the customer when the
problem was identified.
e)
Communicate the resolution estimated timeline
to the customer even if you are unsure.
f)
Once the problem is resolved, inform
the customer.
when relevant let him know we are also applying new procedure to essure that the
problem will not happen again.
13. Angry customer is better than indifferent customer. Anger shows that he still cares while indifference shows he gave up and made a decision to cancel.
14. The customer is not stupid (it doesn't get you anywhere saying he is), take proactive action to explain things better/in a different way.
15. It will be easier to get the customer's attention at the beginning of the project - right after signing the contract. the willingness to assist is higher and the resources are more available at that time.
16. Complicated integrations require the attention of the relevant team (from both sides) at the beginning of the project.
17. Long lasting issues – should be solved by getting the relevant people to the same room/ phone call (if impossible) à push until issue is identified & solved (always better to do it at the beginning of the project when the customer is more dedicated).
18. Customer does not like to feel in the dark – most of the time it is better to communicate the difficulties/delays expected then to be late.
19. When you have conflicts – you may find it helpful to consult the customer, he may solve it to you easily.