TelAPI Blog

Changes to Carrier Lookup API

Posted on by TelAPI


Please note that these changes have been made live as of October 1, 2014 3:20 EST

As a result of customer feedback, we are making a few changes to improve our Carrier Lookup API end-point which allows customers to look-up the Carrier/Network of a supplied phone number in the next few weeks.

The pricing for carrier look-ups will not change.

We are making these changes in an effort to improve the look-up detail in returning more refined data across operators for the global phone numbers.

We are updating our international data to be more descriptive: with additional flags for SMS enabled networks and Networks that support actual devices vs. being phone numbers that belong to an OTT provider (over the top/app supported) or MVNO (Mobile Virtual Network Operator).

As a result of this update, you will now be able to identify the MVNO/OTT provider and their supporting network. This will allow you to differentiate which phone numbers belong to services such as Google Voice, Skype, etc., and will provide you with the underlying operator/network, rather than only the underlying operator/network as we have provide you today.

An important change is being made to our existing Carrier IDs, which reflects an internal reference to the network operator. If you have been using the Carrier ID rather than the name of the network to identify the carrier/operator, this change will impact you going forward. You will want to make the change to consume the newly updated list. It is highly recommended that you review your current process and ensure that the updated Carrier ID list is being used going forward. You should download the new list at your earliest for review and implementation.

We made a change of requiring the request to be sent via POST instead of GET, in the past.

Carrier lookup is achieved using the HTTP POST method. The format of the URI used to
make the POST request is below.
POST https://api.telapi.com/v2/Accounts/{AccountSid}/Lookups/Carrier
Kindly make sure this is being used going forward, as this remains the same.

We are hoping to push these changes in the next 1-2 weeks and we know these changes will affect how your application will interpret carrier look-ups so want to make sure you are prepared.

We are here to help you transition to the new update, please let us know if we can help you do so in any manner.

Please note that these changes have been made live as of October 1, 2014 3:20 EST

Posted on by TelAPI | Posted in API | Tagged ,


Transcription Slicing

Posted on by TelAPI


With our newly released feature of transcription slicing, you can request your submitted audio URL to be transcribed to a certain duration.

This new feature allows companies and developers to transcribe a snippet of the submitted audio instead of the entire file.

SliceStart and SliceDuration allow you to pass the requested duration measured in seconds.

This option is available when transcribing an Audio URL: http://www.telapi.com/docs/api/rest/transcriptions/transcribe-audio-url/#SliceStart or any recording: http://www.telapi.com/docs/api/rest/transcriptions/transcribe-recording/#SliceStart

We'd love to hear how you are using our services. It is our goal to help you take advantage of our powerful APIs to build your next VOIP application.

If you have any questions about our transcription service, please don't hesitate to get in touch with us at support@telapi.com

Note: The SliceStart and SliceDuration are only available within the RestFul API, support for these parameters within InboundXML is coming soon!

Posted on by TelAPI | Posted in General


Things to know for Messaging (SMS) with TelAPI

Posted on by TelAPI


TelAPI allows you to send messages around the globe.

We offer interactive messaging with virtual numbers and allow one-way or two-way messaging via in-country short-codes/bulk SMS routes.

Our focus is on deliverability; so we either connect directly with one of the in country operators or a central aggregators that is no more than 1 connection away from the destination operator.

For notifications and time-sensitive messages, it is best to deliver messages via ShortCodes or Bulk 1-Way routes; As these routes provide you with delivery status notifications and update as the message gets delivered, which sometimes can mean: handset delivery confirmation.

Since each country varies on what type of messaging is allowed, it is highly recommend you check our SMS features document, which will provide you insight on what Sender ID (within TelAPI, we call this the FROM address) requirements based on the country you are sending messages to.

Short-Codes and 1-Way International routes provide you with delivery reports; allowing your application to know when your message was delivered to the end-user.

Below are details of the various SMS routes available through TelAPI. Keep these in mind when using our SMS gateway and you will be able to launch your application without any issues.

US-messaging via Virtual Numbers
This is meant to be used for interactive messaging. The virtual numbers are voice-enabled and can also send/receive messaging from other US based operators. This makes these numbers perfect for interactive messaging. You will be able to send messages by setting the FROM to your purchased virtual number (from the TelAPI dashboard) to a destination number. You can also have an auto-response message incase anyone sends a message to your number; by simply editing the InboundXML document and assigning it to the number.. The limit of delivering messages on these numbers is 3 messages per minute; and are not meant to be used for high-throughput marketing campaigns. Messaging via Virtual Numbers does not support delivery confirmations, we simply show you successful hand-off to the destination operator.

If you are creating a two-way messaging service and want to ensure that the end-user get their messages from the same number, be sure to correspond the origination and destination numbers accordingly. We supply each unique message to/from respective networks with a SID (a unique record), which will allow your application to keep track of these messages.

US-messaging via Short Codes
Short-Codes messages can be scaled to meet higher through-put messaging (than with virtual numbers) along with delivery notifications. TelAPI offers shared short-codes and dedicated short-codes to accommodate for short term campaigns.

Within the US, Short-Codes can be leased from the CSCA (http://usshortcodes.com) and provisioned via TelAPI. Although each provider is different, each application will require that you adhere to MMA (Mobile Marketing Association) guidelines and require approval from each operator that the Short-Code will be made available on.

TelAPI can guide you through the provisioning process and manage communications to all operators regarding your use-case and campaign.
International Short Codes are available within TelAPI in the following countries.

  • Brazil
  • New Zealand
  • United Kingdom
    Contact support (at) telapi.com in order to get more details for Short-Codes outside of the US.

2 way messaging with In-Country Local SMS Numbers (Other countries)
TelAPI offers two-way messaging in the following countries, by request. These numbers are not readily available on our dashboard until we have ensured the use-case is approved by the in-country operators. These numbers are only enabled for SMS inbound messaging. Our users utilize 1-way messaging (mentioned below) and numeric sender IDs, to create a two-way messaging experience for the end-user.

  • Austria
  • Australia
  • Canada
  • Czech Republic
  • Finland
  • Hong Kong
  • Hungary
  • India
  • Ireland
  • Lithuania
  • Netherlands
  • Norway
  • Poland
  • Spain
  • Sweden
  • Switzerland
  • United Kingdom

Upcoming Countries for SMS only number:

  • Belgium
  • China
  • Denmark
  • France
  • Germany
  • Portugal
  • Russia
  • Singapore
  • South Africa
Also, please note: International Short Codes are available in:
  • Brazil
  • New Zealand
  • United Kingdom

1 way messaging, Other countries
One-way messaging is available in 180 countries. TelAPI offers delivery confirmation that are posted on your SMS callback URL; allowing you to measure the time the message was delivered. For this method of submitting messages you have the flexibility to set your FROM address to an alpha/numeric character for upto 15 characters. Again, this depends on the country you are sending the message to; but a quick review of this list of SMS features will help you get a better insight on the sender ID options and allowing you to send SMS messages through TelAPI.

Documentation for our API can be found here.

If you have any questions regarding SMS, feel free to reach dev (at) telapi.com, anytime!

Posted on by TelAPI | Posted in General | Tagged , , , , , ,


Carrier Lookups API

Posted on by TelAPI


At TelAPI, we strive to deliver the most robust telephony platform on the market, allowing developers to mix-and-match our API to deliver complete enterprise solutions.

Our new Carrier Lookup API allows you to perform a real-time carrier/provider lookup on any phone number (mobile/landline). We aggregate this data from in-country local number portability as well as line-range databases maintained by country specific number registry providers. The carrier lookup API provides accurate and real-time information so you can act on it by delivering targeted services and marketing to your end-users.

Below is an example of the data you can expect when sending a carrier lookup request to TelAPI.

The response.

A complete list of covered operators and their respective Carrier IDs can be found on an excel sheet Here.

You can read the full the API docs at http://www.telapi.com/docs/api/rest/carrier-services/carrier-lookup/.

If you have any questions regarding our Carrier Lookup API, please email us at support@telapi.com

Posted on by TelAPI | Posted in API | Tagged , ,


Introducing TelAPI Heroku Addon

Posted on by TelAPI


One of TelAPI’s foremost goals is making the lives of developers easier when building Telephony applications. Heroku is a platform developers can use to make their lives easier when building ANY type of application. Thats why we’re super excited to announce the public beta of our Heroku Addon.

Starting today, developers on the Heroku platform can integrate with TelAPI in minutes. With the the TelAPI Heroku Addon, your app can now send outbound SMS messages, place outbound calls, and even purchase dedicated phone numbers for receiving inbound SMS and calls. All this telephony functionality and no new sign ups -- everything is seamlessly integrated within your existing Heroku account.

To get started, simply provision the addon to your Heroku application via the Heroku CLI Tool:

Or just grab it from the addon marketplace: https://addons.heroku.com/telapi

Once provisioned, you can make HTTP requests to the heroku.telapi.com domain with your authorization token to initaite calls or messages. Any built in HTTP methods or REST helper libraries will work to facilitate these requests so the addon can be used with the programming language of your choice!

We hope this addon helps developers get their telephony applications off the ground faster and can’t wait to see how its used.

Feel free to get in touch with us at support@telapi.com for more information on getting started using the TelAPI Heroku Addon or view the addon documentation available in the Heroku Dev Center: https://devcenter.heroku.com/articles/telapi

Posted on by TelAPI | Posted in General


Part 2: How To Build An SMS Subscription Service With TelAPI

Posted on by TelAPI


In Part 1 of this two part blog post, we walked through how to lay the foundation for an SMS subscription service. With just a few lines of code using TelAPI's Ruby helper library, users can now 'subscribe' or 'unsubscribe' in order to be added to or removed from our database.

The next question we have to ask ourselves is, what kind of content would we like to share with our subscribers and how often would we like to send it to them? First, we'll create a Messages class that can be used to instantiate messages which can be sent to our users. Then we'll use a Heroku scheduled task to send out daily messages to our subscribers regarding upcoming deals our company is offering.

As we did for our User's class in Part 1, we'll once again use scaffolding to generate a Messages model, Messages controller and a Messages view. Messages will have names (string), dates (string) and content (text). The 'name' attribute will be used to uniquely distinguish each message. The 'date' attribute will be used to determine when a particular message should be sent to subscribers. Lastly, the 'content' attribute will be what is sent in the body of our text messages. Let's go ahead and generate our Messages class:

$ rails generate scaffold Message name:string date:string content:text

As we did before upon creating our User class, this will also require a database migration.

$ heroku rake db:migrate

Let's then open our application and create a few samples messages (like the one below) associated with deals our business is offering on certain days.

Take note of the date in our Messages class. Ultimately the date attribute will be used to determine if our SMS messages should be sent. I'll elaborate more on this shortly. Also, you'll notice that the date attribute is in UTC format. This is the date/time format Heroku uses. For the sake of this walkthrough, we'll use UTC date/time in an effort to keep things consistent.

Now that we have our sample messages created, we can then configure a scheduled task to run everyday. The scheduled task will be used to check and see if there are any messages with today's date regarding a deal we're offering that should be sent to our subscribers. Since we are already using Heroku, let's go ahead and use their Heroku Scheduler add-on (though a traditional cron job would work just fine).

To use the Heroku Scheduler add-on, it can be installed like so:

$ heroku addons:add scheduler:standard

Once installed, open your application in the Heroku dashboard. You'll notice that your application has a new "Heroku Scheduler Standard" add-on. Click on that to open the scheduled job configuration page. Upon opening it for the first time, you'll notice that currently "You have no scheduled jobs".

Go ahead and click the 'Add Job' link. Then, let's name the job 'send_sms' and execute it as a rake task. We'll run that rake task everyday at 15:00 UTC (10am EST). Hence, your Heroku Scheduler dashboard should look like this:

Now that we have done that, it's time to write the code the rake task will execute everyday at 15:00 UTC. First, we need to create a scheduler.rake file where we can add our 'send_sms' method. The 'send_sms' method will be used to make an HTTP GET request to a new action called 'send_sms_to_subscribers' in our TextsController. To perform the GET request we'll use HTTParty (i.e. a gem we installed during Part 1). Here's what the code looks like:

We will then save scheduler.rake in our "lib/tasks" directory. Also, we have to remember to add a route to "config/routes.rb" to account for our new 'texts/send_sms_to_subscribers' action.

Now it's time to create our new 'send_sms_to_subscribers' action. When our scheduler.rake task makes an HTTP GET request to 'send_sms_to_subscribers', it must check to see if there is a message in our database with today's date. If there is, then it will send an SMS to all of our users with the message's content as the body of the SMS. The following is what the 'send_sms_to_subscribers' action will look like:

Because this action is using TelAPI's REST API to send SMS messages, we must be sure to authenticate with TelAPI using our Account SID and Authentication Token. To do this, let's create an initializer named 'authenticate.rb' and store our TelAPI credentials there. This way, we'll be able to use our credentials throughout the entire application.

Lastly, let's test our 'send_sms' task to make sure everything in 'send_sms_to_subscribers' is working properly. To do this, we will use rake to trigger the task:

$ rake send_sms

In our server logs we should see the successful GET request to 'texts/send_sms_to_subscribers'. As mentioned before, this action uses TelAPI to send out the texts with today's content to all of our subscribers.

And there you have it! We've successfully implemented a fully functioning SMS subscription service with just a few lines of code. Now your business is well-positioned to take advantage of a rich new medium to engage your customers.

If you have an questions regarding this blog post, please reach out to TelAPI's developer evangelist, Doug Crescenzi. He'll be sure to help you with them!

Posted on by TelAPI | Posted in General | Tagged , , , , ,


Part 1: How To Build An SMS Subscription Service With TelAPI

Posted on by TelAPI


Looking for a new way to engage your customers? Why not give an SMS subscription service a try? In recent months, more and more businesses have begun using SMS subscription services than ever before. Why you ask? Well, there's a few reasons.

First, SMS subscription services facilitate a direct line of communication to your customers. Instead of having them seek information out, your company can use SMS subscriptions to deliver information straight to them. Second, SMS subscription services establish a frictionless user experience. That is to say, they require little to no effort on the user's end to effectively utilize the service. Third, SMS subscription services work as informative reminders. In other words, customers can use them to receive the information they need, when they need it.

As a result of their effectiveness, members of our developer community have inquired about how to build these SMS subscription services. Fortunately, they're incredibly easy to build with TelAPI!

The following two-part blog post demonstrates how a simple SMS subscription service can be built with Ruby on Rails and TelAPI's Ruby helper library. Part 1 walks through the process of building an application with TelAPI that can be used to process incoming SMS messages and create/delete subscribers. Part 2 will explain how scheduled tasks can be used to generate requests to TelAPI's REST API in order to send SMS messages to all of your service's subscribers.

OK, so first things first. Go ahead and create a new Ruby on Rails application.

$ rails new sms-subscription

Upon doing so, open up your Gemfile and add the following gems to it:

Then go ahead and perform a 'bundle install' to ensure all dependencies from the Gemfile will be available in the application.

$ bundle install

Next, let's go ahead and create a 'Texts' controller with a 'subscribe' method that will be used to process incoming SMS subscriptions.

$ rails generate controller Texts subscribe

After our controller has been generated, let's go ahead and assign our TelAPI number to a variable in the 'subscribe' method. Also, while we are at it, let's assign numbers from incoming SMS messages to the 'from_number' variable. That way, when our TelAPI number receives an inbound SMS message, the phone number the message came from will be assigned to a variable. In addition, we'll assign the body of the incoming SMS message to a variable as well.

Next,  create an if statement to handle incoming user subscriptions. In the case that a user texts "Subscribe" (or "Unsubscribe") in the body of a text message, we want to be sure our service recognizes the request and handles it appropriately. We also want to account for incoming messages in which the text's body is neither "Subscribe" or "Unsubscribe". The following if/else statement addresses this:

Once we have ported our code over to our hosting solution of choice (in this example, Heroku), we must then configure our TelAPI SMS Request URL to retrieve and execute our code above. This can be done through the TelAPI 'Manage Numbers' dashboard.

 

Now that we have our SMS Request URL configured properly, it's time to address how to store users in our database. First, we'll use scaffolding to generate a User model, User controller and all corresponding User views. Our User class will have only one attribute: number (i.e. the phone number a User subscribes from).

$ rails generate scaffold User number:string

Don't forget, we need to perform a database migration to alter our existing database and add the new User table to it.

$ heroku rake db:migrate

Now that we have a User class and a Users table in our database, we can then create instances of User when our service receives text messages with "Subscribe" in the body. To do this, we must include the following code after our initial if statement:

Next, we must account for individuals that would like to unsubscribe from our service. To do this, we must add the following line of code after our elsif statement:

Therefore, the code from the entire TextsController looks a little something like this:

Now, we have a working SMS subscription service in which users can 'subscribe' and 'unsubscribe' in order to be added to or removed from our database.

As you can see, creating the initial subscription component of this service was done very easily with TelAPI. In part 2 of this blog post, we will learn how to use a scheduled process to make requests to TelAPI's REST API and send outbound SMS messages to all of our subscribers.

If you have an questions regarding this blog post, please reach out to TelAPI's developer evangelist, Doug Crescenzi. He'll be sure to help you with them!

Posted on by TelAPI | Posted in General | Tagged , , , , , ,


8 Simple Ways Your Startup Can Use SMS And Voice With TelAPI

Posted on by TelAPI


Using TelAPI to create applications that interact with the telephone network is simple. Dead simple. Despite its simplicity, TelAPI is a powerful tool with a range of practical uses for startups. The best way for us to prove this, is by giving you sample code and example apps to backup our claim and get you on your way to setting up your first TelAPI application.

We've tried to make this post as simple as possible, by doing a few examples just in XML, but we've also taken the time to create other examples in PHP, Python, and Ruby. (Note: The PHP, Python, and Ruby examples utilize our TelAPI helper libraries for that language)

When you sign up for TelAPI, you'll also receive $25 in free credit to test these uses — enough to get you 2500 SMS, 2500 voice minutes, or a US phone number for 25 months!

1. A Business Phone Number That Forwards To Your Cell Phone

Entrepreneurs and small business owners want their customers and clients to have access to them at all times, but they don't always want to give out or publicize their direct personal phone numbers. To solve this problem, TelAPI phone numbers can be used to receive calls and forward those calls to another number — anywhere in the world. The best part is, this can be done very easily, with just a few lines of XML.

It gets even easier though! If you use TelAPI's InboundXML Editor, we'll host the XML code for you, so you don't even need a web server or your own hosting to get this up and running. 

2. A Simple Conference Room For Conference Calls

There are countless cases where businesses may need to quickly setup conference calls for impromptu meetings. This is typically costly and/or burdensome, and in many cases inconveniences employees. No one actually likes conferencing services that give out a dial-in number plus another 10 digit room number to dial. It's almost impossible to use a conference room setup like this if the dial-in number is in an email on your smartphone and you don't have a pen handy! With TelAPI, businesses can easily instantiate one, consistent conference call number to share with participants.

3. Record Incoming Calls And Have Them Transcribed To Text

Recording incoming calls and having those conversations transcribed to easily readable and searchable text is extremely valuable. Many businesses and individuals are doing this these days, as a means to capture important information and reference it at a later date. Accomplishing this with TelAPI can be done very easily in just 2 steps. The first step simply involves crafting an inbound XML document that receives the incoming phone call on a TelAPI number and records the conversation. The second step is receiving the resulting transcription in a callback script.

To show you an example of this, we've broken the code down into the two necessary files. You'll notice that part 2, which is the callback script, simply receives the transcription and echos it. However, you could easily expand upon this example. For instance, the transcription could be emailed to participants on the call, stored in a searchable database or even shaved via SMS. The possibilites are endless.

4. A Professional Sounding IVR Menu With Departments

IVRs are ubiquitous in today's enterprise business environment. Many small and medium sized businesses would undoubtedly find value in having such a system in place, but they may lack the resources or funds necessary to build one. TelAPI changes that. Now any developer can buy a toll free number and build a high quality IVR in minutes.

Below is a sample IVR that offers your callers the option to be transfered to three different departments. From here, you could setup an "ivr-user-response" script on your server to do whatever you'd like for each extension, such as routing the calls to a voicemail box or to another individual's phone.

5. SMS Reminders

There are many instances in which businesses could benefit from providing an SMS reminder service to their customers or clients. For instance, if a doctor has a client with an appointment scheduled for tomorrow afternoon, his office could send that client an SMS reminder so they won't forget about their appointment. Practical and useful!

6. Verifying A Number Is A Mobile Number

Many companies these days prefer using SMS over email to send out personalized offers or information to their customers. But are you sure the numbers in your list are valid mobile numbers? Have you thought about checking the numbers before they get added to your lists? For these types of campaigns, it's important for a company to verify their lists only contain mobile numbers capable of receiving SMS. TelAPI's Carrier Lookup endpoint and its 'IsMobile' property can do just that.

7. Customized Caller ID Greetings To Callers

To offer the best service possible, many businesses find it advantageous to offer personal greetings to incoming callers. This can easily be implemented by obtaining the 'CallerName' attribute in the request parameters.

8. Screening Incoming Calls

Businesses can find added value in using call screening software to determine who incoming calls are coming from. For instance, if an important client is trying to get through, they likely don't want to miss that call. However, if it is a telemarketer or something else that is inconsequential, a business's employees would likely prefer to ignore those callers. With TelAPI, building call screening software can be done very easily. This, of course, is just one simple example, but could be expanded upon to create a more comprehensive system.

Take away: These are just a few of many potential business uses that can be implemented with TelAPI using very little code. Ultimately, TelAPI enables developers of all skill levels to seamlessly build a wide-range of powerful telephony applications.

If you have any follow-up questions concerning the examples above, please reach out to Doug Crescenzi, TelAPI's developer evangelist.

Posted on by TelAPI | Posted in General | Tagged , , , , , , , ,


Developer Spotlight: Blow Up My Phone

Posted on by TelAPI


Do you sometimes find yourself looking to escape from awkward conversations? What about times when you're out and about, and you want to show your friends and family how popular you are? If these types of questions resonate with you, then you should definitely check out Blow Up My Phone.

Jonas Meyer's Blow Up My Phone allows users to schedule incoming calls and text messages to their phones as a way to escape from those awkward moments we all know too well. For incoming calls, Jonas is using custom caller IDs which allow his users to make incoming calls come from any number they'd like. "Oh look, my mother's calling. I gotta run!" As Jonas puts it, "It allows a simple phone call or text message to be used as a social tool providing the user credible ‘social currency’ in real time."

Jonas was inspired to build the application after a friend had asked him to call him while he was out on a date. His friend told him that it was a precautionary measure in case the date was going poorly. Not only that, if his date were to see that his phone was blowing up she would "assume that he was popular or important". As far as Jonas's friend was concerned, the fake incoming call was a win/win on both fronts in the context of a potentially awkward date.

Blow Up My Phone was built in PHP via the WordPress CMS. Jonas used scripted shortcodes in order to interface with TelAPI and make phone calls, send text messages and use custom caller IDs. Jonas noted that without the freedom to use unrestricted custom caller IDs, he wouldn't have been able to build such an innovative telephony application.

Next, Jonas intends to create call recordings in other languages and make Blow Up My Phone an international application. He also plans to leverage TelAPI's InboundXML editor as a more convenient way to host and modify his TelAPI XML documents on the fly.

Blow Up My Phone is fresh out of beta and its subscriber-base is growing at a rapid pace. Jonas is super excited about it and we are too. You should definitely check it out!

Learn More About Jonas Meyer

Jonas is a Sarasota, FL based developer/hacker and creator of Blow Up My Phone.  At the moment computers are only a hobby as he’s currently pursuing a BS in Finance. While not in school, Jonas enjoys spending time with his son, building fun telephony web applications and entertaining world changing ideas.  You can contact Jonas on twitter @blowupmyphone or via email at jonas@blowupmyphone.com.

If you're a developer that has built an innovative application using TelAPI, we would love to hear from you! Please reach out to TelAPI's Developer Evangelist Doug Crescenzi to see how we might be able to help you promote your application.

Posted on by TelAPI | Posted in General | Tagged , ,


TelAPI’s Emergency Response and Preparedness Hackathon Recap

Posted on by TelAPI


This past Saturday, TelAPI hosted our very first hackathon, held in New York City, with our good friends at Rain. The hackathon's focus centered on using telephony to create tools for emergency preparedness and response, something which was still fresh on everyone's mind after the recent Hurricane Sandy tragedy. Twenty-five developers came together, and over the span of a 12 hour period, built some incredible applications with immense utility. Here's a brief overview on some of the tools built at the hackathon:

  • POD (winner) - POD (i.e. Power Outage Detector) is a hardware component anyone can plug into their power outlet (and keep plugged in) to determine when the power goes out. When POD detects a power outage, it uses TelAPI to send a text messages to the owner and also calls their utility company to automatically report a power outage (it even uses the owners own phone number as the Caller ID). In addition, POD records every time your power goes out and for how long, which you can see via the web.
  • HomeBase (2nd place) - HomeBase offers hyper-local messaging services to apartments and office buildings. First, it enables any user to create a profile for their apartment or office building through SMS. Once a building's profile is setup, residents or employees can easily join and use HomeBase to send messages to other individuals associated with the profile or broadcast messages to all members using SMS. HomeBase is a great tool for sharing resources and perfect for disseminating information when individuals are away from their residence or offices.
  • Hugo Helps - Hugo Helps is a service allowing users to simply text an address to a TelAPI number and determine if power is available. In the case that power is not available, Hugo responds with the addresses of nearby hotels that have power.
  • Sprout Help - Sprout Help is an application with SMS, web and Twitter interfaces that uses geolocation to match people in need with people ready to help. Sprout Help creates direct relationships to expedite various aid offerings. Instead of proxying resources through intermediaries, Sprout Help aims to ensure resources are allocated effectively and with agility.
  • SafetyNet - SafetyNet is a tool that enables users to quickly broadcast information to emergency contacts using SMS when it matters most. SafetyNet offers three different emergency levels to ensure individuals are able to share critical status information with close friends and family, as well as being able to connect with emergency services in a time of need.

If you would like to learn more about these projects and upcoming TelAPI hackathons, please reach out to Doug Crescenzi, TelAPI's developer evangelist. 

Posted on by TelAPI | Posted in General | Tagged , , , , , , , , , ,