Message distribution system
AssigneeNone recorded
InventorsThomas James Newell, Bradley Jacob Nathan, David Justin Bergert, Richard Shannon Smith
Life of this patent
Estimating the term…
Loading patent…
AssigneeNone recorded
InventorsThomas James Newell, Bradley Jacob Nathan, David Justin Bergert, Richard Shannon Smith
Estimating the term…
The invention is a message distribution system that can deliver a single message to a large number of people with a single act using a group of computer servers. The preferred embodiment requires the user to establish an account using a website and enter a contact list. The contact list can include both email addresses and telephone numbers. When the user wishes to send a message, at a later time, the user contacts the group of computer servers by a telephone number or email address. The user records a message on the servers and the server sends the messages to all email addresses and telephone numbers on the contact list for that user. Other embodiments include procedures to confirm the validity of the email addresses and telephone numbers and to confirm the delivery of messages to the email address and telephone numbers on the contact list.
A message distribution system comprising:
Dependencies are inferred from the claim text.
Drawings are temporarily unavailable. Open the PDF at USPTO
From the US filing history. Foreign family members aren’t listed.
Message disposing or creating aspects: message broadcasting
User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail: unified…
Message adaptation to terminal or network requirements: format adaptation, e.g. format conversion or compression
Related to features of supplementary services: call initiation by network rather than by subscriber
About 3 years 8 months of term left · ends 30 Jun 2030 (estimated)
None
None
This invention relates to message systems. More specifically it relates to automatic message systems. Even more specifically it relates to automatic message systems that allows users to distribute emergency voice messages to family members.
The accompanying drawings, which are incorporated in and form part of the specification, illustrate the embodiments of the present invention and, together with the description, serve to explain the principles of the invention.
FIG. 1 illustrates the registration stage flowchart.
FIG. 2 illustrates the distribution stage flowchart.
FIG. 1 illustrates the registration stage flowchart. This flow chart describes the process by which the invention registers a new user. In step 1, the user contacts the computer server that is operating the invention by a website or phone number. Then, in step 2, the server asks the user to enter basic information such as name, phone number and email address. Then, in step 3, the server asks the user to select a service plan. If the user does not select a service plan, the invention terminates. If the user selects a service plan, then the invention goes to step 4 and asks the user to submit billing information. Then, in step 5, the server submits the order. Then, in step 6, the user receives verification that the order has been submitted. Then, in step 7, the user enters a person to be added to that user's distribution list. Then, in step 8, the server asks the user to enter contact information for that person, including at least a phone number or an email address, or both. Then, in step 9, the server offers the user to option to add another person to the distribution list. If the user elects to add another person, the invention returns to step 7 and add another person and the contact information. If the user elects not to add another person, the invention ends its process. The user can access his account through a website using his account number and enters more contact information at a later time.
FIG. 2 illustrates the distribution stage flowchart. This flowchart describes the process by which the invention distributes a message to the persons on the distribution list. In step 21, the user dials a toll free access number. Then in step 22, the user is prompted to enter an account number and the user enters an account number. Then, in step 23, the user records a message with a voice recording software. Then, in step 24, the server sends that message to each phone number and email address on the user's distribution list. Thus, in step 25, the message is delivered to all the people on the distribution list.
FIG. 3 illustrates the automated confirmation of contact information stage flowchart. This flow describes the process by which the invention confirms the contact information on each user's distribution list. In step 11, the computer server dials the phone number for each person on the predetermined list. Then, in step 12, the phone server uses an outbound call using interactive voice recognition software (IVR). Then, in step 13, a text to speech program reads the email address for that phone number to the person the server called. Then, in step 14, the IVR processes the response from the person and converts the speech into text. Then in step 15, the IVR system confirms that the phone number and email address are correct using a text to speech program. Also, in step 16, the server sends the person an email with the person's phone number to confirm that the email address and phone number are correct. This email can be sent while the person is on the phone, or this email can be sent later when the person has hung up the phone. Then, in step 17, the person determines if the phone number and the email address are correct. If the person states that information is correct then the invention advances to step 18. If the person states that information is not correct, the invention returns to step 13. In step 18, the server writes the phone number and email address into the database of the server for that user's distribution list. Then in step 19, the server sends a written confirmation that the phone number of the email has been confirmed to both the user and the person on the user's distribution list. Alternatively, the server can send a written confirmation to either the user or the person.