﻿<!--<!DOCTYPE nitf SYSTEM "nitf-3-4.dtd">-->
<nitf>
  <head>
    <title id="Title">&amp; çâÌæÚUæð´ ·¤è ¥ôÚU Îð¹Ùæ ÁæÚUè ÚU¹ð´ ¥ÍæüÌ ¥ÂÙð ÜÿØ ÂÚU ŠØæÙ ÚU¹ð´Ð ãæÚU Ù ×æÙð´, €UØô´ç·¤ ·¤æ× ·¤ÚUÙð âð ¥æÂ·¤ô ©gðàØ ·¤è Âýæç# ãôÌè ãñ ¥õÚU ÁèßÙ ·¤æ ¹æÜèÂÙ ÎêÚU ãôÌæ ãñÐ ÖÜð ãè ÁèßÙ ×ð´ ç·¤ÌÙè Öè ·¤çÆÙæ§ü €UØô´ Ù ¥æ°, çÁ™ææâæ ¥õÚU ©ˆâæã ÕÙæ° ÚU¹ð´Ð ŠØæÙ ÚU¹ð´, ÜÿØ ã×ðàææ ¥æÂ·Ô¤ Âæâ ãôÌð ãñ´ çÁ‹ãð´ ÂæÙð ·Ô¤ çÜ° ÂýØæâ ¥æÂ ·¤Öè Öè àæéM¤ ·¤ÚU â·¤Ìð ãñ´Ð</title>
    <docdata management-doc-idref="">
      <date.issue id="CreationDate" norm="" />
      <du-key id="rev-ver" generation="1" version="Default" />
      <du-key id="Parent-Version" version="" />
      <identified-content>
        <classifier id="newspro-nitf" value="r2" />
        <classifier id="Newspro-App" value="Epaper" />
        <classifier id="Content-Type" value="Story" />
        <classifier id="storyID" value="" />
        <classifier id="CmsConID" value="" />
        <classifier id="Desk" value="" />
        <classifier id="Source" value="" />
        <classifier id="Edition" value="" />
        <classifier id="Category" value="-1" />
        <classifier id="UserName" value="" />
        <classifier id="PublicationDate" value="20220103" />
        <classifier id="PublicationName" value="Hindustan" />
        <classifier id="IsPublished" value="Y" />
        <classifier id="IsPlaced" value="Y" />
        <classifier id="IsCompleated" value="N" />
        <classifier id="IsProofed" value="N" />
        <classifier id="User" value="" />
        <classifier id="Headline-Count" value="" />
        <classifier id="Slug-Count" value="0" />
        <classifier id="Photo-Count" value="0" />
        <classifier id="Caption-Count" value="0" />
        <classifier id="Word-Count" value="0" />
        <classifier id="Character-Count" value="0" />
        <classifier id="Location" value="" />
        <classifier id="TemplateType" value="1" />
        <classifier id="StoryType" value="Story" />
        <classifier id="Author" value="" />
        <classifier id="UOM" value="mm" />
        <classifier id="IndexPage" value="" />
        <classifier id="box-geometry" value="-7,40,950,284" />
        <classifier id="Epaper-Build" value="Build-No: 2.1.0.9, Dated: 04/12/2021" />
        <classifier id="Application" value="QuarkXpress 8" />
        <classifier id="MachineName" value="TV0254" />
        <classifier id="ProcessingDateTime" value="Mon 03 Jan 2022 07:00:24" />
      </identified-content>
      <urgency id="home-page" ed-urg="0" />
      <urgency id="priority" ed-urg="0" />
      <doc-scope id="scope" value="0" />
    </docdata>
    <pubdata type="print" name="Hindustan" date.publication="20220103T000000+5.30" edition.name="RPAjmCity" edition.area="RPAjmCity" position.section="03012022-RPAjmCity-01-PAGE-03012022_RPAjmCity_01~WS4~" position.sequence="01" ex-ref="03012022-RPAjmCity-01-PAGE-03012022_RPAjmCity_01~WS4~" SectionName="" />
  </head>
  <body>
    <body.head>
      <hedline>
        <hl1 id="kicker" class="1" style="Shoulder" MainHead="false">
          <lang class="3" style="kicker" font="Patrika18" size="12">
</lang>
        </hl1>
        <hl1 id="Headline" class="1" style="Headline" MainHead="true">
          <lang class="3" style="Headline" font="Patrika18" fontStyle="Bold" size="15">Take care of your email
</lang>
        </hl1>
        <hl1 id="Subhead" class="1" style="Subhead" MainHead="true">
          <lang class="3" style="Subhead" font="Patrika18" fontStyle="Bold" size="15">
</lang>
        </hl1>
        <hl1 id="Byline" class="1" style="Byline" MainHead="true">
          <lang class="3" style="Byline" font="Patrika18" fontStyle="Bold" size="15">Star Business Desk
</lang>
        </hl1>
      </hedline>
      <summary></summary>
      <quotes>
        <quote></quote>
      </quotes>
    </body.head>
    <body.content id="Bodytext">
      <block>
        <media id="1" media-type="image">
          <media-reference id="tn" source-credit="" data-location="1" ImgOrderNum="" source="03012022-RPAjmCity-01-PAGE-03012022_RPAjmCity_01~WS4~_SubGroupImage_720446704_tn.JPG" Units="pixels" width="50" height="50"></media-reference>
          <media-caption id="Caption1" font="">
            <hl2></hl2>
          </media-caption>
          <media-reference id="tn" source-credit="" data-location="2" ImgOrderNum="" source="03012022-RPAjmCity-01-PAGE-03012022_RPAjmCity_01~WS4~_SubGroupImage_720325568_tn.JPG" Units="pixels" width="50" height="50"></media-reference>
          <media-caption id="Caption1" font="">
            <hl2></hl2>
          </media-caption>
          <media-reference id="tn" source-credit="" data-location="3" ImgOrderNum="" source="03012022-RPAjmCity-01-PAGE-03012022_RPAjmCity_01~WS4~_SubGroupImage_720436736_tn.JPG" Units="pixels" width="50" height="50"></media-reference>
          <media-caption id="Caption1" font="">
            <hl2></hl2>
          </media-caption>
          <media-reference id="tn" source-credit="" data-location="4" ImgOrderNum="" source="03012022-RPAjmCity-01-PAGE-03012022_RPAjmCity_01~WS4~_SubGroupImage_715957792_tn.JPG" Units="pixels" width="50" height="50"></media-reference>
          <media-caption id="Caption1" font="">
            <hl2></hl2>
          </media-caption>
          <media-reference id="tn" source-credit="" data-location="5" ImgOrderNum="" source="03P1 StephenHawkings_tn.JPG" Units="pixels" width="50" height="50"></media-reference>
          <media-caption id="Caption1" font="">
            <hl2></hl2>
          </media-caption>
        </media>
      </block>
      <p style=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Patrika15 Ultra" fontStyle="Bold" size="130">****Do not make an email longer than it needs to be. Remember that reading an email is harder than reading printed communications and a long email can be very discouraging to read ****
</lang>
      </p>
      <p class=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Patrika15 Ultra" fontStyle="Bold" size="130">Many companies have still not realised how important their email communications are. They send email replies late or not at all, or send replies that do not actually answer the questions you asked. If your company is able to deal professionally with email, this will provide your company with that all important competitive edge. Moreover by educating employees as to what can and cannot be said in an email, you can protect your company from awkward liability issues.</lang>
      </p>
      <p class=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Patrika15 Ultra" fontStyle="Bold" size="130">By requiring employees to use appropriate, businesslike language in all electronic communications, employers can limit their liability risks and improve the overall effectiveness. A company needs to implement etiquette rules for the following three reasons:</lang>
      </p>
      <p class=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Patrika15 Ultra" fontStyle="Bold" size="130">Professionalism: by using proper email language your company will convey a professional image.</lang>
      </p>
      <p class=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Patrika15 Ultra" fontStyle="Bold" size="130">Efficiency: emails that get to the point are much more effective than poorly worded emails.</lang>
      </p>
      <p class=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Patrika15 Ultra" fontStyle="Bold" size="130">Protection from liability: employee awareness of email risks will protect your company from costly law suits.</lang>
      </p>
      <p class=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Patrika15 Ultra" fontStyle="Bold" size="130">So following are the things to do.</lang>
      </p>
      <p class=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Patrika15 Ultra" fontStyle="Bold" size="130">Be concise and to the point: Do not make an email longer than it needs to be. Remember that reading an email is harder than reading printed communications and a long email can be very discouraging to read.</lang>
      </p>
      <p class=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Patrika15 Ultra" fontStyle="Bold" size="130">Answer all questions, and pre-empt further questions: An email reply must answer all questions, and pre-empt further questions. If you do not answer all the questions in the original email, you will receive further emails regarding the unanswered questions, which will not only waste your time and your customer's time but also cause considerable frustration. Moreover, if you are able to pre-empt relevant questions, your customer will be grateful and impressed with your efficient and thoughtful customer service.</lang>
      </p>
      <p class=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Patrika15 Ultra" fontStyle="Bold" size="130">Use proper spelling, grammar and punctuation: This is not only important because improper spelling, grammar and punctuation give a bad impression of your company, it is also important for conveying the message properly. E-mails with no full stops or commas are difficult to read and can sometimes even change the meaning of the text.</lang>
      </p>
      <p class=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Patrika15 Ultra" fontStyle="Bold" size="130">Make it personal: Not only should the email be personally addressed, it should also include personal i.e. customised content. For this reason, auto replies are usually not very effective. However, templates can be used effectively in this way.</lang>
      </p>
      <p class=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Patrika15 Ultra" fontStyle="Bold" size="130">Use templates for frequently used responses: Some questions you get over and over again, such as price of a particular product, or directions to your office or how to subscribe to your upcoming product. Save these texts as response templates and paste these into your message when you need them.</lang>
      </p>
      <p class=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Patrika15 Ultra" fontStyle="Bold" size="130">Answer swiftly: Customers send an email because they wish to receive a quick response. If they did not want a quick response they would send a letter or a fax. Therefore, each email should be replied to within at least 24 hours, and preferably within the same working day. If the email is complicated, just send an email back saying that you have received it and that you will get back to them. This will put the customer's mind at rest and usually customers will then be very patient.</lang>
      </p>
      <p class=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Patrika15 Ultra" fontStyle="Bold" size="130">Do not write in CAPITALS: IF YOU WRITE IN CAPITALS IT SEEMS AS IF YOU ARE SHOUTING. This can be highly annoying and might trigger an unwanted response in the form of a flame mail. Therefore, try not to send any email text in capitals.</lang>
      </p>
      <p class=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Patrika15 Ultra" fontStyle="Bold" size="130">Take care with abbreviations and emoticons: In business emails, try not to use abbreviations such as BTW (by the way) and LOL (laugh out loud). The recipient might not be aware of the meanings of the abbreviations and in business emails these are generally not appropriate. The same goes for emoticons, such as the smiley:-). If you are not sure whether your recipient knows what it means, it is better not to use it.</lang>
      </p>
      <p class=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Patrika15 Ultra" fontStyle="Bold" size="130">Do not use email to discuss confidential information: Sending an email is like sending a postcard. If you don't want your email</lang>
      </p>
      <p class=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Patrika15 Ultra" fontStyle="Bold" size="130">to be displayed on a bulletin board, don't send it. Moreover, never make any libelous, sexist or racially discriminating comments in emails, even if they are meant to be a joke.</lang>
      </p>
      <p class=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Patrika15 Ultra" fontStyle="Bold" size="130">Use a meaningful subject: Try to use a subject that is meaningful to the recipient as well as yourself. For instance, when you send an email to a company requesting information about a product, it is better to mention the actual name of the product.</lang>
      </p>
      <p class=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Patrika15 Ultra" fontStyle="Bold" size="130">Use active instead of passive: Try to use the active voice of a verb wherever possible. For instance, 'We will process your order today', sounds better than 'Your order will be processed today'.</lang>
      </p>
      <p class=".Bodylaser">
        <lang class="3" style=".Bodylaser" font="Patrika15 Ultra" fontStyle="Bold" size="130">With details from www.emailreplies.com</lang>
      </p>
    </body.content>
  </body>
</nitf>