<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Part two: the business of SMS Couponing</title>
	<atom:link href="http://blog.jwegener.com/2009/06/25/part-two-the-business-of-sms-couponing/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jwegener.com/2009/06/25/part-two-the-business-of-sms-couponing/</link>
	<description>Jonathan Wegener's Technology/Marketing Blog</description>
	<lastBuildDate>Fri, 12 Feb 2010 22:34:04 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jonathan Wegener</title>
		<link>http://blog.jwegener.com/2009/06/25/part-two-the-business-of-sms-couponing/comment-page-1/#comment-436</link>
		<dc:creator>Jonathan Wegener</dc:creator>
		<pubDate>Mon, 26 Oct 2009 20:47:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jwegener.com/?p=382#comment-436</guid>
		<description>What you&#039;re missing is how to get anyone to care.  How do you get couponees to your site?  How do you get couponers to your site?  Without a significant number of both there&#039;s no value to the site -- getting over that critical mass hump would be brutal and take significant upfront investment in marketing efforts.</description>
		<content:encoded><![CDATA[<p>What you&#39;re missing is how to get anyone to care.  How do you get couponees to your site?  How do you get couponers to your site?  Without a significant number of both there&#39;s no value to the site &#8212; getting over that critical mass hump would be brutal and take significant upfront investment in marketing efforts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jackson Stout</title>
		<link>http://blog.jwegener.com/2009/06/25/part-two-the-business-of-sms-couponing/comment-page-1/#comment-160</link>
		<dc:creator>Jackson Stout</dc:creator>
		<pubDate>Mon, 03 Aug 2009 22:18:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jwegener.com/?p=382#comment-160</guid>
		<description>What about a service that connects businesses (couponers) and couponees.   You provide an interface for both couponers and couponees to sign up.  Couponers send their coupon to their couponees through your site and pay per sms?   &lt;br&gt;&lt;br&gt;I&#039;m sure there is someone doing this - basically aweber for sms.  Surely seems like it scales.&lt;br&gt;&lt;br&gt;What am I missing?   Thanks.</description>
		<content:encoded><![CDATA[<p>What about a service that connects businesses (couponers) and couponees.   You provide an interface for both couponers and couponees to sign up.  Couponers send their coupon to their couponees through your site and pay per sms?   </p>
<p>I&#39;m sure there is someone doing this &#8211; basically aweber for sms.  Surely seems like it scales.</p>
<p>What am I missing?   Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Wegener</title>
		<link>http://blog.jwegener.com/2009/06/25/part-two-the-business-of-sms-couponing/comment-page-1/#comment-150</link>
		<dc:creator>Jonathan Wegener</dc:creator>
		<pubDate>Fri, 26 Jun 2009 16:16:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jwegener.com/?p=382#comment-150</guid>
		<description>But could you build a scalable business on the back of it?</description>
		<content:encoded><![CDATA[<p>But could you build a scalable business on the back of it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ashish</title>
		<link>http://blog.jwegener.com/2009/06/25/part-two-the-business-of-sms-couponing/comment-page-1/#comment-149</link>
		<dc:creator>Ashish</dc:creator>
		<pubDate>Fri, 26 Jun 2009 12:50:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jwegener.com/?p=382#comment-149</guid>
		<description>Why not use TextMarks.com? The user experience is a tad clunkier than email or using your own shortcode, but it&#039;s free.</description>
		<content:encoded><![CDATA[<p>Why not use TextMarks.com? The user experience is a tad clunkier than email or using your own shortcode, but it&#39;s free.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron Gejman</title>
		<link>http://blog.jwegener.com/2009/06/25/part-two-the-business-of-sms-couponing/comment-page-1/#comment-148</link>
		<dc:creator>Ron Gejman</dc:creator>
		<pubDate>Thu, 25 Jun 2009 20:13:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jwegener.com/?p=382#comment-148</guid>
		<description>Interesting. I wasn&#039;t running into any limits on AT&amp;T and Verizon on my (albeit limited) reminders sent from &lt;a href=&quot;http://www.proddr.com&quot; rel=&quot;nofollow&quot;&gt;http://www.proddr.com&lt;/a&gt; (not currently working - I&#039;ve stopped developing it).</description>
		<content:encoded><![CDATA[<p>Interesting. I wasn&#39;t running into any limits on AT&#038;T and Verizon on my (albeit limited) reminders sent from <a href="http://www.proddr.com" rel="nofollow">http://www.proddr.com</a> (not currently working &#8211; I&#39;ve stopped developing it).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Wegener</title>
		<link>http://blog.jwegener.com/2009/06/25/part-two-the-business-of-sms-couponing/comment-page-1/#comment-147</link>
		<dc:creator>Jonathan Wegener</dc:creator>
		<pubDate>Thu, 25 Jun 2009 20:11:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jwegener.com/?p=382#comment-147</guid>
		<description>Hey Ron,&lt;br&gt;I found that the SMS &lt;-&gt; Email worked well the first time you send an email.  But that&#039;s it.  A second email attempt would be delayed for hours or days.  So if there was an upper limit, it seemed to be about, well, one.&lt;br&gt;&lt;br&gt;Either way, we&#039;re talking about a hack, not a true scalable solution.  You can&#039;t build a VC-backed company on a technology hack like this.&lt;br&gt;&lt;br&gt;One thing I find really interesting is companies using push notification on the iPhone as a way of getting around SMS fees:  &lt;a href=&quot;http://www.businessinsider.com/aols-aim-iphone-app-is-getting-awesome-disruptive-to-att-2009-6&quot; rel=&quot;nofollow&quot;&gt;http://www.businessinsider.com/aols-aim-iphone-...&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Hey Ron,<br />I found that the SMS &lt;-&gt; Email worked well the first time you send an email.  But that&#39;s it.  A second email attempt would be delayed for hours or days.  So if there was an upper limit, it seemed to be about, well, one.</p>
<p>Either way, we&#39;re talking about a hack, not a true scalable solution.  You can&#39;t build a VC-backed company on a technology hack like this.</p>
<p>One thing I find really interesting is companies using push notification on the iPhone as a way of getting around SMS fees:  <a href="http://www.businessinsider.com/aols-aim-iphone-app-is-getting-awesome-disruptive-to-att-2009-6" rel="nofollow"></a><a href="http://www.businessinsider.com/aols-aim-iphone-.." rel="nofollow">http://www.businessinsider.com/aols-aim-iphone-..</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron Gejman</title>
		<link>http://blog.jwegener.com/2009/06/25/part-two-the-business-of-sms-couponing/comment-page-1/#comment-146</link>
		<dc:creator>Ron Gejman</dc:creator>
		<pubDate>Thu, 25 Jun 2009 20:11:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jwegener.com/?p=382#comment-146</guid>
		<description>Ah, so the way you solve that problem is to only email your users from an email address that is traceable. By this I mean, say you need to SMS a user with user ID 10535. You SMS them from &lt;a href=&quot;mailto:user-10535@yourdomain.com&quot; rel=&quot;nofollow&quot;&gt;user-10535@yourdomain.com&lt;/a&gt;. When they SMS or email you back, the email will go to &lt;a href=&quot;mailto:user-10535@yourdomain.com&quot; rel=&quot;nofollow&quot;&gt;user-10535@yourdomain.com&lt;/a&gt; and you can see exactly who the user was.</description>
		<content:encoded><![CDATA[<p>Ah, so the way you solve that problem is to only email your users from an email address that is traceable. By this I mean, say you need to SMS a user with user ID 10535. You SMS them from <a href="mailto:user-10535@yourdomain.com" rel="nofollow">user-10535@yourdomain.com</a>. When they SMS or email you back, the email will go to <a href="mailto:user-10535@yourdomain.com" rel="nofollow">user-10535@yourdomain.com</a> and you can see exactly who the user was.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Wegener</title>
		<link>http://blog.jwegener.com/2009/06/25/part-two-the-business-of-sms-couponing/comment-page-1/#comment-145</link>
		<dc:creator>Jonathan Wegener</dc:creator>
		<pubDate>Thu, 25 Jun 2009 20:06:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jwegener.com/?p=382#comment-145</guid>
		<description>Thanks for the comment Ramsey.  I didn&#039;t have any issues with figuring out the carrier because I just used teleflip.  Ie you can email any number at &lt;a href=&quot;http://teleflip.com&quot; rel=&quot;nofollow&quot;&gt;teleflip.com&lt;/a&gt; and it routes it correctly (not sure if they&#039;re still in business: &lt;a href=&quot;http://gigaom.com/2008/08/12/teleflip-has-flipped-for-good/&quot; rel=&quot;nofollow&quot;&gt;http://gigaom.com/2008/08/12/teleflip-has-flipp...&lt;/a&gt; ).  There was an issue the other way though -- emails from users would have rather random email addresses that often didn&#039;t contain their phone numbers in them.  So it was hard to match up with the existing users in the database.&lt;br&gt;&lt;br&gt;Interesting idea of using college students/interns.  In-person sales is one of the few things that can&#039;t be offshored cheaply.  But using interns...now we&#039;re onto something!</description>
		<content:encoded><![CDATA[<p>Thanks for the comment Ramsey.  I didn&#39;t have any issues with figuring out the carrier because I just used teleflip.  Ie you can email any number at <a href="http://teleflip.com" rel="nofollow">teleflip.com</a> and it routes it correctly (not sure if they&#39;re still in business: <a href="http://gigaom.com/2008/08/12/teleflip-has-flipped-for-good/" rel="nofollow"></a><a href="http://gigaom.com/2008/08/12/teleflip-has-flipp.." rel="nofollow">http://gigaom.com/2008/08/12/teleflip-has-flipp..</a>. ).  There was an issue the other way though &#8212; emails from users would have rather random email addresses that often didn&#39;t contain their phone numbers in them.  So it was hard to match up with the existing users in the database.</p>
<p>Interesting idea of using college students/interns.  In-person sales is one of the few things that can&#39;t be offshored cheaply.  But using interns&#8230;now we&#39;re onto something!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron Gejman</title>
		<link>http://blog.jwegener.com/2009/06/25/part-two-the-business-of-sms-couponing/comment-page-1/#comment-144</link>
		<dc:creator>Ron Gejman</dc:creator>
		<pubDate>Thu, 25 Jun 2009 20:01:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jwegener.com/?p=382#comment-144</guid>
		<description>But actually, that&#039;s not even necessary: &lt;a href=&quot;http://www.seabreezecomputers.com/tips/phone.htm&quot; rel=&quot;nofollow&quot;&gt;http://www.seabreezecomputers.com/tips/phone.htm&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>But actually, that&#39;s not even necessary: <a href="http://www.seabreezecomputers.com/tips/phone.htm" rel="nofollow">http://www.seabreezecomputers.com/tips/phone.htm</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron Gejman</title>
		<link>http://blog.jwegener.com/2009/06/25/part-two-the-business-of-sms-couponing/comment-page-1/#comment-143</link>
		<dc:creator>Ron Gejman</dc:creator>
		<pubDate>Thu, 25 Jun 2009 19:40:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jwegener.com/?p=382#comment-143</guid>
		<description>Ah, I had the benefit of being able to ask my users who their provider was.</description>
		<content:encoded><![CDATA[<p>Ah, I had the benefit of being able to ask my users who their provider was.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
