Browse Prior Art Database

System to process of voice calls and voicemails then displaying important details back to the user as actionable items after the call.

IP.com Disclosure Number: IPCOM000211510D
Publication Date: 2011-Oct-07
Document File: 2 page(s) / 24K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a system that displays details from incoming phone calls or voicemails as actionable items by buffering the call and using speech processing software to parse the voice call for a predefined set of details that a user specifies.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 2

System to process of voice calls and voicemails then displaying important details back to the user as actionable items after the call .

Voice calls and voicemails often contain difficult to remember details that users need after the call and in some instances the user is unable to remember or save these details while listening in real time. This invention solves this problem by displaying these details after the voice calls and voicemails in an actionable item that the user can process at their convenience. There are current inventions that can transcribe voice mails and allows the user to read the text such as Google Voice*. The current inventions out there do not do enough processing or intelligent mining for user specified information given user specific conditions. However, this invention allows the user to retrieve specific information instead of raw data and the information is presented back to the user as actionable items. This invention also allows the user to specify only processing

portions of the voice call instead the full call to save storage and not to overstress resources on the system. Below are some example use cases of this invention:

Use case #1: User Receive an incoming call and wants to retrieve a phone number from the call

Pre-conditions:


User has already configured the system to only store portion of the call. User defines storing trigger and ending trigger (# key for start, * key for end)

User defines the system to parse for phone numbers:


1) User picks up and talks normally.


2) User starts storing a portion of the call with the # key.


3) User ends storing of the call by pressing the * key.


4) User ends call and selects to process the portion of the call.


5) System process the stored portion of the call and looks for phone #s.


6) System displays these phones as contacts for user.


7) User takes action on these contacts (eg: storing, calling, etc..)

Use case #2: User Receive an incoming call and wants to retrieve a meeting location from the call

Pre-conditions:


User has already configured the system to only store portion of the call. User defines storing trigger and ending trigger (# key for start, * key for end)

User defines the system to parse for phone numbers:


1) User picks up and talks normally.


2) User starts storing a portion of the call with the # key.


3) User ends storing of the call by pressing the * key.


4) User ends call and selects to process the portion of the call.


5) System process the stored portion of the call and looks for meeting locations.


6) System displays these phones as contacts for user.


7) User takes actio...