<?xml version="1.0"?>
<rss version="2.0">
<channel>
  <title>BitLogistics - notification tag</title>
  <link>http://blog.bitlogistics.com:80/bitlogistics/tags/notification/</link>
  <description>Supply Chain Management Solution</description>
  <language>en</language>
  <copyright>BitLogistics</copyright>
  <lastBuildDate>Fri, 18 Jul 2008 10:25:20 GMT</lastBuildDate>
  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>Avoiding language issues</title>
    <link>http://blog.bitlogistics.com:80/bitlogistics/2007/08/22/avoiding_language_issues.html</link>
    
      
        <description>
          &lt;p&gt;We were recently talking to someone who works for an import-export company. He is French, and told as that one of the difficulties he has when dealing with Eastern European transporters on the telephone is that they do not understand each other&#039;s English. They solve this by following-up each telephone call with an e-mail to confirm what was said. This works, but it costs time.&lt;/p&gt;

&lt;p&gt;Although we had not thought of this before, it turns out that the &lt;a href=&#034;http://www.visiblelogistics.com/&#034;&gt;VisibleLogistics&lt;/a&gt; notification e-mails I described in my previous post help a lot here. It is less effort to update an order status on a web page, and generate a notification e-mail, than it is to type the e-mail by hand. Furthermore, each e-mail has a standard structure, which makes it easier to translate and understand.&lt;/p&gt;

&lt;p&gt;I guess we should think about adding the ability to generate notifications in Polish and Czech, for example.&lt;/p&gt;
        </description>
      
      
    
    
    
    <category>VisibleLogistics</category>
    
    <comments>http://blog.bitlogistics.com:80/bitlogistics/2007/08/22/avoiding_language_issues.html#comments</comments>
    <guid isPermaLink="true">http://blog.bitlogistics.com:80/bitlogistics/2007/08/22/avoiding_language_issues.html</guid>
    <pubDate>Wed, 22 Aug 2007 10:07:42 GMT</pubDate>
  </item>
  
  <item>
    <title>Avoiding duplicate data entry in e-mail</title>
    <link>http://blog.bitlogistics.com:80/bitlogistics/2007/08/16/avoiding_duplicate_data_entry_in_e_mail.html</link>
    
      
        <description>
          &lt;p&gt;While talking to people about our forthcoming &lt;a href=&#034;http://www.visiblelogistics.com/&#034;&gt;VisibleLogistics&lt;/a&gt; product, we are conscious of the fact that people want to avoid entering the same data into two &#039;systems&#039;. After all, everyone knows that the first rule of data entry is never re-key data, right?&lt;/p&gt;

&lt;p&gt;Well, that is what people say, except for when the other system is e-mail. They just copy or retype order information into an e-mail whenever they need to let their customer know that the order status has changed. This is why VisibleLogistics sends e-mail notifications like this one:&lt;/p&gt;

&lt;p&gt;&lt;img src=&#034;/bitlogistics/images/order-status-email.png&#034; alt=&#034;VisibleLogistics order creation e-mail notification&#034;/&gt;&lt;/p&gt;

&lt;p&gt;Not only does it save you time by sending these automatically, but they save you double typing because the e-mail contains basic order information and a hyperlink to order information on the web.&lt;/p&gt;
        </description>
      
      
    
    
    
    <category>VisibleLogistics</category>
    
    <comments>http://blog.bitlogistics.com:80/bitlogistics/2007/08/16/avoiding_duplicate_data_entry_in_e_mail.html#comments</comments>
    <guid isPermaLink="true">http://blog.bitlogistics.com:80/bitlogistics/2007/08/16/avoiding_duplicate_data_entry_in_e_mail.html</guid>
    <pubDate>Thu, 16 Aug 2007 14:47:00 GMT</pubDate>
  </item>
  
  </channel>
</rss>
