Client communication: Difference between revisions
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
{{a|devil|[[File:biblical outreach.png|450px|frameless|center]]}} | {{a|devil|[[File:biblical outreach.png|450px|frameless|center]]}}When engaged in the business of customer communications, whether you are a [[law firm]] composing [[Client alert|client bulletins]] and [[Law firm seminar|seminars]], a [[client outreach]] team creating mail-shots to meet financial services regulations or — ''speak it softly'': preparing [[Contract|customer contracts]] — you know, ''actual legal [[verbiage]]''<ref>While true, considering contracts as a form of client communication to be dressed up and somehow made presentable is regarded as, if not a type of mental illness, then a bridge too far, by most in the [[legal community]].</ref> — there is a lot to be said for getting your tone and presentation right. | ||
When engaged in the business of customer communications, whether you are a [[law firm]] composing [[Client alert|client bulletins]] and [[Law firm seminar|seminars]], a [[client outreach]] team creating mail-shots to meet financial services regulations or — ''speak it softly'': preparing [[Contract|customer contracts]] — you know, ''actual legal [[verbiage]]''<ref>While true, considering contracts as a form of client communication to be dressed up and somehow made presentable is regarded as, if not a type of mental illness, then a bridge too far, by most in the [[legal community]].</ref> — there is a lot to be said for getting your tone and presentation right. | |||
However much there is to be said, not much of it is habitually listened to, and those who do listen have a chance to set their communications above all the others. | However much there is to be said, not much of it is habitually listened to, and those who do listen have a chance to set their communications above all the others. | ||
Line 65: | Line 64: | ||
====Sub-rule: avoid disclaimers==== | ====Sub-rule: avoid disclaimers==== | ||
Think first “what will my customer think of ''me'' if I say that”, rather than “what if I get it wrong and my customer sues me?” You are a professional. You are good at what you do. Trust yourself not to get it wrong. Disclaimers are like [[airbags]]. [[You only need airbags if you don’t steer straight]]. Concentrate on defensive driving, not crash mats. If you ''have'' to have a disclaimer — and I know, you ''will'' have to have one — keep it brief, to the point and put it at the end. If the first thing your customer reads is “[[Please be advised]] we take no responsibility for this, we are only doing this because someone said we have to, so on your own head be it”, your customer is going to think, “gee, what a douche”. Generally, that’s not how you want your customer to be thinking now, is it? | Think first “what will my customer think of ''me'' if I say that”, rather than “what if I get it wrong and my customer sues me?” You are a professional. You are good at what you do. Trust yourself not to get it wrong. Disclaimers are like [[airbags]]. [[You only need airbags if you don’t steer straight]]. Concentrate on defensive driving, not crash mats. If you ''have'' to have a disclaimer — and I know, you ''will'' have to have one — keep it brief, to the point and put it at the end. If the first thing your customer reads is “[[Please be advised]] we take no responsibility for this, we are only doing this because someone said we have to, so on your own head be it”, your customer is going to think, “gee, what a douche”. Generally, that’s not how you want your customer to be thinking now, is it? | ||
{{sa}} | |||
*[[Law firm seminar]] | |||
{{ref}} |
Revision as of 22:22, 7 December 2021
|
When engaged in the business of customer communications, whether you are a law firm composing client bulletins and seminars, a client outreach team creating mail-shots to meet financial services regulations or — speak it softly: preparing customer contracts — you know, actual legal verbiage[1] — there is a lot to be said for getting your tone and presentation right.
However much there is to be said, not much of it is habitually listened to, and those who do listen have a chance to set their communications above all the others.
First: for your customer, all client communications are a drag. Customers do not want advertising or spam arriving unbidden in their inboxes, much less problems they didn’t even know they had. So even if they are not specifically a damage-limitation exercise, if practice, client communications always are: if you are writing to all of your customers at once, your news is either outright bad — “we’ve screwed something up” — or tedious — “regulations have changed and there is some stuff you need to know, say or do” — or annoying — “there is something we forgot to tell you, or we need to correct what we’ve already told you”.
Remember: if your customers care at all about your communiqué, they will care less about it than you do. Perhaps they should care, but they won’t.
With this in mind, the JC offers you some rules of client communication.
Rule 1: be brief
It ought to go without saying, but the modern professional seems unable to grasp the idea: keep it short. Do not use two words when one will do. Do not use one word when none will do. Writing to customers is like flying on the cheapest budget airline in the world, your words are your luggage.
Sub-rule: get to the point
Presume that if a customer starts reading at all, she will stop reading you prose far more quickly than you would. If your client must do something, state it clearly and early in the communication.
Don’t say | Do say |
---|---|
The original fund status certificate needs to be in place at the Bank before the taxable income event is due to be paid. To avoid delay of certificate recording, customers are reminded to send the fund status certificates to the Bank. |
From 1 July, you must provide us with newly issued WHT certificates before the dividend record date. |
Sub-rule: don’t show your working
Having been mired in it for months, your subject matter experts will have dominion over every last detail and nuance of the topic. They will barely be able to resist regurgitating them all over your letter. Don’t let them. Say only what a non-specialist needs to hear to grasp the gist. Say that as clearly as you can, and say no more.
Don’t say | Do say |
---|---|
The Upper House of the German Parliament on 28 May 2021 approved the bill pertaining to the modernisation of withholding tax relief procedures (“AbzStEntModG”; Abzugsteuerentlastungsmodernisierungsgesetz), parts of which are due to enter into force on 1 July 2021, especially amendments to the German Investment Tax Act. The bill foresees a change in terms of the relief at source procedure applicable to income payments subject to German withholding tax (for example dividend and taxable interest payments) paid to a foreign investment fund (“beschränkt körperschaftsteuerpflichtiger Investmentfonds”). In this context, newly issued fund status certificates will contain information on the corporation tax status (“Körperschaftsteuerstatus”) of the certified investment fund. Current valid certificates that are already submitted, however, will stay valid according to a letter issued by the Ministry of Finance on 1 June 2021 (BMF – reference GZ: IV C 1 - S 1980-1/19/10027 :006 DOK: 2021/0577184). | On 1 July, Germany changed its rules for claiming withholding tax relief on dividend income. These changes affect your non-resident investment funds. |
Sub-rule: don’t track regulatory language
It is fashionable among legal eagles to “track the language of the legislation” in client communications. This ensures utmost fidelity with the rules: one cannot be blamed for getting anything wrong if one copies out the text verbatim. YOU SHOULD NOT WRITE WITH THE MAIN GOAL OF AVOIDING BLAME FOR GETTING THINGS WRONG. Write with the objective of getting things right. Own your expertise. Own your language. Be brave. Tracking legislation is lazy. It is timid. It rejects responsibility and puts it on the customer. It converts your regulatory problem into your customer’s.
Your job is to to make your customer’s life easier, not harder. You are meant to internalise the ugliness of your regulatory environment, not to lay it on your client. It is not your client’s problem. It most likely meant to be for your client’s benefit. So: speak only in terms of consequences, and action. Where this points back to regulation, summarise. Extract. Contextualise. Put this in a format the customer can understand and relate to. Think like a professional writer, because you are a goddamn professional writer.
Rule 2: be clear
Sub-rule: State consequences
Be clear what will happen if the customer doesn’t reply. Don’t be judgmental; just matter of fact.
Don’t say | Do say |
---|---|
In accordance with the above-mentioned bill, any application for the reversal of overpaid tax, via presentation of a fund status certificate with retroactive validity, will no longer be possible via the Bank. Instead, the reclaim must be addressed directly to the Federal Central Tax Office (Bundeszentralamt für Steuern; BZSt). Consequently, as of 1 July 2021 customers providing a fund status certificate for a foreign investment fund after the payment date of the taxable income event cannot be refunded. Full tax must be withheld. The Bank will in turn issue a tax voucher upon customer request. | If you do not, you must file your WHT reclaim directly with the German tax authority. |
Rule 3: be persuasive
To the extent following rules 1 and 2 don’t get you there, remember you are writing with the idea of not just discharging some regulatory obligation to your customer — that’s a second order objective — but to make your customer think well of you. Frame your letter to appeal to your correspondents, so they are more likely to read it.
Remember Robert Cialdini’s six rules of persuasion. Deploy them where you can.
Sub-rule: be personal
Personalise it. don’t say “Dear Client” — don’t ever do that — but address an individual by name, and send from an individual, by name.
Yes, it is a mass mailshot to every customer in the book. But we are in 2021, friends. It is not beyond the wit of technology, anymore to use a freaking mail merge.[2] What’s stopping you? Oh, crappy client static data? Fix your damn client static data. If your salespeople aren’t keeping it up to date, they’re not doing their jobs. Either have good client static data, and use it to demonstrate you care enough about your customer to be justified in calling them “dear” — or don’t, accept your customers to you are a passive herd of cattle there only to be milked, and don’t try to be ingratiating while you do it.
Don’t say “please be advised”. Ever. Just don’t do it. These are your valuable customers, not truculent secondary school children plotting to burn down the staff room.
Sub-rule: be emphatic
say what you mean with strong, active, assertive nouns and verbs. Don’t use weasle words. Avoid “seems to”, “appears to be”, “slightly”, “almost”, “practically”, “virtually”.
Sub-rule: avoid disclaimers
Think first “what will my customer think of me if I say that”, rather than “what if I get it wrong and my customer sues me?” You are a professional. You are good at what you do. Trust yourself not to get it wrong. Disclaimers are like airbags. You only need airbags if you don’t steer straight. Concentrate on defensive driving, not crash mats. If you have to have a disclaimer — and I know, you will have to have one — keep it brief, to the point and put it at the end. If the first thing your customer reads is “Please be advised we take no responsibility for this, we are only doing this because someone said we have to, so on your own head be it”, your customer is going to think, “gee, what a douche”. Generally, that’s not how you want your customer to be thinking now, is it?
See also
References
- ↑ While true, considering contracts as a form of client communication to be dressed up and somehow made presentable is regarded as, if not a type of mental illness, then a bridge too far, by most in the legal community.
- ↑ You thought I was going to say “use neural networks to guess customer names” didn’t you?