System Details


First -- this is for US Mobiles only.  We do realtime lookups on the phone number and verify that it's a US wireless number.  If you get a failure on registration, it's simply because your user entered a non-US or non-mobile phone number.  Really!  We reject land lines, VOIP, Skype numbers, Google Voice.  We support only US Mobile carriers.

Registering users in Telesocial is simple, and relies on hard authenticating user devices (mobile phones) with the system.  As a developer, the first thing to do is to query the Telesocial API with the user's network ID to get the user's status in the Telesocial system.  First, developers should check a user's registration status -- think about asking a simple question like "Is the user's device in the Telesocial system, and if so, can I use it for communication"?  There are 2 parts to registering with Telesocial -- the first, called a "Hard" registration is when a user's device (phone number) is not in our system.  In this case, the user will have to complete a hard challenge, which is really just them answering their phone and pressing "1" to register into the system.  The second use case is what we call a soft registration, which does not require a user to enter a challenge, but requires your application to acknowledge that the user has opted-in to your application and does make a separate system call to designate opt-in by you, the developer.  


The network ID is the identification number, symbol, or string used in a particular affiliated social network and implemented in the Telesocial API.

Facebook:         Facebook ID
Twitter:            @twittername
iOS:                 iTunes username
Android:           Android App Store username
LinkedIn:          Linkedin ID 
SalesForce:       SalesForce UserID
Box:                 Box  username
Yammer:          Yammer login user
Email:              Email address, the old-school social network
Minecraft:         Minecraft username


Really a conferenceID as discussed.


Uploaded or recorded content in the Telesocial API.  In the case of uploaded content, MP3 media is expected, and in the case of recorded content, we generate MP3 files.  You can play back the MP3's as URLs or play back on mobiles.

Greetings:  special media files that you designate as prompts for calls, recordings, playback and other functions that require "Press 1".


Let's look at our demo application at

In any Telesocial application, you will be doing one of a few things -- having people call into TalkSpaces, record MP3's from the phone, playback MP3's etc.  In each case, when you make the phone ring, there's a default "Press 1" security greeting that the users hear.  We let you customize this greeting, so in effect you establish the message and the context and content of the call and make it completely your own experience in your application.

CallFriends - Press 1 to Activate your Phone - Opt In

CallFriends - Press 1 to Activate by Telesocial

Example:  issue a create media request and generate a media ID -- think of this as a placeholder / wrapper for the media that you wish to manipulate.  Once you have a valid Media ID, you can issue a "record" command to generate phone-recorded content (which gets delivered as an MP3 or as a phone "Blast") or you can then upload binary MP3 content to the server directly via mime-multipart binary uploads.