WhatsApp for business? How international organizations are getting in on mobile messaging

Originally posted on VentureBeat

Although it had not received much attention until recently, the global mobile messaging space has long been a high-growth, high-value space. After last month’s $19 billion acquisition of WhatsApp by Facebook, it’s undeniable.

With a 55-person team ($345 million per employee), 450 million users ($42.20 per user) and $20 million in annual revenue (950x revenue), WhatsApp’s acquisition has been feverishly sensationalized, debated, and analyzed worldwide.

So what made WhatsApp so incredibly valuable, and what does it mean for the mobile messaging space?

The WhatsApp deal demonstrates the importance of connectivity by means other than the Internet: The use of text messaging on mobile phones. WhatsApp pioneered a non-paternalistic international approach that facilitated easier connectivity in the developing world. And finally, WhatsApp’s focus has been on personal use, allowing the company to rapidly gain momentum. Together with an advertisement-free experience, WhatsApp created a perfect storm that led to its incredible success.

The question on everyone’s lips: What’s the business model? After all, it’s “business use” that has a history of proving the long-term sustainability of technologies and offering new ways of generating scalable revenue. No doubt businesses, organizations and communities in emerging markets would find value in connecting with constituents, customers, and partners on mobile devices.

But before we talk about businesses using mobile messaging, let’s examine the role of connectivity and how people can access the Internet and other digital services. It’s here where we see the beginning of the divergence between corporate uses and personal uses for mobile messaging technology.

Mark Zuckerberg recently explained how WhatsApp aligns with his and Facebook’s vision to connect the world. He pointed out that only a third of the globe’s population is currently connected to the Internet. He stressed the importance of increasing worldwide Internet connectivity, and noted that emerging market connectivity (such as, places like Africa, Southeast Asia, Latin America, the Middle East and rural and disaffected communities around the world) could bring and improve essential services in areas such as healthcare, education, and financial systems.

But “connectivity” means different things to different markets. For most of the world, connectivity means a basic mobile phone, not an Internet-connected device as it does in the U.S. and Europe. While 2.7 billion people may have internet connectivity, an estimated 4.5 billion people in the world have at least one active mobile device, meaning that mobile messaging is accessible to the majority of the world in a way that many other internet services are not.


Indeed, mobile messaging has become second nature to billions, particularly in the developing world where it is the primary form of electronic communication.

At the same time, non-Western technological adoption has progressed in a non-linear way, offering solutions like WhatsApp an opportunity to capitalize in ways that incumbent carriers and telcos hadn’t realized. In the west, our technological progression is linear: mainframes to PCs to laptops and landlines to mobile phones to smartphones to the wide range of mobile and wearable devices available today.

For a variety of reasons (much of it due to the relatively recent emergence of necessary infrastructure) much of the developing world went from having no technology at all to having mobile devices. WhatsApp recognized that while smart phones with basic internet access were finally becoming affordable in emerging markets, carrier SMS rates remained expensive. Their solution? Save people money by enabling them to message each other through their data plans. WhatsApp made messaging less expensive, simple to use for those who aren’t accustomed to technology (imagine someone who’d never used a computer or phone before), and as device-agnostic as possible.

If WhatsApp highlights the need for frictionless person-to-person messaging, the need for frictionless business-to-business and business-to-person messaging is even more clear — especially since barriers to running mobile communication services in most of the developing world have been prohibitively expensive and, for many, too technically complicated. Some of the challenges typically associated with business mobile messaging (particularly internationally) include paying for an expensive short code from a local mobile carrier and hiring a development team to build out a communications service. All too often, business mobile messaging is out of reach for businesses and organizations without the necessary resources.

At Telerivet, we’re working to help make mobile messaging accessible to business and organizations around the world. And the unique ways in which these businesses and organizations are using mobile messaging are incredibly surprising and inspiring:

  • Clinics in rural areas send automated, scheduled mobile message updates to pregnant mothers to remind them to get periodical check-ups, reducing pregnancy complications and infant mortality
  • Radio networks send timely SMS notifications to local farmers with critical farming information and collect real-time weather and condition updates from farmers who on the ground, enabling them to compile mission-critical farming data and advocate on communities’ behalves to end hunger and poverty
  • Humanitarian organizations use SMS to collect representative data from families and displaced people in challenging environments to get real-time updates on rapidly-changing humanitarian and security situations
  • Banks provide credit scoring and financial literacy training through SMS to unbanked individuals around the world
  • Trucking and logistics companies in the developing world streamline their operations and keep track of packages as they move across rural or geopolitically unstable environments

There are virtually endless scenarios in which business to business (B2B) and business to consumer (B2C) mobile messaging is practical.

We’re living in a time of constantly accelerating technological change, and each iteration expands the possibilities of economies, businesses and ultimately, societies. The mainframe era made it possible to gather, collate and manage information, giving way to the PC, which allowed everyday businesses to bring computing power into their operations.

The rise of the cloud made it possible for businesses of all sizes to utilize and leverage powerful, scalable technologies without the cost and complexity of on-premise software.

We are now witnessing the ways in which the affordability of mobile devices have enabled people in emerging markets to finally have connectivity and services like WhatsApp have made that connectivity affordable for personal use anywhere on the globe. The continued democratization of mobile communications in emerging markets is a similar narrative to the cloud’s democratizing effect on business software in the West, and the implications of the rise of mobile communications that we can already see (not to mention those we haven’t yet) are boundless.

Africa’s rapid growth: 2 discussions

Africa’s massive growth in tech and mobile is gaining attention, and Silicon Valley is taking note of this opportunity. Our CEO Joshua recently spoke on two panels that focused on mobile payments and innovation within Africa.

The first discussion was part of Meltwater’s The Next Frontier Africa event series. The topic focused on how Africa is leading the mobile payment charge. According to Meltwater, “Africa hosts 6 of the 10 fastest growing economies and and has the second biggest mobile market in the world. With rapid urbanization and an ever growing middle class, now estimated at 300 million consumers, there is a large and rising demand for new technology products and services.”




Joshua commented that "The mobile money opportunity in Africa now is similar to the early days of Diner's Club card in the US."

Joshua also joined a panel on frugal innovation in Africa at m-NEXT at GMIC this past Tuesday. The main focus of the panel was on the rapid growth of Africa’s mobile market and how this expansion continues to present unique business opportunities across the mobile value chain. Panelists discussed how limited resources can lead to extremely innovative and creative ideas. The panelists also talked about how their companies have seen the expansive growth of mobile money and m-PESA within Africa.



To learn more about a user experience breakout session on Telerivet’s unique opportunities and challenges with designing technology for the developing world next month, read more here.

Hope to see you there!


Optimizing Telerivet for Mobile Web

Software developers like Telerivet face a number of unique challenges when designing and deploying software for users in developing countries:

  • sporadic power and internet connectivity
  • language barriers
  • devices ranging from feature phones to smartphones to PCs
  • older computers, phones, and browsers
  • users with less computer experience
  • higher latency and lower bandwidth
  • increased cost of internet access

Much of our work at Telerivet goes into addressing the particular challenges of building software that works well in developing countries, in places where most other software doesn't work very well.

Among these many challenges, we've recently been focusing on the particular challenge of making Telerivet's web-based tools work on mobile devices.

Even though Telerivet is designed for communicating with non-internet-connected mobile phone users, we initially designed Telerivet.com around the idea that our customers would manage their SMS service from a web browser on an internet-connected PC with a large screen, keyboard, and mouse.

For people using Telerivet's Android app to send and receive SMS, this meant that our customers needed two computing devices: an Android phone, and a PC.

But as we started to reach out to customers in developing countries, we realized that many of them use their phone as their primary computing device, and they didn't have easy access to a PC.

So we are happy to launch two new features today that will make a big difference for many Telerivet customers in developing countries. 

1. A Mobile web version of Telerivet.com that works on any smartphone (and many feature phones)

From any smartphone, simply open http://telerivet.com in your browser, to log in and manage your SMS service while on the go. Telerivet will automatically detect whether you are using a mobile or standard browser, so you use the same URLs on your phone as on your PC.

Mobile-contacts Mobile-messages


Most things work pretty well even on feature phones with Opera Mini (if you have enough patience)!

2. A new version of Telerivet's Android app that embeds Telerivet's web-based tools

For those using Telerivet's Android app, all of Telerivet's web-based administration tools are now available as tabs directly within the app. (For security, these tools require you to log in to your Telerivet account.) You can send and view messages, view and update contact information, view statistics, and configure automated SMS services such as subscriptions, polls, and auto-replies directly from the Android app. No PC necessary.

App-running App-messages

Of course, some actions are inevitably going to be tedious on a small touchscreen device, no matter what we do. So when it's convenient, you can still log into Telerivet.com using a PC with a keyboard and mouse.

How we did it

Instead of building entirely separate interfaces and interactions for mobile and desktop browsers, the two versions share almost all the same code.

(Actually there are three different versions, since the pages that show up within the Telerivet Android app are slightly different from those viewed in a normal mobile web browser.)

Most of the differences between the two (or three) versions of Telerivet.com are simply a matter of sending the browser a different CSS stylesheet. (CSS allows web developers to specify the sizes, positions, and colors of the various visual elements on screen when someone open a web page in your browser.)

Telerivet's desktop version assumes that the browser is at least 920 pixels wide, so the CSS stylesheet often specifies the exact pixel width of various parts of the user interface. In contrast, Telerivet's mobile version automatically adjusts the content to fit the width of the screen.

But some mobile optimizations aren't possible with CSS. In these cases, we create custom HTML templates to render parts of pages differently between the mobile and desktop versions of our website.

For example, in the desktop version of our website, each page includes a header with a graphical Telerivet logo:


On the mobile web version, showing this logo at the top of each page would take up a significant portion of the screen, leaving less space for the actual content (not to mention the extra bandwidth that would be used to download the logo). Instead, the mobile web version simply uses the text "Telerivet", while the version inside the Telerivet app doesn't include the word "Telerivet" at all.

Mobile-header  App-header

However, customizations like these come at a cost — more code for us to maintain and test! Since we're always rapidly adding new features to Telerivet, we don't want it to be twice as much work to support both a mobile and desktop version.

So we try to keep the differences between the desktop and mobile versions at a minimum, and structure our code so that the mobile and standard views can use the same HTML and CSS whenever possible. Only 2% of Telerivet's HTML templates and about 11% of our CSS styles are different between the mobile and standard versions of our website.

To upgrade the Telerivet app on your Android phone, just open the Telerivet app and click the button to upgrade. (If you haven't started using Telerivet yet, sign up for free here.)

Try it out on your phone, and let us know what you think!

(Stay tuned for more blog posts where we'll discuss our work to optimize Telerivet for users in developing countries, and follow us on Twitter for more updates!)

What we did when all the other SMS tools didn’t work

Welcome to Telerivet's new blog!

In the coming weeks/months/years, we'll be using this space to introduce new features and service updates, share tips and tutorials, profile organizations using Telerivet in interesting ways, and discuss our thoughts on the mobile ecosystem in general.

As we post new updates here, we'll tweet about them too — follow us on Twitter to stay updated!

To kick off our new blog, let's introduce how Telerivet fits into the huge ecosystem of SMS tools and services, as we tell the story of why we created Telerivet in the first place.

In 2010, we wanted to set up a SMS service so that grassroots non-profit organizations in Tanzania could publish news to envaya.org, interact with other organizations, and receive notifications, even if they didn't have internet access.

Here's what we tried, and how we ended up building Telerivet instead.

Attempt #1: Online SMS APIs

If we had wanted to set up this SMS service in North America or Europe, instead of East Africa, it would have been simple.

There are a lot of great online SMS gateway API services out there, like Twilio, Clickatell, Nexmo, and Tropo, which allow software developers to easily send and receive SMS messages from their own applications.

However, most of these services only offer phone numbers in a few countries, such as the U.S., U.K., and Canada.

This meant that our users in Tanzania would have to pay extra to send international SMS messages, instead of paying cheaper domestic SMS rates using one of the SMS bundles offered by their mobile network.

And although many of these services were able to send SMS to other countries, we found that international SMS was often unreliable  and sometimes wouldn't reach users on particular mobile networks in East Africa.

Attempt #2: Buy a SMS shortcode

To avoid the problem of sending international SMS, we tried to get a phone number in Tanzania that would let us send and receive SMS domestically.

Unfortunately, in Tanzania there aren't yet any companies like Twilio where you can get an inexpensive "longcode" virtual mobile number with an API for sending and receiving SMS.

However, there are a number of mobile networks and resellers that offer SMS shortcodes.

Often these companies do not offer transparent pricing, and instead negotiate private contracts.

We negotiated with one of them, and they offered a year-long contract amounting to over $5,000, in addition to about 3 cents for each message sent or received.

The non-profit organization we were volunteering for couldn't justify spending that much on a SMS shortcode.

To reduce the cost of SMS shortcodes, many companies offer shared shortcodes, which allow multiple users to build services on top of the same shortcode and reserve different keywords for their applications.

For some uses, shared shortcodes are often an economical option. However, shared shortcodes have the limitation that each incoming SMS message must begin with the user's unique keyword, and we decided they wouldn't work for us.

Attempt #3: Download software to send and receive SMS with a GSM modem

Free downloadable software tools like FrontlineSMS and RapidSMS have proven popular among many non-profits in developing countries.

With these tools, you connect a GSM modem or a basic feature phone to a computer running the software, turning your computer into a SMS gateway.

Tools like FrontlineSMS are indeed useful in some scenarios, especially because you can use them in remote areas where you don't have internet access.

But as we explored using them for our SMS service in Tanzania, it soon became clear that they would prove expensive, unreliable, and unmaintainable in practice.

Connecting a phone or GSM modem to our computer to send and receive SMS was the first challenge.

These software tools interact with phones and GSM modems by using a protocol called the Hayes command set (also known as AT commands), essentially the same way computers interacted with analog modems in the 1990s and earlier, complete with archaic settings like baud rate and COM ports. However, each phone and GSM modem implements a different subset of the protocol, and only a small fraction of current devices are compatible with the software.

None of the phones we already had proved to be compatible with the software, so we ordered one of the devices known to be compatible.  But when it arrived and we tried to connect it, the device drivers wouldn't install correctly on our computer.

As we struggled with connecting the GSM modem, we realized that even if we got it to work correctly, running a SMS gateway on a PC in Tanzania was not going to be maintainable.

In order to provide a SMS service 24/7, we'd need to dedicate a computer to it, make sure the software is always running and doesn't crash, and make sure the computer always has electricity – no easy task in developing countries like Tanzania.

And although software like FrontlineSMS and RapidSMS don't require internet access themselves, we would need reliable internet access in order to integrate with envaya.org. Since the non-profit's office in Dar es Salaam often has power outages that take the network down, this did not seem promising.

And if we wanted to access this computer from elsewhere, even just to send SMS notifications, we would need to host it somewhere where it would have a public IP address.

It was clear that the model of using PC and GSM modem as an SMS gateway was not going to work.

Attempt #4: Use a phone as an SMS gateway

We realized that since phones can send and receive both SMS messages and internet packets, that we could use a phone as a standalone SMS gateway without needing to be connected to a PC.

We started by exploring the possibility of building a J2ME (mobile Java) app that would work on the cheap feature phones common in countries like Tanzania. However, it didn't take long to discover that it simply wasn't possible to build apps that access the necessary SMS functionality on cheap feature phones.

Then, we discovered that on Android, a few SMS gateway apps had already been created — including KalSMS, APK SOFT SMS Gateway, and Ushahidi SMSSync.

We realized that using an Android phone as an SMS gateway was a great solution: sub-$100 Android phones such as the Huawei IDEOS are rapidly proliferating throughout developing countries (and are much less expensive than a computer and GSM modem); they're easy for non-technical people to maintain, and have built-in battery backup and redundant networking (Wi-Fi and mobile data) to stay operational in challenging environments.

Unfortunately, our testing showed that the existing Android apps were quite limited and not very robust. For example, all were limited by Android's restriction of 100 outgoing SMS messages per hour per app, and would freeze if you attempted to send more than 100 SMS per hour. Also, they all struggled with the problem of how to send outgoing SMS — since the Android phone generally does not have a public IP address, it has to constantly poll the server for outgoing messages, using bandwidth and battery life. They also didn't make it easy to figure out what was wrong if the phone was having problems.

Since none of the other Android SMS gateway apps were good enough for us, we built a vastly improved SMS gateway app ourselves, deployed it in Tanzania to power Envaya's SMS interface in October 2011, and shared it with other software developers.

Attempt #5: Start a company

Soon, other people began using our Android SMS gateway app, and non-developers started asking for our help because they didn't have the technical skills to set up servers, or to implement the complex developer API provided by the Android app.

Then we realized our opportunity: to provide a service to make it easy for anyone to build their own services and applications on top of SMS anywhere in the world, even if they didn't have the technical expertise (or didn't want to spend the time, money, or effort) to implement a complex API or run their own servers.

By building a service that combined an Android app with our own servers (aka "the cloud"), we could build something that non-technical users could use to send and receive SMS in developing countries, without all the issues of using a GSM modem with software on a PC.

A couple months of hacking later, we quietly released Telerivet in beta on Leap Day 2012. Telerivet lets people easily create and deploy custom mobile services anywhere in the world, letting them focus on the high-level aspects of creating and running mobile services without getting bogged down by technical barriers.

The response has been amazing.  Spreading mostly by word-of-mouth, leading non-profits and businesses are already using Telerivet to send SMS in many countries around the world, such as:

  • Kiva to facilitate communication between borrowers in Kenya and lenders around the world
  • myAgro (2012 Echoing Green winner) to allow farmers in Mali to save for agricultural supplies (even throughout a coup-d'etat)
  • InVenture to help people establish creditworthiness in India
  • FieldPulse Research to collect data from market sellers in Mogadishu, Somalia

Even if you work in a place with a bit more stability than Mali or Somalia, you can use Telerivet to build automated SMS services like opt-in subscriptions, polls, and informational services, or just send and receive SMS in your browser.

Read more about the amazing things that other people are already doing with Telerivet, and try it out yourself!

Jesse Young is Telerivet's Chief Technology Officer.