<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" 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/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>Mobile Commons</title>
	
	<link>http://www.mobilecommons.com</link>
	<description>Connect and Measure</description>
	<pubDate>Thu, 09 Jul 2009 13:21:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/MobileCommons" type="application/rss+xml" /><item>
		<title>AFSCME adopts innovative advocacy tools and strategies</title>
		<link>http://feedproxy.google.com/~r/MobileCommons/~3/Fv3uhTBJZK0/</link>
		<comments>http://www.mobilecommons.com/blog/2009/06/afscme-adopts-innovative-advocacy-tools-and-strategies/#comments</comments>
		<pubDate>Mon, 01 Jun 2009 22:48:36 +0000</pubDate>
		<dc:creator>matt w.</dc:creator>
		
		<category><![CDATA[All Posts]]></category>

		<guid isPermaLink="false">http://www.mobilecommons.com/?p=527</guid>
		<description><![CDATA[Over the last few months, one of our savviest clients, AFSCME, has adopted new ways to engage their members using voice and mobile technology, leading the labor movement in grassroots advocacy.
Check out these examples:
Web-driven voice advocacy through the &#8220;Make America Happen&#8221; Campaign
AFSCME sends emails to their list to drive constituents to web forms for congressional [...]]]></description>
			<content:encoded><![CDATA[<p>Over the last few months, one of our savviest clients, <a href="http://www.afscme.org/">AFSCME</a>, has adopted new ways to engage their members using voice and mobile technology, leading the labor movement in grassroots advocacy.</p>
<p>Check out these examples:</p>
<p><strong>Web-driven voice advocacy through the &#8220;Make America Happen&#8221; Campaign</strong></p>
<p style="padding-left: 30px;">AFSCME sends emails to their list to drive constituents to web forms for congressional voice advocacy.</p>
<p style="padding-left: 30px;">
<dl>
<dt><img class="size-full wp-image-531 alignright" src="http://www.mobilecommons.com/wp-content/uploads/2009/06/afscme.gif" alt="Make America Happen Logo" width="279" height="232" /></dt>
</dl>
<p style="padding-left: 30px;"><strong><em>Make America Happen Campaign Results:</em></strong></p>
<p style="padding-left: 30px;">Over a two  week span when the Obama Jobs and Recovery package was being debated in Congress, AFSCME  sent out three standalone  emails that <em>generated approximately 1,000 calls to Congress in support of  the bill. </em> Additionally, AFSCME has been building their text messaging file by converting email subscribers into text subscribers as an optional check box in the web form. In the future, they will drive response via SMS.</p>
<p><strong>Advocacy at Live Events</strong></p>
<p style="padding-left: 30px;">At their recent conferences, AFSCME asked their audience to text &#8220;happen&#8221;  69866 to make calls into Congress.</p>
<p style="padding-left: 30px;">Results: They have seen response rates as high as 53%  for people in the room texting in (225  person conference, 119 opt-ins) and 42% response rates on broadcast text-to-call messages sent later that day to generate calls. (119 opt-ins, 50 calls generated)</p>
<p><strong>Targeting state legislators</strong></p>
<p style="padding-left: 30px;">AFSCME has also used mobile to target state legislators. This strategy gets their affiliates involved and targets legislators who get calls less frequently, which means the calls are typically more effective.</p>
<p>Thanks so much to Tracey Conaty, Assistant Director of Online Communications, at AFSCME for sharing the results and to our friends at the <a href="http://watershedcompany.com">Watershed Company</a> for all their hard work!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mobilecommons.com/blog/2009/06/afscme-adopts-innovative-advocacy-tools-and-strategies/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.mobilecommons.com/blog/2009/06/afscme-adopts-innovative-advocacy-tools-and-strategies/</feedburner:origLink></item>
		<item>
		<title>A “Starbucks Locator” for the Rest of Us</title>
		<link>http://feedproxy.google.com/~r/MobileCommons/~3/NLZj9n-V6Cs/</link>
		<comments>http://www.mobilecommons.com/blog/2009/05/a-starbucks-locator-for-the-rest-of-us/#comments</comments>
		<pubDate>Fri, 15 May 2009 19:49:01 +0000</pubDate>
		<dc:creator>ben</dc:creator>
		
		<category><![CDATA[All Posts]]></category>

		<guid isPermaLink="false">http://mcommons.com/?p=502</guid>
		<description><![CDATA[A couple years ago, Starbucks rolled out a popular SMS application.  Users could text their zip code to MYSBUX and they would get back the closest Starbucks location.  Google has an SMS service that lets you text in to GOOGLE and get back weather, directions, sports scores and more.  
Mobile Commons has [...]]]></description>
			<content:encoded><![CDATA[<p>A couple years ago, Starbucks rolled out a popular SMS application.  Users could text their zip code to MYSBUX and they would get back the closest Starbucks location.  Google has an SMS service that lets you text in to GOOGLE and get back weather, directions, sports scores and more.  </p>
<p>Mobile Commons has a similar application that our customers use to make their own SMS lookup services.  Organizations can quickly create a service that users can text to and get back information quickly.  For example, text &#8216;FISH SALMON&#8217; 30644 and you&#8217;ll get a response letting you know if there are any health or environmental concerns with it (courtesy of Blue Ocean Institute).  Text SHOP and the name of a company to 30644 to find out if they are LGBT friendly (courtesy of HRC).</p>
<p>We often get requests to make services based on location; in other words, a private-label Starbucks locator.  Some organizations have faked it by uploading a database of zip codes.  This works great but takes a lot of work and doesn&#8217;t handle people texting in their address.  As we mentioned a couple days ago, we&#8217;ve been working hard <a href="http://mcommons.com/blog/2009/05/location-location-location/">integrating location information into everything we do</a>.  Today we are very excited to announce that we have <b>added automatic location information to our SMS database applications</b>.  </p>
<p>How does it work?  First, you upload your database as a spreadsheet with two columns: input and output.  Check the box that says &#8220;Treat inputs as geographic locations&#8221;.  That&#8217;s it!</p>
<p>Now you can instruct people to text your keyword plus their address.  <b>We automatically find the closest geographic match and text it to you</b>.  They can text in their full address, city, zip code - it doesn&#8217;t matter.  We can handle it all.</p>
<p>This is best illustrated with an example. Let&#8217;s create a service to find the closest Mobile Commons office via SMS.  Here&#8217;s our sample CSV file:<br />
<code><br />
"input","output"<br />
"86 Chambers St, New York NY 10007","The closest Mobile Commons office is at 86 Chambers St, New York NY 10007"<br />
"100 Bush St, San Francisco CA 94104","The closest Mobile Commons office is at 100 Bush St, San Francisco CA 94104"<br />
</code></p>
<p>I copy-and-pasted the above text into our application and hit &#8220;Save&#8221;. Finally, I chose the keyword &#8220;mcommons&#8221; and added a default response. </p>
<p><em><b>Try it! Text MCOMMONS and your address to 30644 and we&#8217;ll reply with our closest office.</b></em><br />
<br />
<img src="http://mcommons.com/wp-content/uploads/2009/05/photo-2.jpg" alt="mcommons locator iphone" title="mcommons locator iphone" width="320" height="480" class="alignnone size-full wp-image-511" /></p>
<p>Now imagine you&#8217;re a retail business and you want to build a store locator.  Easy!  Just upload a spreadsheet of your store addresses in one column and your contact information in the other.  We automatically take care of the rest.  Want to advertise local events, rallies, or house parties.  No problem!  </p>
<p>It&#8217;s a &#8220;Starbucks Locator&#8221; for the rest of us!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mobilecommons.com/blog/2009/05/a-starbucks-locator-for-the-rest-of-us/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.mobilecommons.com/blog/2009/05/a-starbucks-locator-for-the-rest-of-us/</feedburner:origLink></item>
		<item>
		<title>Location, Location, Location</title>
		<link>http://feedproxy.google.com/~r/MobileCommons/~3/CjQbGEu2UG8/</link>
		<comments>http://www.mobilecommons.com/blog/2009/05/location-location-location/#comments</comments>
		<pubDate>Tue, 12 May 2009 22:11:28 +0000</pubDate>
		<dc:creator>ben</dc:creator>
		
		<category><![CDATA[All Posts]]></category>

		<guid isPermaLink="false">http://mcommons.com/?p=483</guid>
		<description><![CDATA[Over the past few months, we&#8217;ve slowly been incorporating location information to all parts of the Mobile Commons application.  Every phone &#038; profile in our database is now associated with a geographical location and location is added for all new users. (Note: we aren&#8217;t tracking users in real-time; just their address).
Locations can be as [...]]]></description>
			<content:encoded><![CDATA[<p>Over the past few months, we&#8217;ve slowly been incorporating location information to all parts of the Mobile Commons application.  Every phone &#038; profile in our database is now associated with a geographical location and location is added for all new users. (Note: we aren&#8217;t tracking users in real-time; just their address).</p>
<p>Locations can be as accurate as a home address or as general as a city, depending on the information your users share with you. For example, if someone texts in a zip code, we can figure out their city and state.  If they fill out their mailing address a web form, we&#8217;ll add it to their profile.  And of course you can manually edit any profile or import your own CRM data and we&#8217;ll use that instead.  Once we stored everyone&#8217;s location information, the next step was to find everyone&#8217;s legislators.  We went through every profile and updated their profile with their congressional district.</p>
<p>Now that the data is in place, we can start doing some really cool things:</p>
<p><strong>Advanced Group Targeting:</strong><br />
Armed with latitude, longitude and congressional district, we were able to really improve your ability to create groups of users:</p>
<ul>
<li>Reach out to people only in a certain state (e.g. only text people in California)</li>
<li>Advertise events near a particular city (e.g. text everyone within 25 miles of New York City)</li>
<li>Target specific legislators (e.g. text everyone in the NY-01 congressional district)</li>
</ul>
<p>And while we were at it, we also created some useful new group functionality for our advanced users: </p>
<ul>
<li>Create groups that contain other groups</li>
<li>Exclude people from your groups based on search criteria</li>
<li>Finer grained control of AND and OR logic</li>
</ul>
<p>For example, you can target a group that includes everyone in California but except Los Angeles and excludes an uploaded list of your major donors.</p>
<p><strong>Targeted Legislative Call Campaigns</strong><br />
Our customers have run some amazing <a href="http://mcommons.com/features/mobile-advocacy/">legislative call campaigns</a> over the past couple years, really helping to affect change in policy.  But with the addition of location information, we can now take these call campaigns to a whole new level!</p>
<p>When we first introduced <a href="http://mcommons.com/features/text-voice/">mConnect</a>, all calls were routed to the capitol switchboard and users asked to be connected to their representative.  Now that we know everyone&#8217;s representative, we can automatically route the call to the correct destination!  This eliminates the switchboard operators as a potential bottleneck and makes for a fantastic user experience.  Not only that, but your organization can see in real-time exactly which legislators were called and how the call was made — from the web, Facebook, email, or text message.</p>
<p><img src="http://mcommons.com/wp-content/uploads/2009/04/location-collage_4.png" alt="Targetet mConnect" title="Targetet mConnect" width="400" height="400" class="alignnone size-full wp-image-328" /></p>
<p>To take it a step further, we realize that organizations don&#8217;t always want a shotgun approach; they would rather target <em>specific</em> legislators.  With Advanced Targeting, you can now select particular senators to target.  This enables your organization maximize your efforts and reach exactly the legislators that you need to. </p>
<p>Got some great ideas that you&#8217;d like to see incorporated into our platform?  Feel free to leave a comment below.  Ready to get started with mobile? <a href="http://mcommons.com/about-us/">Contact us</a> or find us on Twitter <a href="http://twitter.com/mobilecommons">@mobilecommons</a>.  </p>
]]></content:encoded>
			<wfw:commentRss>http://www.mobilecommons.com/blog/2009/05/location-location-location/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.mobilecommons.com/blog/2009/05/location-location-location/</feedburner:origLink></item>
		<item>
		<title>Integrating Text Messaging with Fundraising = More Dough</title>
		<link>http://feedproxy.google.com/~r/MobileCommons/~3/sRqmttKuN30/</link>
		<comments>http://www.mobilecommons.com/blog/2009/03/integrating-text-messaging-during-year-end-fundraising-more-dough/#comments</comments>
		<pubDate>Thu, 05 Mar 2009 17:37:14 +0000</pubDate>
		<dc:creator>matt w.</dc:creator>
		
		<category><![CDATA[All Posts]]></category>

		<guid isPermaLink="false">http://mcommons.com/integrating-text-messaging-during-year-end-fundraising-more-dough</guid>
		<description><![CDATA[We spent a lot of time at the end of 2008 working with one of our clients, the Humane Society of the United States, and our friends at the Watershed Company to come up with a nice mobile test for end of year fundraising. We wanted to give mobile subscribers an option to donate over [...]]]></description>
			<content:encoded><![CDATA[<p>We spent a lot of time at the end of 2008 working with one of our clients, <a href="http://hsus.org">the Humane Society of the United States</a>, and our friends at <a href="http://watershedcompany.com">the Watershed Company</a> to come up with a nice mobile test for end of year fundraising. We wanted to give mobile subscribers an option to donate over the phone via an inbound call center after they received a text message promoting the call.</p>
<p>It didn&#8217;t quite work out the way we planned; we received no donations over the phone.</p>
<p>It did, however, produce a very interesting result&#8211;people who got the text message gave online with an <strong>increased response rate of 77%!</strong></p>
<p>We suppressed a third of their list to see if the text had any effect on online giving, and it turned out to have a huge impact.</p>
<p><a href="http://mcommons.com/media/pdf/casestudies/mcommons-hsus-fundraising.pdf">Download the Full Case Study</a> (pdf)</p>
<p>We are excited about all the different ways people are pushing mobile fundraising and we hope that this integrated approach becomes another arrow in the mobile fundraising quiver.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mobilecommons.com/blog/2009/03/integrating-text-messaging-during-year-end-fundraising-more-dough/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.mobilecommons.com/blog/2009/03/integrating-text-messaging-during-year-end-fundraising-more-dough/</feedburner:origLink></item>
		<item>
		<title>Reply “Please” to Unsubscribe?</title>
		<link>http://feedproxy.google.com/~r/MobileCommons/~3/7OkN4KG06kY/</link>
		<comments>http://www.mobilecommons.com/blog/2009/02/reply-please-to-unsubscribe/#comments</comments>
		<pubDate>Thu, 19 Feb 2009 15:39:40 +0000</pubDate>
		<dc:creator>ben</dc:creator>
		
		<category><![CDATA[All Posts]]></category>

		<category><![CDATA[algorithm]]></category>

		<category><![CDATA[mcommons]]></category>

		<category><![CDATA[mma]]></category>

		<category><![CDATA[mobile]]></category>

		<category><![CDATA[mobile commons]]></category>

		<category><![CDATA[sms]]></category>

		<category><![CDATA[stop]]></category>

		<category><![CDATA[text messaging]]></category>

		<category><![CDATA[user experience]]></category>

		<guid isPermaLink="false">http://mcommons.com/reply-please-to-unsubscribe</guid>
		<description><![CDATA[Last week, we wrote a blog post discussing SMS signatures and doing some analysis to see how common they are.  This week, we decided to continue with the theme of text message processing and analyze opt-out requests.
Background
According to the Mobile Marketing Association&#8217;s best practices, text messaging providers are required to look for special opt-out keywords [...]]]></description>
			<content:encoded><![CDATA[<p>Last week, we wrote a blog post discussing <a href="http://mcommons.com/text-message-signatures">SMS signatures and doing some analysis to see how common they are</a>.  This week, we decided to continue with the theme of text message processing and analyze opt-out requests.</p>
<p><strong>Background</strong><br />
According to the Mobile Marketing Association&#8217;s best practices, text messaging providers are required to look for special opt-out keywords and automatically unsubscribe users who text them in.  The published list of opt-out words are <em>STOP, END, CANCEL, UNSUBSCRIBE </em>or<em> QUIT</em>.  Our customers are all required to include opt-out instructions (e.g. &#8220;reply STOP to unsubscribe&#8221;) in their first interaction with end-users and encouraged to include instructions on subsequent messaging whenever possible.</p>
<p>Perhaps due to the conversational nature of many of our customers&#8217; programs, people often don&#8217;t realize that their messages are initially processed by an algorithm. As such, many people do not reply with carrier-recommended opt-out keywords, but rather ask to opt-out in plain English (&#8221;Please remove me from your list. Thanks!&#8221;).</p>
<p>Early on, we realized that for the best possible user experience, we needed a way for organizations to opt-out users who send in plain English responses.  The Mobile Commons platform provides an SMS Inbox that our customers can use to view all their incoming messages.  We added an &#8220;Opt Out&#8221; button to the Inbox, allowing our customers to read incoming messages and opt-out users as needed.<br />
<span id="more-88"></span></p>
<p>Over the past two years, we&#8217;ve accumulated a ton of data about users&#8217; mobile behavior.  Specifically, by analyzing the list of manual opt-outs, we are able to determine the most common words and phrases that people use to opt-out that aren&#8217;t recommended by the carriers.</p>
<p><strong>Experiment</strong><br />
We pulled 50,000 random, anonymous  text messages from our database from the past year that included both automated and manual opt-outs.  We then did a frequency analysis of the bodies of the messages to determine which words and phrases were the most common.</p>
<p><strong>Results</strong><br />
As expected, STOP by itself is by far the most prevalent opt-out word, accounting for 80.4% of all opt-outs.  The word STOP followed by more text (SMS signatures or an entire phrase) was the second most popular, with 9.3% of all opt-outs.  In total, incoming messages starting with the word STOP represented 89.7% of all opt-outs!</p>
<p>The requisite carrier opt-out words rank as follows:</p>
<ul>
<li>STOP: 89.7%</li>
<li>CANCEL: 1.0%</li>
<li>END: 0.8%</li>
<li>UNSUBSCRIBE: 0.7%</li>
<li>QUIT: 0.1%</li>
</ul>
<p>92% is obviously a huge percentage and almost all opt-outs can be captured just by checking for these words at the beginning of a message!</p>
<p>This still leaves about 8% of all opt-out requests going unprocessed.  <strong>For systems like ours that process millions of text messages, 8% represents a huge number of people who would like to stop receiving text messages but are confused about the exact procedure to follow.  </strong>At Mobile Commons, we strongly believe that mobile is a highly valued communication medium and we should go the extra mile to make the best possible end-user experience.  <strong>Keeping mobile communication spam-free and nuisance-free is critical to our success!</strong></p>
<p>As with all good algorithm design, we began by analyzing the thousands of messages in our database.  This would allow us to write regression tests using real-life messages.  We&#8217;d like to share some of our findings with you.</p>
<p>Much to our surprise, the word or phrase that started the majority of the non-standard opt-outs was PLEASE, as in &#8220;please stop&#8221;, &#8220;please remove me&#8221;, or &#8220;please only send emails. texts cost money.&#8221;  It&#8217;s nice to know people out there are still polite!</p>
<p>The following table represents the percentages of the most common words that are <em>not</em> part of the Mobile Marketing Association required list but resulted in an opt-out:</p>
<ul>
<li>PLEASE: 21.7%</li>
<li>STOP2: 8.3%</li>
<li>REMOVE: 7.9%</li>
<li>F*CK: 4.6%</li>
<li>TAKE ME OFF: 2.4%</li>
<li>DO NOT: 2.9%</li>
</ul>
<p>Just to be clear, we do not mean to imply that every message beginning with a &#8220;please&#8221; should be an opt-out.  In fact, the majority of them are <em>not</em> opt-outs. It means that <strong>of the opt-out messages that do not use standard opt-out words, 21.7% of them began with the word &#8220;please&#8221;</strong>.</p>
<p>The word STOP2 was somewhat surprising, but after further investigation, we realized it was a very common response to the often used phrase: &#8220;Rply STOP 2 opt-out.&#8221;</p>
<p><strong>Conclusion:</strong><br />
Over the past year, we&#8217;ve worked very hard on our message processing algorithms.  The algorithms often go unnoticed by end users and customers - after all, it&#8217;s pretty tough to see an algorithm =)</p>
<p>We have a number of goals with our message processing:</p>
<ul>
<li>Correctly identify the incoming messages, whether they be opt-ins, opt-outs, help requests, replies, phone call requests, search queries, donation, and more</li>
<li>Automate as much as possible, reducing the amount of extra work and manual intervention our customers need to do to keep their campaigns running smoothly &amp; their lists clean</li>
<li>Keep the number of false positives as low as possible (accidentally opting-out a user is a terrible thing to do!)</li>
</ul>
<p>Our engineers have done a great job of all three, including processing opt-outs.  We automatically catch an extremely high percentage of them correctly with almost no false positives.  This makes for a great user experience:  a &#8220;Please take me off your list&#8221; text message will be followed by an immediate &#8220;You have been removed. Thanks for your support&#8221; response (as opposed to the &#8220;Unknown keyword. Try again.&#8221; response you often find on shared short code services).</p>
<p>Of course, our job is never complete. We continue to update our algorithms as we learn more and more about user behavior and our natural language processing improves.  We&#8217;ll keep you updated on our blog!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mobilecommons.com/blog/2009/02/reply-please-to-unsubscribe/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.mobilecommons.com/blog/2009/02/reply-please-to-unsubscribe/</feedburner:origLink></item>
		<item>
		<title>Text Message Signatures</title>
		<link>http://feedproxy.google.com/~r/MobileCommons/~3/1QENakvB-Yw/</link>
		<comments>http://www.mobilecommons.com/blog/2009/02/text-message-signatures/#comments</comments>
		<pubDate>Sun, 15 Feb 2009 23:10:23 +0000</pubDate>
		<dc:creator>ben</dc:creator>
		
		<category><![CDATA[All Posts]]></category>

		<category><![CDATA[algorithm]]></category>

		<category><![CDATA[mcommons]]></category>

		<category><![CDATA[mobile commons]]></category>

		<category><![CDATA[signature]]></category>

		<category><![CDATA[sms]]></category>

		<guid isPermaLink="false">http://mcommons.com/text-message-signatures</guid>
		<description><![CDATA[SMS Signature Overview 
Maybe you&#8217;ve seen them before.  Every single text message you get from one of your friends ends with &#8220;&#60;3 Stacee&#8221; or &#8220;Hugs&#38;Kisses&#8221;.  It&#8217;s called a text messages signature. They are just like email signatures; users setup their phones to automatically insert a message at the end of every text message.  This can [...]]]></description>
			<content:encoded><![CDATA[<p><strong>SMS Signature Overview </strong></p>
<p>Maybe you&#8217;ve seen them before.  Every single text message you get from one of your friends ends with &#8220;&lt;3 Stacee&#8221; or &#8220;Hugs&amp;Kisses&#8221;.  It&#8217;s called a text messages signature. They are just like email signatures; users setup their phones to automatically insert a message at the end of every text message.  This can be your name, a short phrase, or anything else you like, and are very common on newer phone models.</p>
<p>For example, I could setup my phone so that every message I send ends with &#8220;-=Ben=-&#8221; so people know it&#8217;s from me: &#8220;I&#8217;ll meet you at the coffee shop at 3pm -=Ben=-&#8221;  If you&#8217;ve seen these before, you know exactly what I&#8217;m talking about.  If you haven&#8217;t you probably think it&#8217;s crazy that someone would fill up part of their precious 160 characters with a signature!</p>
<p>Over the past year, we&#8217;ve processed millions of text messages.  We&#8217;ve seen all sorts of different SMS signatures and unexpected user behavior and we want to share some of our data.  Specifically, we wanted to understand how prevalent are SMS signatures and what can do to improve our text message processing algorithms.<br />
<span id="more-87"></span><br />
<strong>Experiment Setup</strong></p>
<p>First we chose a single keyword that we knew was actively promoted.  We then extracted 6,000 unique text messages start started with keyword in the past year.  Next we removed all duplicate messages so we only had a single message for each phone.  Then we removed multiple different messages for each giving phone; it turns out that people change their signatures more than you think (some change them weekly)!  Finally, we manually went through the list and discounted any extraneous messages that were obviously manually typed and clearly not a signature.  Ambiguous messages were also removed from the list.  This left 5,242 unique text messages to analyze.</p>
<p>(To protect the privacy of our customers and users, we are unable to publish the list of signatures, but we are able to share aggregate results with you.)</p>
<p><strong>Results</strong></p>
<ul>
<li>647 users out of 5,242 had SMS signatures, or 12.34% of users</li>
<li>The average signature length is 11 characters</li>
<li>The longest signature was a whopping 91 characters!</li>
<li>513 signatures, or 79% of them, had punctuation or other non-alphanumeric characters in them</li>
<li>13.8% of all signatures contain a heart &lt;3 and 7.7% contain a smile =)</li>
</ul>
<p>We were also curious if SMS signatures varied by demographic.  We repeated our analysis for a known audience that was significantly older than the average.  We do not know (nor could we share) the exact ages of users, so let&#8217;s just define the term &#8216;older&#8217; to mean exclusively adults, as opposed to teenagers or college students.  In this case, only 18 out of 414, or 4.3% of adults use SMS signatures, compared with 12.3% above.</p>
<p><strong>Challenges</strong></p>
<p>By now you have probably guessed why this is such a significant topic for Mobile Commons.  SMS signatures might be fun when texting your friends, but they post a significant technological challenge for companies like ours.  Our products are built around recognizing keywords for opting in and search terms for querying data while on the go.  How can we reliably parse keywords and queries when messages have seemingly random text added to them?!</p>
<p>This is best illustrated with an example:  Consider FishPhone, an SMS service that lets you text FISH and the name of a fish to 30644 and get back the health and environmental impact of that species.  For example, &#8220;fish halibut&#8221; tells you the environmental impact of halibut.  But what happens if the text message reads &#8220;fish halibut peace,&lt;3,and :)&#8221;?  Or &#8220;fish atlantic salmon xoxobaby girlxoxo&#8221;?  How can we tell what you&#8217;re searching for? It gets even harder when you allow multi-word keywords (e.g. You can text WHERE IS and a bottle water brand to 69866 to find out how far away your water&#8217;s source is).</p>
<p>This is a great example of a real world problem.  You can write the best algorithms in the world for parsing text messages, but until you start processing live user data, you have no idea what you&#8217;re likely to encounter or how wrong your assumptions were.  Unfortunately I can&#8217;t reveal  our algorithms (that&#8217;s part of our secret sauce), but I can say that they have evolved tremendously over the past couple years.</p>
<p><strong>Conclusion</strong></p>
<p>In message processing systems that only rely on a single keyword, SMS signatures aren&#8217;t really a problem; your system can just grab the first word.  When you start allowing multi-word keywords (e.g. text &#8220;do something&#8221; to 30644), keywords with search terms, or data collection (text your email address and zip code), signatures become quite difficult to deal with.  We&#8217;re quite proud of the natural language processing algorithms we&#8217;ve written over the past two years to elegantly handle these sorts of real-world challenges.  We constantly tweak our algorithms and run regression tests to ensure we have the most sophisticated and accurate text messaging processing product available!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mobilecommons.com/blog/2009/02/text-message-signatures/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.mobilecommons.com/blog/2009/02/text-message-signatures/</feedburner:origLink></item>
		<item>
		<title>Dane Grams of HRC on their Mobile Successes</title>
		<link>http://feedproxy.google.com/~r/MobileCommons/~3/0GXZCNHRbJ4/</link>
		<comments>http://www.mobilecommons.com/blog/2009/02/dane-grams-of-hrc-on-their-mobile-successes/#comments</comments>
		<pubDate>Wed, 04 Feb 2009 10:53:20 +0000</pubDate>
		<dc:creator>cm</dc:creator>
		
		<category><![CDATA[All Posts]]></category>

		<guid isPermaLink="false">http://mcommons.com/dane-grams-of-hrc-on-their-mobile-successes</guid>
		<description><![CDATA[&#8220;You have one cell phone number and generally it does stay with you forever. A lot of folks on our file at HRC have 3, 4, 5 email addresses and it gets really complicated to match them and figure out who they all are, but they only have one cellphone.&#8221; - Dane Grams, HRC
&#160;
Dane Grams [...]]]></description>
			<content:encoded><![CDATA[<p><span class="bigquote">&#8220;You have one cell phone number and generally it does stay with you forever. A lot of folks on our file at HRC have 3, 4, 5 email addresses and it gets really complicated to match them and figure out who they all are, but they only have one cellphone.&#8221; - Dane Grams, <a href="http://www.hrcactioncenter.org/actioncenter/txtsignup.html">HRC</a></span><br />
<br />&nbsp;</p>
<p>Dane Grams of HRC gave a presentation at the <a href="http://www.the-dma.org/conferences/dmanonprofitdc/index.shtml">DMA 2009 Washington Nonprofit Conference</a> session titled &#8220;New Media Channels — Adding Text Messaging, Social Networks and Media to the Marketing Mix&#8221; last Friday. Also on the panel were Scott Goodstein from the Obama campaign and Grace Markarian of the Humane Society (HSUS). We&#8217;ve embedded the full 8-minute video below.</p>
<p><object width="425" height="344"><param name="movie" value="http://www.youtube.com/v/k25aG6ma9is&#038;color1=0xb1b1b1&#038;color2=0xcfcfcf&#038;hl=en&#038;feature=player_embedded&#038;fs=1"></param><param name="allowFullScreen" value="true"></param><embed src="http://www.youtube.com/v/k25aG6ma9is&#038;color1=0xb1b1b1&#038;color2=0xcfcfcf&#038;hl=en&#038;feature=player_embedded&#038;fs=1" type="application/x-shockwave-flash" allowfullscreen="true" width="425" height="344"></embed></object></p>
<p>One of the main points that Dane addresses is that organizations have causes that matter and can run highly effective campaigns even though they don&#8217;t have Obama as their figurehead. At Mobile Commons, we&#8217;ve seen proof of this again and again as we see people use our tools to spread causes and ideas they care about (and now we&#8217;ve made that even easier by tying into Facebook and Twitter). Dane and Grace have both had great successes with Mobile Commons and Convio eCRM integration and will continue to because they&#8217;ve embraced mobile as an ongoing part of their communications and are constantly looking for ways to engage more deeply with their constituents.</p>
<p>Thanks to <a href="http://www.connectioncafe.com/posts/2009/february/will-mobile-really-move.html">Tad at Convio</a> for posting the great video.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mobilecommons.com/blog/2009/02/dane-grams-of-hrc-on-their-mobile-successes/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.mobilecommons.com/blog/2009/02/dane-grams-of-hrc-on-their-mobile-successes/</feedburner:origLink></item>
		<item>
		<title>Twitter &amp; Facebook Integration</title>
		<link>http://feedproxy.google.com/~r/MobileCommons/~3/096mufNDwO8/</link>
		<comments>http://www.mobilecommons.com/blog/2009/01/twitter-facebook-integration/#comments</comments>
		<pubDate>Thu, 29 Jan 2009 22:52:51 +0000</pubDate>
		<dc:creator>ben</dc:creator>
		
		<category><![CDATA[All Posts]]></category>

		<category><![CDATA[facebook]]></category>

		<category><![CDATA[mcommons]]></category>

		<category><![CDATA[mobile commons]]></category>

		<category><![CDATA[sms]]></category>

		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://mcommons.com/twitter-facebook-integration</guid>
		<description><![CDATA[Our goal at Mobile Commons has always been to provide our customers with the best tools to run the most successful mobile campaigns. Today we&#8217;re pleased to announce both Twitter and Facebook integration into the Mobile Commons platform!
Twitter has had phenomenal growth over the past year and organizations have been very quick to embrace Twitter [...]]]></description>
			<content:encoded><![CDATA[<p>Our goal at Mobile Commons has always been to provide our customers with the best tools to run the most successful mobile campaigns. Today we&#8217;re pleased to announce both Twitter and Facebook integration into the Mobile Commons platform!</p>
<p>Twitter has had phenomenal growth over the past year and <a href="http://beth.typepad.com/beths_blog/2008/12/social-media-research-snippets-state-of-the-twittersphere-q4-whats-does-it-mean-for-nonprofits.html" target="_blank">organizations have been very quick to embrace Twitter as part of their media strategy</a>.  In addition to mobile, many of our customers also use Twitter as a way of communicating.  To integrate with Twitter, click the &#8216;Setup&#8217; tab in your Mobile Commons account and enter your Twitter login information.  Once you do this, a new &#8220;Send to Twitter&#8221; checkbox will appear as an option whenever you schedule a broadcast.  If you check the box, your message will simultaneously be posted to Twitter as well as to your mobile list!</p>
<p><img src="http://mcommons.com/images/twitter_mcommons.png" width="293" height="99" /></p>
<p>The popularity of Facebook goes without saying.  We&#8217;ve had Facebook apps available in beta for a while and they officially launched this week!  We&#8217;ve gotten great feedback as customers have used our Facebook apps to collect mobile donations, trigger calls to the White House, and get supporters to join their mobile lists.  Facebook integration really is incredible and deserves it&#8217;s own blog post which is coming soon.  If you have any questions or would like advice on getting started with Facebook, please don&#8217;t hesitate to contact us.  We&#8217;ll be happy to help!</p>
<p>These new features are part of a larger trend we&#8217;re seeing based on connecting mobile technology to the web.  Many of our tools have had web components for a long time:  Mobile donations and phone calls can be triggered by filling out a web form.  mData databases can be queried from a Flash widget.  mCast text-to-screen apps can shown anywhere on the web.  We&#8217;ve been working hard to expand beyond static sites and really connect you with the social graph.  With our Facebook and Twitter integration, we continue to lead the way helping organizations spread their ideas, extend their reach, and accomplish their goals!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mobilecommons.com/blog/2009/01/twitter-facebook-integration/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.mobilecommons.com/blog/2009/01/twitter-facebook-integration/</feedburner:origLink></item>
		<item>
		<title>New Java Library for Mobile Commons API</title>
		<link>http://feedproxy.google.com/~r/MobileCommons/~3/mnHNA-4ATfA/</link>
		<comments>http://www.mobilecommons.com/blog/2009/01/new-java-library-for-mobile-commons-api/#comments</comments>
		<pubDate>Mon, 19 Jan 2009 23:36:07 +0000</pubDate>
		<dc:creator>ben</dc:creator>
		
		<category><![CDATA[All Posts]]></category>

		<category><![CDATA[api]]></category>

		<category><![CDATA[java]]></category>

		<category><![CDATA[mcommons]]></category>

		<category><![CDATA[mobile commons]]></category>

		<category><![CDATA[opensource]]></category>

		<guid isPermaLink="false">http://mcommons.com/new-java-library-for-mobile-commons-api</guid>
		<description><![CDATA[Mobile Commons exposes a lot of its functionality through a really simple REST API.  Our customers have built lots of innovative applications on top of our platform, extending our functionality in ways we&#8217;ve never even thought of!
Jeff, our intern from this past summer, wanted to hack away on an open-source project over his winter break.  [...]]]></description>
			<content:encoded><![CDATA[<p>Mobile Commons exposes a lot of its functionality through a <a href="http://mcommons.com/developers/mobile-commons-rest-api">really simple REST API</a>.  Our customers have built lots of innovative applications on top of our platform, extending our functionality in ways we&#8217;ve never even thought of!</p>
<p>Jeff, our intern from this past summer, wanted to hack away on an open-source project over his winter break.  He created a <a href="http://github.com/mcommons/mcommons4j">Java library for the Mobile Commons API</a>.  It&#8217;s released under the MIT License, so you can feel free to use it in your own applications.  Libraries like this one really lower the barrier-to-entry for developers looking to integrate SMS and voice into their Java applications.</p>
<p>Are you interested in contributing to the open-source community?  If you have used our API in the past and want to release your code, let us know.  Just email us at developers@mcommons.com and we&#8217;ll showcase you and your work on our site!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mobilecommons.com/blog/2009/01/new-java-library-for-mobile-commons-api/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.mobilecommons.com/blog/2009/01/new-java-library-for-mobile-commons-api/</feedburner:origLink></item>
		<item>
		<title>Introducing “Mobile Giving Insider”</title>
		<link>http://feedproxy.google.com/~r/MobileCommons/~3/NF2-WK5_Heg/</link>
		<comments>http://www.mobilecommons.com/blog/2009/01/introducing-mobile-giving-insider/#comments</comments>
		<pubDate>Thu, 15 Jan 2009 23:25:43 +0000</pubDate>
		<dc:creator>ben</dc:creator>
		
		<category><![CDATA[All Posts]]></category>

		<guid isPermaLink="false">http://mcommons.com/introducing-mobile-giving-insider</guid>
		<description><![CDATA[At Mobile Commons, we are obviously very excited about the growing popularity of mobile donations and thrilled at how many organizations are embracing mobile technology.
We get tons of questions about mobile giving, how it works, and what is required to get started.  We&#8217;ve quickly realized that there is a lack of useful information currently available [...]]]></description>
			<content:encoded><![CDATA[<p>At Mobile Commons, we are obviously very excited about the growing popularity of mobile donations and thrilled at how many organizations are embracing mobile technology.</p>
<p>We get tons of questions about mobile giving, how it works, and what is required to get started.  We&#8217;ve quickly realized that there is a lack of useful information currently available on the web for organizations trying to learn.  A Google search for &#8220;mobile giving&#8221; currently returns links to the Mobile Giving Foundation, a year-old article on Mobile Active, and a 6-month-old article from about.com.</p>
<p>We couldn&#8217;t find very many useful sites with case studies, new campaigns, strategy tips, or other information about mobile giving.  We (and other vendors) certainly have lots information on our own company web sites, but that&#8217;s probably not the best place to showcase all the exciting things happening around mobile giving.</p>
<p>So today we&#8217;re proud to announce that Mobile Commons is sponsoring a new blog called <a href="http://mobilegivinginsider.com">Mobile Giving Insider</a>.  The site provides useful information about mobile giving, resources for nonprofits (e.g. vendors, technical documentation, etc), and a detailed FAQ.  Additionally, it will be a blog with original reporting, highlights about exciting new campaigns that non-profits are launching, and informative case studies. We really hope this becomes a little community where lots of people can contribute, cross-post, and add your own original content.</p>
<p>The site is now up and running at <a href="http://mobilegivinginsider.com">http://mobilegivinginsider.com</a> and you can subscribe to the RSS feed at <a href="http://feeds.feedburner.com/MobileGivingInsider">http://feeds.feedburner.com/MobileGivingInsider</a>.</p>
<p>Have any interesting news or case studies that you&#8217;d like to share or promote? Please email the editors at <a href="mailto:tips@mobilegivinginsider.com">tips@mobilegivinginsider.com</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mobilecommons.com/blog/2009/01/introducing-mobile-giving-insider/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.mobilecommons.com/blog/2009/01/introducing-mobile-giving-insider/</feedburner:origLink></item>
	</channel>
</rss>
