<?xml version="1.0" encoding="UTF-8"?>
<blog-post>
  <author-id type="integer">32561</author-id>
  <blog-comments-count type="integer">1</blog-comments-count>
  <blog-post-status-id type="integer">3</blog-post-status-id>
  <body-format>econsultancy_xml</body-format>
  <body-formatted>
  &lt;p&gt;In my webmail this week I received a couple of unexpected but welcome emails from a well-known drinks brand&#160;that I gave my address to in a pub some months ago. &lt;/p&gt;
  &lt;p&gt;Despite the time lag, I remembered I&#8217;d given permission and was interested to see what they had to offer.&lt;br /&gt;&lt;br /&gt;However, as I&#8217;d received two identical emails from them and as a good email citizen, I pressed the unsubscribe button on one to help tidy up the database.&lt;/p&gt;
  &lt;p&gt;This presented an unsubscribe page with more fields in it than Norfolk. &lt;/p&gt;
  &lt;p&gt;In addition to mandatory postal address fields (why?), title, name and shoe size, the page listed not just the brand I was responding to but an additional eight brands owned by the same drinks group with four tick boxes for each. &lt;/p&gt;
  &lt;p&gt;That&#8217;s a total of 42 fields that need filling in &#8211; horrible!&lt;br /&gt;&lt;br /&gt;And so I did the easier thing, which was hit the spam button.&lt;/p&gt;
  &lt;p&gt;We&#8217;re talking a lot about email CRM at the moment, whereby the customer&#8217;s experience at every point&#160;in the relationship needs to be considered carefully -and that should include the unsubscribe experience. &lt;/p&gt;
  &lt;p&gt;By law, we are required to keep unsubscribe procedure simple in any case, but from a commercial perspective, if you don&#8217;t allow your potential customer to leave easily, they&#8217;re unlikely to give you permission to email them again, or worse, classify you as spam. &lt;br /&gt;&lt;br /&gt;My recommendation would be a much simpler process, which doesn&#8217;t ask for information customers may not want to give and has just one or two fields to fill in plus possibly an option to give feedback to a customer service team. &lt;/p&gt;
  &lt;p&gt;It may then be possible, if appropriate, to re-establish the relationship in a different way or at a later point.&lt;br /&gt;&lt;br /&gt;No matter how well intentioned, 42 fields are never a good thing &#8211; unless you&#8217;re a farmer.&lt;/p&gt;
  &lt;p&gt;
    &lt;strong&gt;
      &lt;em&gt;Michael Weston is the managing director of &lt;/em&gt;
    &lt;/strong&gt;
    &lt;a href="http://www.silverpop.com"&gt;
      &lt;strong&gt;
        &lt;em&gt;Silverpop&lt;/em&gt;
      &lt;/strong&gt;
    &lt;/a&gt;
    &lt;strong&gt;
      &lt;em&gt;.&lt;/em&gt;
    &lt;/strong&gt;
  &lt;/p&gt;
</body-formatted>
  <body-unformatted>&lt;FormattedContent xmlns="http://www.e-consultancy.com/schema/formattedContent/"&gt;
  &lt;Paragraph&gt;In my webmail this week I received a couple of unexpected but welcome emails from a well-known drinks brand&#160;that I gave my address to in a pub some months ago. &lt;/Paragraph&gt;
  &lt;Paragraph&gt;Despite the time lag, I remembered I&#8217;d given permission and was interested to see what they had to offer.&lt;LineBreak /&gt;&lt;LineBreak /&gt;However, as I&#8217;d received two identical emails from them and as a good email citizen, I pressed the unsubscribe button on one to help tidy up the database.&lt;/Paragraph&gt;
  &lt;Paragraph&gt;This presented an unsubscribe page with more fields in it than Norfolk. &lt;/Paragraph&gt;
  &lt;Paragraph&gt;In addition to mandatory postal address fields (why?), title, name and shoe size, the page listed not just the brand I was responding to but an additional eight brands owned by the same drinks group with four tick boxes for each. &lt;/Paragraph&gt;
  &lt;Paragraph&gt;That&#8217;s a total of 42 fields that need filling in &#8211; horrible!&lt;LineBreak /&gt;&lt;LineBreak /&gt;And so I did the easier thing, which was hit the spam button.&lt;/Paragraph&gt;
  &lt;Paragraph&gt;We&#8217;re talking a lot about email CRM at the moment, whereby the customer&#8217;s experience at every point&#160;in the relationship needs to be considered carefully -and that should include the unsubscribe experience. &lt;/Paragraph&gt;
  &lt;Paragraph&gt;By law, we are required to keep unsubscribe procedure simple in any case, but from a commercial perspective, if you don&#8217;t allow your potential customer to leave easily, they&#8217;re unlikely to give you permission to email them again, or worse, classify you as spam. &lt;LineBreak /&gt;&lt;LineBreak /&gt;My recommendation would be a much simpler process, which doesn&#8217;t ask for information customers may not want to give and has just one or two fields to fill in plus possibly an option to give feedback to a customer service team. &lt;/Paragraph&gt;
  &lt;Paragraph&gt;It may then be possible, if appropriate, to re-establish the relationship in a different way or at a later point.&lt;LineBreak /&gt;&lt;LineBreak /&gt;No matter how well intentioned, 42 fields are never a good thing &#8211; unless you&#8217;re a farmer.&lt;/Paragraph&gt;
  &lt;Paragraph&gt;
    &lt;Emphasis&gt;
      &lt;Quote&gt;Michael Weston is the managing director of &lt;/Quote&gt;
    &lt;/Emphasis&gt;
    &lt;Link URL="http://www.silverpop.com" Window="Self"&gt;
      &lt;Emphasis&gt;
        &lt;Quote&gt;Silverpop&lt;/Quote&gt;
      &lt;/Emphasis&gt;
    &lt;/Link&gt;
    &lt;Emphasis&gt;
      &lt;Quote&gt;.&lt;/Quote&gt;
    &lt;/Emphasis&gt;
  &lt;/Paragraph&gt;
&lt;/FormattedContent&gt;</body-unformatted>
  <created-at type="datetime">2007-11-27T15:22:00+00:00</created-at>
  <enabled-blog-comments-count type="integer">1</enabled-blog-comments-count>
  <expertise-level-id type="integer">1</expertise-level-id>
  <extract-format>econsultancy_xml</extract-format>
  <extract-formatted>
  &lt;p&gt;
    &lt;strong&gt;How did a reputable family of brands (whose products I enjoy a little too much) annoy me into hitting the SPAM button?&lt;/strong&gt;
  &lt;/p&gt;
</extract-formatted>
  <extract-unformatted>&lt;FormattedContent xmlns="http://www.e-consultancy.com/schema/formattedContent/"&gt;
  &lt;Paragraph&gt;
    &lt;Emphasis&gt;How did a reputable family of brands (whose products I enjoy a little too much) annoy me into hitting the SPAM button?&lt;/Emphasis&gt;
  &lt;/Paragraph&gt;
&lt;/FormattedContent&gt;</extract-unformatted>
  <featured type="boolean">false</featured>
  <id type="integer">1976</id>
  <learn-more-formatted>&lt;p&gt;For further information about email marketing, download Econsultancy's &lt;strong&gt;&lt;a href="http://econsultancy.com/reports/email-census"&gt;Email Census&lt;/a&gt;&lt;/strong&gt; (based on a survey of digital marketers) and the &lt;strong&gt;&lt;a href="http://econsultancy.com/reports/email-marketing-buyers-guide"&gt;Email Marketing Platforms Buyer's Guide&lt;/a&gt;&lt;/strong&gt; (particularly relevant for the UK market). See also the &lt;strong&gt;&lt;a href="http://econsultancy.com/reports/email-marketing-statistics"&gt;Email Statistics Compendium&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;</learn-more-formatted>
  <learn-more-unformatted>&lt;p&gt;For further information about email marketing, download Econsultancy's &lt;strong&gt;&lt;a href="http://econsultancy.com/reports/email-census"&gt;Email Census&lt;/a&gt;&lt;/strong&gt; (based on a survey of digital marketers) and the &lt;strong&gt;&lt;a href="http://econsultancy.com/reports/email-marketing-buyers-guide"&gt;Email Marketing Platforms Buyer's Guide&lt;/a&gt;&lt;/strong&gt; (particularly relevant for the UK market). See also the &lt;strong&gt;&lt;a href="http://econsultancy.com/reports/email-marketing-statistics"&gt;Email Statistics Compendium&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;</learn-more-unformatted>
  <legacy-article-id type="integer">364663</legacy-article-id>
  <name>Email marketing: Keep it simple...</name>
  <private type="boolean">false</private>
  <published-at type="datetime">2007-11-28T08:30:00+00:00</published-at>
  <slug>email-marketing-keep-it-simple</slug>
  <tweetbacks-updated-at type="datetime">2009-04-30T01:00:17+01:00</tweetbacks-updated-at>
  <unpublished-at type="datetime" nil="true"></unpublished-at>
  <updated-at type="datetime">2009-10-13T09:26:04+01:00</updated-at>
  <views-count type="integer">341</views-count>
</blog-post>
