Writing Voice Mashups with Amazon Turks - Presentation Transcript
Writing Voice Mashups Thomas Howe - http://www.thomashowe.com
Agenda
Introduce the After Hours Doctor’s Office
Scenario
The goals of the Mashup
Introduce the architecture
Go over every component
Functionality, interface, code
Give you some ingredients, ideas
What this isn’t
A complete, and coherent, application
Utterly scalable, but surprisingly close
What is this?
Think of Lewis and Clark
Today’s telephony is very far from this. Very far.
With a bit of luck, this is tomorrow’s telephony
After Hours Doctor’s Office
Mashup written specifically for the Contest
I quit my job because I was technically bothered
Goals
Show you the money
Explore the use of Amazon Turks in Telephony Mashups
Demonstrate the effects of modern Web technologies in telephony applications
Resources
Me, 40 hours and a PowerMac G5 Server
TellMe Studio - Voice XML hosting
Strike-Iron - SMS Messaging
Amazon Web Services - Amazon Mechanical Turks
Web Hosting Provider - PHP and Ruby on Rails
Source and commentary available at thomashowe.com
Application Scenario
Mr. Kraus feels sick, calls Dr. McCarthy
After hours - no one’s there.
Decision to make - emergency room? Tomorrow?
Application takes voice mail message
Forwards into pool of Amazon Turk Nurses
SMS messages increase reaction time for small service
Immediately responds to patient - constant feedback
Turk Nurse determines urgency
Listens to the message, summarizes and forwards
Application gives direction to patient
Routine? A message from nurse reassuring patient
Urgent? A call from the Doctor, right away
Benefits?
Faster, cheaper with a higher quality of care
The Money
Where is the money?
50 million unnecessary emergency room visits in the US
Each costs about $900.00 more than a doctor’s office visit
Where isn’t the money?
Customer education that the service exists
Repeated marketing to habituate the service
Costly market trials
Why?
Integration of real time communications into the business process makes it more efficient, saving money for the enterprise and increasing customer satisfaction
Amazon Turks
Internet Scale Workforce
One doctor needs 1/10 of a nurse
One thousand doctors needs 100.
More use, more turks, faster service
Practical? Absolutely
Nurses get $3.00 for three minutes work == $60/hour
Down time, family time, sick time, whatever
Off-shoring?
Comprehensive Quality
Amazon Turks automatically
Record urgency accuracy, compare history
Transcriptions
Bringing a knife to a gun fight…
What did I use?
40 hours, web services and a rapidly aging geek
Ruby on Rails, SOA, PHP
$25.00 to Strike Iron, and I’d probably have to pay x cents a minute to TellMe, Angel, or Voxeo
What did I not use?
Big Iron ==> NO LARGE INVESTMENT
A Contract ==> NO CARRIER INVOLVEMENT
Marketing ==> NO CUSTOMER EDUCATION
Risk ==> NO LONG DEVELOPMENT CYCLES
Traditional carriers will get their clocks cleaned.
After Hours Mashup Architecture
VoiceXML
Accepts inbound phone calls with rich media experience
A few short years ago, communications applications more
A few short years ago, communications applications required millions of dollars, teams of highly skilled engineers, access to networks, and many months of time. Telephony Mashups rewrite that equation, and make it possible to blend communications services into applications quickly and easily.
In this workshop, led by 2007 O'Reilly Mashup Winner Thomas Howe, we look at how these mashups are created, and at the implementation details in depth. Using After Hours Doctor's Office as an example, every part of the mashup will be reviewed in code-level detail, including a Voice XML front end, the software interfaces to the Amazon Mechanical Turk nurses, and mapping displays to help direct the patient to a local health care facility. The attendees will leave with a good understanding of the technology and effort required to write their own compelling application.
less
0 comments
Post a comment