Brand
Position
14
Sprachlevel
Audio-Übung
Nein
Original-Rubrik
Business Skills
Lernsprache
Mono-Lingual
Mono-Lingual
Dauer / Länge
303
Quelle
Ausgabentitel
Business Skills - the art of polite emails
Ausgabe EVT
Ausgabennummer
202103
Audio Transcript Flag
No problematic content found
Digitization status
Stand alone
Off
Audio-Transkript
getting the tone right email rudeness among team members can take many forms. The direct kind might include passive aggressive statements or sarcastic put downs. The non reply is an example of the more common indirect kind of email rudeness. Both can trigger feelings of stress, Both lack empathy and the worst kind could get you fired. Fortunately most of the time you can safely assume that email rudeness isn't deliberate at the same time, you should also assume that your emails could be taken the wrong way. There are a few obvious reasons for this. Emails lack the warmth of the human voice that you get in a phone call. The non verbal cues you would get in a face to face meeting or a video call are also missing. All the reader has to go on are your words? So choose them carefully. Here we present seven tips on how to make your emails more polite. Open with a pleasantry. Even if you're emailing the same people back and forth on a regular basis, you can still include some pleasantries from time to time. You could ask how's it going? Which would cover anything the reader might want to talk about. Another option would be to say that you hope someone is doing okay during a crisis or in uncertain times. This might be your safest option. Show recognition. Alternatively, if appropriate, you could open with some praise. Pay attention to how people communicate and adjust your language to match the tone and culture of your team or company. While awesome may feel over the Top in one team. Nice may come across as too weak in another. Make a note of the positive language that is frequently used and try to mirror it. Keep to the facts. If an email is clearly route, you should remain calm and keep to the facts in your reply. Remember it's quite possible that the writer is frustrated about the fact that they are unable to move forward with their own work and don't realize that they are being rude to you. Think about the reasons why you find the email route, then avoid making the same mistakes in your own emails. Be polite and helpful when you need to ask for something. Try a more polite structure use could you or would you instead of the imperative or begin a request with? We depreciate if you notice that someone seems frustrated, try offering your support keep it short but upbeat. Gretchen McCulloch, an internet linguist and author of the book because internet recommends that if your responses are short they shouldn't be too short while in okay, on its own can seem rude. She writes an okay, sounds good or okay, great. Doesn't note the use of the exclamation mark at the end. McCulloch describes this usage as a kind of polite social smile included to make your response more upbeat. Don't add too many exclamation marks though or it might make you appear juvenile. Mix it up. If you feel downbeat after reading an email, maybe it's time to choose a different form of communication, pick up the phone or schedule a video call and clear up any problems in person. It's important to discuss your communication styles and agree on a code of conduct in the team. Take a positive approach. It's all too easy to see rudeness in an email when it wasn't intended. The way you end your email reply will often influence how the person feels after reading it. So try to end on a positive note that said, if you feel someone is using email to make a personal attack on you, that will require a very different approach forward such emails to your boss or personnel manager and include an explanation of the situation. There's no reason why you should have to put up with such rudeness.
Transcription JsonFile Url
https://s3.eu-central-1.amazonaws.com/spotlight.audio/transcriptions/business-spotlight/Audio-Trainer/202103/014_030_Business_Spotlight_Audio_0321.json
ContentHub Node reference - AudioTrack (NID)
75471
ContentHub Node reference - AudioArchive (NID)
75488
File Reference
https://s3.eu-central-1.amazonaws.com/spotlight.audio/business-spotlight-audio/standard/202103/audio/014_030_Business_Spotlight_Audio_0321.mp3
Audio Update Status
Original Mp3
Dauer precise
302.79