Method and apparatus for managing multi-entity customer relations

• US 20060020507A1
• Filed: 07/21/2004
• Published: 01/26/2006
• Est. Priority Date: 07/21/2004
• Status: Abandoned Application

• Current Assignee: Richard W. Sagey
• Original Assignee: Richard W. Sagey
• Inventors: Sagey, Richard W.
• Application Number:
  US10/896,328
• Publication Number:
  US 20060020507A1
• Time in Patent Office: Days
• US Class Current: 705/14.360
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/0236 Incentive or reward received by requiring registration or ID from user
• CPC Class Codes: G06Q 30/0241 Advertisements

Abstract

Disclosed are a method and apparatus for managing customer relations programs amongst a plurality of entities. A first customer relations program is managed according to a customer identifier and a first entity identifier. A second customer relations program is managed according to the customer identifier and a second entity identifier.

Claims

1. A method for managing customer relations amongst a plurality of entities comprises:

managing a first customer relations program according to a customer identifier and a first entity identifier; and

managing a second customer relations program according to the customer identifier and a second entity identifier.

2. The method of claim 1 wherein managing a first customer relations program comprises:

defining an aggregate purchase level for an incentive for the first entity; and

maintaining an aggregate purchase tally according to a customer identifier and a first entity identifier.

3. The method of claim 1 wherein managing a first customer relations program comprises:

defining an aggregate visit level for an incentive for the first entity; and

maintaining an aggregate visit tally according to a customer identifier and a first entity identifier.

4. The method of claim 1 wherein managing a first customer relations program comprises associating a coupon with a customer identifier and a first entity identifier.

5. The method of claim 1 wherein associating a first customer relations program comprises:

receiving a transaction customer identifier for a customer transaction;

receiving an entity identifier for a first entity;

creating a tuple according to the transaction customer identifier and the entity identifier; and

associating a customer relations program with the tuple when the tuple is not yet associated with a customer relations program.

6. The method of claim 1 further comprising associating customer information with the customer identifier.

7. The method of claim 6 further comprising generating a promotional message to a customer according to the customer information.

8. The method of claim 6 further comprising directing a promotional message in the form of an electronic message to a customer according to the customer information.

9. The method of claim 6 further comprising conveying the customer information to an entity.

10. The method of claim 1 further comprising conveying customer status information associated with a customer identifier to an entity.

11. A system for managing customer relations amongst a plurality of entities comprising:

processor capable of executing an instruction sequence;

transaction interface capable of communicating with a transaction network;

memory; and

one or more instruction sequences stored in the memory including;

customer relations management module that, when executed by the processor, minimally causes the processor to;

manage a first customer relations program according to a customer identifier and a first entity identifier; and

manage a second customer relations program according to the customer identifier and a second entity identifier.

12. The system of claim 11 further comprising a network interface capable of communicating with a wide area network and wherein the customer relations manager module causes the processor to manage a first customer relations program by minimally causing the processor to:

accept an aggregate purchase level for an incentive by way of the network interface;

associate the accepted aggregate purchase level with a first entity identifier;

receive by means of the transaction interface a customer transaction message that includes the first entity identifier, a customer identifier and a purchase amount; and

maintain an aggregate purchase tally according to the first entity identifier, the customer identifier and the purchase amount.

13. The system of claim 11 wherein the customer relations manager module causes the processor to manage a first customer relations program by minimally causing the processor to:

accept an aggregate visit level for an incentive;

associate the accepted aggregate visit level with a first entity identifier;

receive by means of the transaction interface a customer transaction message that includes the first entity identifier and a customer identifier; and

maintain an aggregate visit tally according to the first entity identifier and the customer identifier.

14. The system of claim 11 wherein the customer relations manager module causes the processor to manage a first customer relations program by minimally causing the processor to:

accept a coupon definition; and

associate the coupon definition with a customer identifier and a first entity identifier.

15. The system of claim 11 wherein the customer relations manager module causes the processor to manage a first customer relations program by minimally causing the processor to:

receive by means of the transaction interface a customer transaction message that includes a first entity identifier and a customer identifier;

create a tuple according to the received first entity identifier and the customer identifier; and

associate a default customer relations program with the tuple when the tuple is not yet associated with a customer relations program.

16. The system of claim 11 further comprising a network interface capable of communicating with a wide area network and a customer information module that, when executed by the processor, minimally causes the processor to:

receive by means of the network interface customer information; and

associate the customer information with a customer identifier.

17. The system of claim 16 further comprising a print interface and a customer promotions dispatch module that, when executed by the processor, minimally causes the processor to:

generate a promotional message according to the customer information; and

convey the promotional message to the print interface.

18. The system of claim 16 further comprising a customer promotions dispatch module that, when executed by the processor, minimally causes the processor to convey by means of the network interface a promotional message to a customer an electronically deliverable message according to the customer information.

19. The system of claim 11 further comprising a network interface capable of communicating with a wide area network and a customer status dispatch module that, when executed by the processor, minimally causes the processor to convey to an entity by way of the network interface status information associated with a customer identifier.

20. A method for conducting a customer relations transaction comprising:

receiving a list of known customer identifiers from a multi-entity customer list;

receiving a transaction customer identifier; and

applying a customer relations program according to the transaction customer identifier when the transaction customer identifier is found in the list of known customer identifiers.

21. The method of claim 20 wherein receiving a transaction customer identifier comprises at least one of optically detecting a customer identifier, reading a magnetic stripe and determining a customer identifier according to a received electromagnetic signal.

22. The method of claim 20 wherein receiving a transaction customer identifier comprises:

receiving an arbitrary element of customer information; and

consulting the known list of customer identifiers using the arbitrary element of customer information in order to determine a customer identifier.

23. The method of claim 20 wherein applying a customer relations program comprises:

consulting the list of known customer identifiers according to the transaction customer identifier to determine customer incentive status; and

applying a customer incentive to a transaction according to the determined customer incentive status.

24. The method of claim 23 wherein applying a customer incentive comprises:

determining a customer-specific aggregate purchase tally according to the customer incentive status; and

applying a customer privilege when the customer-specific aggregate purchase tally is greater than a pre-established amount.

25. The method of claim 23 wherein applying a customer incentive comprises:

determining a customer-specific aggregate visit tally according to the customer incentive status; and

applying a customer privilege when the customer-specific aggregate visit tally is greater than a pre-established amount.

26. The method of claim 23 wherein applying a customer incentive comprises:

determining the availability of a coupon according to the customer incentive status; and

applying the coupon to the transaction when coupon redemption is selected.

27. The method of claim 23 further comprising updating the customer incentive status according to the transaction customer identifier and particulars of a transaction.

28. The method of claim 20 further comprising:

adding the transaction customer identifier to the list of known customer identifiers when the customer identifier is not found in the list of known customer identifiers; and

conveying the transaction customer identifier to a multi-entity customer relations management system.

29. The method of claim 20 further comprising applying a bonus customer relations program according to the transaction customer identifier when the transaction customer identifier is found in the list of known customer identifiers and the list of known customer identifiers indicates that the transaction customer identifier is registered.

30. A multi-entity aware customer transaction terminal comprising:

processor capable of executing an instruction sequence;

network interface capable of communicating with a wide area network;

transaction interface capable of communicating with a transaction network;

transaction customer identification unit;

display capable of presenting a customer incentive instruction;

memory capable of storing one or more instruction sequences; and

one or more instructions stored in the memory including;

customer list reception module that, when executed by the processor, minimally causes the processor to receive a list of known customer identifiers from a multi-entity customer list and store the list of known customers in the memory;

customer identification module that, when executed by the processor, minimally causes the processor to receive a transaction customer identifier by way of the transaction customer identification unit; and

incentive award module that, when executed by the processor, minimally causes the processor to direct to the display an incentive according to information included in the known customer list when the received transaction customer identifier is found in the known customer list.

31. The transaction terminal of claim 30 wherein the transaction customer identification unit comprises a bar-code reader and wherein the customer identification module includes a bar-code driver that, when executed by the processor, minimally causes the processor to retrieve a customer identifier from the bar-code reader.

32. The transaction terminal of claim 30 wherein the transaction customer identification unit comprises a magnetic stripe reader and wherein the customer identification module includes a magnetic stripe driver that, when executed by the processor, minimally causes the processor to retrieve a customer identifier from the magnetic stripe reader.

33. The transaction terminal of claim 30 wherein the transaction customer identification unit comprises a radio frequency identification transponder reader and wherein the customer identification module includes a frequency identification transponder driver that, when executed by the processor, minimally causes the processor to retrieve a customer identifier from the frequency identification transponder reader.

34. The transaction terminal of claim 30 wherein the transaction customer identification unit comprises a keyboard and wherein the customer identification module includes a keyboard driver that, when executed by the processor, minimally causes the processor to retrieve an arbitrary element of customer information and further wherein the customer identification module minimally causes the processor to determine a customer identifier by searching for a record in the received known customer list that includes the arbitrary element of customer information.

35. The transaction terminal of claim 30 wherein the incentive award module causes the processor to apply an incentive by minimally causing the processor to:

retrieve from the list of known customer identifiers stored in the memory a customer incentive status according to a transaction customer identifier; and

apply a customer incentive according to the customer incentive status.

36. The transaction terminal of claim 35 wherein the incentive award module includes an aggregate purchase tally module that, when executed by the processor, minimally causes the processor to apply a customer incentive by minimally causing the processor to:

determine a customer-specific aggregate purchase tally according to the customer incentive status; and

apply a customer privilege when the customer-specific purchase tally is greater than a pre-established amount.

37. The transaction terminal of claim 35 wherein the incentive award module includes an aggregate visit tally module that, when executed by the processor, minimally causes the processor to apply a customer incentive by minimally causing the processor to:

determine a customer-specific aggregate visit tally according to the customer incentive status; and

apply a customer privilege when the customer-specific visit tally is greater than a pre-established amount.

38. The transaction terminal of claim 35 wherein the incentive award module includes a coupon module that, when executed by the processor, minimally causes the processor to apply a customer incentive by minimally causing the processor to:

determine the availability of a coupon according to the customer incentive status; and

apply the coupon to a transaction when coupon redemption is selected.

39. The transaction terminal of claim 35 wherein the incentive award module further minimally causes the processor to:

convey the particulars of a transaction and a corresponding customer identifier to the transaction interface.

40. The transaction terminal of claim 30 wherein the customer identification module, when executed by the processor, further minimally causes the processor to:

add the customer transaction identifier to the list of known customer identifiers when the customer identifier is not found in said list of known customer identifiers; and

convey the transaction customer identifier to a multi-entity customer relations management system by way of the network interface.

41. The transaction terminal of claim 30 wherein the incentive award module further minimally causes the processor to apply a bonus customer relations program according to the transaction customer identifier when the transaction customer identifier is found in the list of known customer identifiers and the list of known customer identifiers indicates that the transaction customer identifier is registered.