Commentary

Stephen Wellman
 

Sybase Sent 25B Mobile Messages In 2006

Mobile message enabler Sybase 365 today said it delivered a jaw-dropping 25 billion SMS and MMS messages in 2006. That's almost double from 2005. And I thought I sent a lot of text messages. What's driving all this SMS growth?

Mobile message enabler Sybase 365 today said it delivered a jaw-dropping 25 billion SMS and MMS messages in 2006. That's almost double from 2005. And I thought I sent a lot of text messages.

What's driving all this SMS growth?In the enterprise, it's employees, many of whom now rely on SMS and MMS as ways to keep in touch with their business contacts and their colleagues at the office.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Here is an example plucked straight from my work life. I just spent the last two days at the AlwaysOn confernce. While I was out of the office, I received around 15 text messages each day -- all work related. Granted, I foot the bill for this, since it's my personal cell phone. But if I was using a work phone, who would pay for these text messages? That's right, your IT/telecom budget, that's who.

If you're not already, you need to make sure your IT/telecom budget has room for SMS messaging, because I bet you have employees already texting for work (and for other things too, but that's another blog post). And don't think this is covered by your BlackBerry (or other) push email plan. When you negotiate your company's cell phone plan with your carrier, make sure you budget both in the carrier service agreement and in your internal budget for your employees' SMS usage.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links