MESSAGE PROCESSING SYSTEM

• US 20150004949A1
• Filed: 06/23/2014
• Published: 01/01/2015
• Est. Priority Date: 06/28/2013
• Status: Abandoned Application

• Current Assignee: Callplease LLC
• Original Assignee: Callplease LLC
• Inventors: Ludewig, Carl, Fienberg, Gregg D., Ryan, Rhys
• Application Number:
  US14/312,408
• Publication Number:
  US 20150004949A1
• Time in Patent Office: Days
• US Class Current: 455/414.1
• CPC Class Codes: H04M 2203/551 Call history recording a computer conference H04L12/1831
• CPC Class Codes: H04M 3/42136 Administration or customisation of services
• CPC Class Codes: H04M 3/5231 with call back arrangements

Abstract

A system and method for synchronizing data across multiple mobile platforms. Certain embodiments employ a server operating to receive from a first remote device, call action information, test that call action for prior reception of the same information, store the information in a structured data store in response to said testing, transmit a push notification to a second remote device, wait for a response from the second remote device, and transmit the call action to the second remote device based on the response. The remote devices may be cell phones, laptops, tablets and the like and the call actions may include work processes like docketing, sales functions and technical support information.

Claims

1. A method including:

receiving from a first remote device, information, said information including a call action;

testing that call action for prior reception of the same information;

storing the information in a structured data store in response to said testing;

transmitting a push notification to a second remote device;

waiting for a response from the second remote device, and

transmitting the call action to the second remote device based on the response.

2. The method of claim 1 wherein the second remote device is selected from a predetermined collection of remote devices.

3. The method of claim 1 wherein the call action is selected from a queue stored on the first remote device.

4. The method of claim 1 wherein the call action includes an information representing at least one of a call received, a message received, or a request to call.

5. The method of claim 1 wherein the first remote device and the second remote device are wireless devices.

6. The method of claim 1 further including:

testing the call action against a rules lookup table, and

altering the call action in response to the testing.

7. The method of claim 1 wherein the call action includes information representing at least one of a customer request, a sales call, or a technical request.

8. One or more processor readable storage devices having processor readable, non-transitory, code embodied on said processor readable storage devices, said processor readable code for programming one or more processors to perform a method including:

receiving from a first remote device, information, said information including a call action;

testing that call action for prior reception of the same information;

storing the information in a structured data store in response to said testing;

transmitting a push notification to a second remote device;

waiting for a response from the second remote device, and

transmitting the call action to the second remote device based on the response.

9. The device of claim 8 wherein the second remote device is selected from a predetermined collection of remote devices.

10. The device of claim 8 wherein the call action is selected from a queue stored on the first remote device.

11. The device of claim 8 wherein the call action includes an indicia representing at least one of a call received, a message received, or a request to call.

12. The device of claim 8 wherein the first remote device and the second remote device are wireless devices.

13. The device of claim 8 wherein the method further includes:

testing the call action against a rules lookup table, and

altering the call action in response to the testing.

14. The device of claim 8 wherein the call action includes information representing at least one of a customer request, a sales call, or a technical request.