IP Library Granted Patent US 10,489,748
Granted Patent B2
US 10,489,748 · App. 15/552,077 · Granted Nov 26, 2019

Managing the generation of text messages

Inventors: Ben Brophy (Crows Nest, AU); Shane Berkinshaw (Crows Nest, AU)
Assignee: Upwire Pty Ltd.
G06Q10/107G06F3/0482G06F3/0486G06F8/38G06Q10/06H04L51/04H04L51/28H04W4/14
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,489,748
App. No.
15/552,077
Granted
Nov 26, 2019
Kind
B2
Abstract

This disclosure relates to sending electronic messages, including SMS, voice and email messages. A processor generates a graphical user interface with multiple message types as options to a user, and with multiple functional features for each of the multiple message types. The user selects message types and functional features for the message types. The processor stores a template as one of multiple templates associated with a template identifier. The template comprises data indicative of the selected message types and the selected functional features. Received message generation request data comprises addresses associated with a template identifier. The processor selects a second template from the multiple templates such that the second template is associated with the template identifier and creates for each of the message addresses an electronic message and sends each electronic message to the associated message address.

Claims (42)

1. A method for sending electronic messages, the method comprising:

generating a graphical user interface, the graphical user interface comprising:

a first user input element to present multiple message types as options to a user, and

a second user input element to present multiple functional features for the multiple message types to the user;

wherein one or more of the first user element and the second user element comprise drag and drop items;

receiving user input in relation to the graphical user interface indicative of a drag and drop of a first message type of the multiple message types, creating an instance of the first message type on the graphical user interface;

receiving user input in relation to the graphical user interface indicative of a drag and drop of a first functional feature of the multiple functional features in relation to the first message type;

creating an instance of the first functional feature connected to the first message type on the graphical user interface including multiple connectors, each of the multiple connectors representing a different possible output of the first functional feature;

receiving user input in relation to the graphical user interface indicative of a drag and drop of a second message type of the multiple message types;

creating an instance of the second message type on the graphical user interface;

receiving user input in relation to the graphical user interface indicative of a connection between one of the multiple connectors and the second message type;

storing a first template as one of multiple templates on a data store associated with a template identifier, the first template comprising data indicative of the first and second message types, the first functional feature and the connection;

receiving message generation request data, the message generation request data comprising one or more message addresses associated with the template identifier;

selecting a second template from the multiple templates, wherein the second template is associated with the template identifier;

creating for each of the one or more message addresses an electronic message associated with that message address; and

sending each electronic message to the associated message address.

2. The method of claim 1 , further comprising receiving scheduling data, wherein sending each electronic message comprises determining a schedule for sending each message based on the scheduling data.

3. The method of claim 2 , wherein receiving scheduling data comprises one or more of receiving scheduling data from the user through the graphical user interface; and receiving scheduling data as part of the message generation request data.

4. The method of claim 2 , wherein the scheduling data comprises data indicative of a time window for sending the electronic messages.

5. The method of claim 2 , wherein the scheduling data comprises data indicative of a starting time for sending the electronic messages.

6. The method of claim 2 , further comprising determining an association between a message address and a time zone wherein determining a schedule for sending each message is based on the time zone, wherein determining the association between the message address and the time zone comprises determining a prefix of a telephone number.

7. The method of claim 1 , wherein receiving message generation request data comprises receiving an incoming phone call at an incoming telephone number and the incoming telephone number is the template identifier.

8. The method of claim 1 , wherein sending each electronic message comprises creating a job item for each electronic message and storing the job item in a job queue.

9. The method of claim 1 , wherein the message generation request data is one or more of XML and JSON data and the method further comprises determining the template identifier based on the one or more of XML and JSON data.

10. The method of claim 1 , wherein sending the electronic messages comprises determining a destination country and a route comprising a telecommunications provider of the destination country.

11. The method of claim 1 , wherein the graphical user interface further comprises a third user input element to present one or more options for relating the message types to the functional features to the user and the method further comprises receiving user input in relation to the third user input element indicative of one or more selected relations that relate the message types to the functional features.

12. The method of claim 11 , wherein the selected relation is a conditional element and the method further comprises receiving user input indicative of a condition to configure the selected relation.

13. The method of claim 12 , further comprising receiving user input in relation to the first message type to relate a status connector representing a status of sending the first message type to a conditional relation.

14. The method of claim 1 , wherein generating the graphical user interface comprises generating the graphical user interface comprising a first page and a second page, wherein the first user input element is located on the first page and the second user input element is located on the second page.

15. The method of claim 1 , further comprising: generating a document editor user interface comprising multiple document features; receiving user input in relation to the document editor user interface indicative of one or more selected document features; and storing multiple documents, wherein each of the multiple documents represents the user input in relation to the document editor user interface and is in a different document format.

16. The method of claim 1 , further comprising applying a filter to the one or more message addresses and the filter is based on user input data.

17. A non-transitory computer readable medium that has an executable program stored thereon that when executed causes a computer to perform the method of claim 1 .

18. A system for sending messages, the system comprising:

a processor to generate a graphical user interface, the graphical user interface comprising:

a first user input element to present multiple message types as options to a user, and a second user input element to present multiple functional features for one or more of the multiple message types to the user;

wherein one or more of the first user element and the second user element comprise drag and drop items;

a first input port to receive user input in relation to the graphical user interface indicative of a drag and drop of a first message type of the multiple message types, receiving user input in relation to the graphical user interface indicative of a drag and drop of a first functional feature of the multiple functional features in relation to the first message type, receive user input in relation to the graphical user interface indicative of a drag and drop of a second message type of the multiple message types, and receive user input in relation to the graphical user interface indicative of a connection between one of multiple connectors and the second message type;

wherein an instance of the first functional feature connected to the first message type on the graphical user interface including the multiple connectors, and each of the multiple connectors representing a different possible output of the first functional feature;

a data store to store a first template as one of multiple templates associated with a template identifier, the first template comprising data indicative of the first and second message types, the first functional feature and the connection;

a second input port to receive message generation request data, the message generation request data comprising one or more message addresses associated with the template identifier:

the processor to select a second template from the multiple templates, wherein the second template is associated with the template identifier, and to create for each of the one or more message addresses a message associated with that message address; and

an output port to send each message to the associated message address.

Assignments (2)
CHANGE OF NAME Recorded Nov 16, 2017
From: ZYNC PTY LTD
To: UPWIRE PTY LTD
Reel/Frame 044152/0861 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 1, 2017
From: BROPHY, BEN; BERKINSHAW, SHANE
To: ZYNC PTY LTD
Reel/Frame 044010/0109 →
Priority Claims (2)
AU 2015900556 · Feb 18, 2015 · national
AU 2015904827 · Nov 23, 2015 · national
Continuity (1)
Related Publication 20180046984A1 · Feb 15, 2018