The fun part about blogging is the new people you get to meet and converse with. This happens in a variety of ways. Some people post comments, some write emails, some tweet, but recently I got my first voice message comment.
It was from Chris, a Telecom Specialist in North Carolina, whom I have not had the pleasure of meeting in person. This blog has a gadget that allows visitors to call. Chris called, and left me a voice mail. The voice mail was 2:22 long and was delivered as an audio file and a text file. Here is an excerpt:
This was using voice recognition software provided with the Google Voice service (voice mail transcription). As you can see, it isn’t perfect. Here is the revised version I created after listening to the message:
I’ve been a proponent of IP telephony for a long time (Skype and Google Voice stuff is pretty cool too). Only one comment, I love doing telephony from the PC from the PC desktop, Only problem is the PC has to be on and logged on to do it…
It is actually a little more clear in the Google Voice inbox because the more ify words are in gray and when you press the play button, the cursor highlights the text as it reads it. I don’t expect the voice recognition to be able to get the unspoken parentheses, but why can’t it capitalize the “i’ve” like a word processor can?
Anyway, the point is this blog is hosted by Blogger (yet another Google tentacle in my life). Why not offer a solution that allows the voice mail (with the audio, text, and play button) to be within the comments section?
It really doesn’t even have to be Google Voice. Companies like Twilio or Voxeo should be able to offer a widget like this (though unlikely for free).
This is the great part of UC, being able to apply the pieces into custom(izable) solutions offering new capabilities. The solutions can be from anywhere and be implemented anyplace where it makes sense.
There is no ROI in audio comments on my blog site (though clearly it would be nice), but the ability to take things like a voice mail recording and update an application has lots of potential. For example, a field tech that calls in to close a ticket – complete with reason codes and free form text. Lots of websites rely heavily on comments – such as Amazon (they even rate the comments) – why must contributors be forced to type?
There are speech recognition systems that work better than shown above. Of course, when you know what to expect, the systems get very accurate – like a “yes” or “no” choice. Free=from text is quite a bit trickier. One of the problems with Google Voice transcription is people don’t talk slowly and clearly to voice mail as they do when they know they are talking to a speech recognition system.
Nice post… looking at speech recognition hard lately. Just haven't found a good way to deal with large vocabularies, background noise, and accented speech.
http://www.twilio.com Danielle Morrill
Hi Dave,
You might enjoy Twilio Labs, where we have a bunch of widgets called Twimlets that you can use to quickly build simple voice apps with Twilio.
Here's one I made for you, call 866-945-1842 to try it out. You could easily use the Voicemail Twimlet (which is what I used) to add a phone number to your blog where readers can call in and leave comments.
Dave is a self-proclaimed Telecommunications Contemplator. Most industry professionals gravitate toward the role of Analyst, Consultant or Journalist, but Dave blends all three as a professional Contemplator. He shares what he sees with the vendors, service providers, and end users. Learn More
New Panasonic KX-UT670 Smart Desk Phone Recognized for Innovation SECAUCUS, NJ–(Marketwire – Feb 2, 2012) – Panasonic System Communications Company of North America, the leader … […]
New Numbers Show Information Professionals, Hiring Managers and Decision-Makers Benefit From Certification SILVER SPRING, MD–(Marketwire – Feb 2, 2012) – AIIM, the global community of … […]
By Martha BuyerThe state of Florida determined that over a 7-year period, more than 600,000 customers were charged for Roadside Assistance at $2.99 per month without either granting consent for such charges or using the […]
By Andy HowardMobile device support for video conferencing is clearly in its infancy, but all of the vendors are going to continue to invest heavily in mobile capabilities because their customers are demanding it. […]
ShoreTel had a blockbuster week, announcing it has signed a definitive agreement to acquire M5 Networks, giving its customers a choice between on-premise and hosted UC solutions. The acquisition allows ShoreTel to quickl […]
Applied Voice & Speech Technologies, Inc. (AVST) has released the AVST CX-S, a new product line of interoperable, enterprise-class unified communications solutions. These solutions are aimed at small-to-midsize busin […]
Dave is a self-proclaimed Telecommunications Contemplator. Most industry professionals gravitate toward the role of Analyst, Consultant or Journalist, but Dave blends all three as a professional Contemplator. He shares what he sees with the vendors, service providers, and end users. Learn More
Audio Comments
The fun part about blogging is the new people you get to meet and converse with. This happens in a variety of ways. Some people post comments, some write emails, some tweet, but recently I got my first voice message comment.
It was from Chris, a Telecom Specialist in North Carolina, whom I have not had the pleasure of meeting in person. This blog has a gadget that allows visitors to call. Chris called, and left me a voice mail. The voice mail was 2:22 long and was delivered as an audio file and a text file. Here is an excerpt:
This was using voice recognition software provided with the Google Voice service (voice mail transcription). As you can see, it isn’t perfect. Here is the revised version I created after listening to the message:
It is actually a little more clear in the Google Voice inbox because the more ify words are in gray and when you press the play button, the cursor highlights the text as it reads it. I don’t expect the voice recognition to be able to get the unspoken parentheses, but why can’t it capitalize the “i’ve” like a word processor can?
Anyway, the point is this blog is hosted by Blogger (yet another Google tentacle in my life). Why not offer a solution that allows the voice mail (with the audio, text, and play button) to be within the comments section?
It really doesn’t even have to be Google Voice. Companies like Twilio or Voxeo should be able to offer a widget like this (though unlikely for free).
This is the great part of UC, being able to apply the pieces into custom(izable) solutions offering new capabilities. The solutions can be from anywhere and be implemented anyplace where it makes sense.
There is no ROI in audio comments on my blog site (though clearly it would be nice), but the ability to take things like a voice mail recording and update an application has lots of potential. For example, a field tech that calls in to close a ticket – complete with reason codes and free form text. Lots of websites rely heavily on comments – such as Amazon (they even rate the comments) – why must contributors be forced to type?
There are speech recognition systems that work better than shown above. Of course, when you know what to expect, the systems get very accurate – like a “yes” or “no” choice. Free=from text is quite a bit trickier. One of the problems with Google Voice transcription is people don’t talk slowly and clearly to voice mail as they do when they know they are talking to a speech recognition system.
About Dave Michels
blogger, comments, google voice, speech recognition, UC