WO2013116708A1 - Programmes d'incitation commerciale basés sur un nuage - Google Patents

Programmes d'incitation commerciale basés sur un nuage Download PDF

Info

Publication number
WO2013116708A1
WO2013116708A1 PCT/US2013/024422 US2013024422W WO2013116708A1 WO 2013116708 A1 WO2013116708 A1 WO 2013116708A1 US 2013024422 W US2013024422 W US 2013024422W WO 2013116708 A1 WO2013116708 A1 WO 2013116708A1
Authority
WO
WIPO (PCT)
Prior art keywords
customer
code
information
loyalty
voucher
Prior art date
Application number
PCT/US2013/024422
Other languages
English (en)
Inventor
Greg DEMETRIADES
Original Assignee
Clk Clk, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Clk Clk, Inc. filed Critical Clk Clk, Inc.
Publication of WO2013116708A1 publication Critical patent/WO2013116708A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/20—Point-of-sale [POS] network systems
    • G06Q20/202—Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/387—Payment using discounts or coupons
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions

Definitions

  • the instant disclosure relates to sales devices.
  • the instant disclosure more specifically relates to a cloud-based sales system incorporating a customer loyalty program.
  • stamp card which allows a customer a collect stamps for purchasing certain items. When enough stamps are collected, the stamp card may be traded in for a discount or a free item. Stamp cards suffer similar drawbacks to mailed coupons.
  • Social media may be used to improve customer retention rates and improve customer referral rates by providing customers both the opportunity and incentive to share their experience at a business with others. For example, customers may be offered an opportunity to refer others to the business. In another example, customers may be offered an opportunity to review the business or review products purchased at the business or services consumed from the business. In exchange for referrals and reviews, incentives may be provided to the customer. The incentives, such as discounts and vouchers, may be defined by the business.
  • Tracking of the incentives and of the use of social media may be performed by a cloud-based system remote from the point-of-sale devices at the business.
  • the cloud-based system may communicate with the point-of-sale devices to receive registration information and/or transaction information for a customer.
  • the cloud-based system may interact with the customer when the customer is not present at the business. For example, the cloud-based system may provide a web-based portal for the customer to review and rate recent transactions and earn incentives that may later be redeemed at the business.
  • a point balance may be linked to a card issued to a student or may be linked to a student ID card already issued to a student by the school.
  • the card may provide points for on-time attendance, paying attention in class, managing time, academic progress, and/or completing courses. Students may then redeem the points for gift cards at participating merchants.
  • a method includes receiving, from a point-of-sale device, information for a transaction completed by a customer of a business.
  • the method also includes providing the customer with an opportunity to electronically review the transaction.
  • the method further includes receiving a review of the transaction.
  • the method also includes storing the review in a cloud-based customer loyalty system, which may be separate from the point-of-sale device.
  • the method further includes providing loyalty rewards to the customer after receiving the review.
  • an apparatus includes a memory storing a customer-loyalty database.
  • the apparatus also includes a network interface for communicating with a point-of-sale system.
  • the apparatus further includes a processor coupled to the memory and coupled to the network interface.
  • the processor is configured to receive, from the point-of-sale device, information for a transaction completed by a customer of a business.
  • the processor is further configured to provide the customer with an opportunity to electronically review the transaction.
  • the processor is also configured to receive a review of the transaction.
  • the processor is further configured to store the review in a cloud-based customer loyalty system, which may be separate from the point-of-sale device.
  • the processor is also configured to provide loyalty rewards to the customer after receiving the review.
  • a computer program product includes a non-transitory computer readable medium having code to receive, from a point-of-sale device, information for a transaction completed by a customer of a business.
  • the medium also includes code to provide the customer with a link to electronically review the transaction.
  • the medium further includes code to receive a review of the transaction.
  • the medium also includes code to store the review in a cloud- based customer loyalty system, which may be separate from the point-of-sale device.
  • the medium further includes code to provide loyalty rewards to the customer after receiving the review.
  • a method includes receiving, at a device, information regarding a customer. The method also includes transmitting, to a server, the customer information. The method further includes receiving, from the server, information regarding a loyalty program enrolled in by the customer, wherein the loyalty program information includes a world dollar balance and a loyalty dollar balance. The method also includes displaying, at the device, the loyalty program information.
  • a computer program product includes a non-transitory computer readable medium having code to receive, at a device, information regarding a customer.
  • the medium also includes code to transmit, to a server, the customer information.
  • the medium further includes code to receive, from the server, information regarding a loyalty program enrolled in by the customer, wherein the loyalty program information includes a world dollar balance and a loyalty dollar balance.
  • the medium also includes code to display, at the device, the loyalty program information.
  • an apparatus includes a memory and a processor coupled to the memory, in which the processor is configured to receive information regarding a customer.
  • the processor is also configured to transmit the customer information.
  • the processor is further configured to receive information regarding a loyalty program enrolled in by the customer, wherein the loyalty program information includes a world dollar balance and a loyalty dollar balance.
  • the processor is also configured to display the loyalty program information.
  • FIGURE 1 is a block diagram illustrating a server configuration for operating the cloud-based customer loyalty program according to one embodiment of the disclosure.
  • FIGURE 2 is a block diagram illustrating a ticket database according to one embodiment of the disclosure.
  • FIGURE 3 is a block diagram illustrating access points for a customer to access the cloud-based customer loyalty program according to one embodiment of the disclosure.
  • FIGURE 4 is a block diagram illustrating an information system for storing customer data in a cloud-based customer loyalty system according to one embodiment of the disclosure.
  • FIGURE 5 is a block diagram illustrating a computer system according to one embodiment of the disclosure.
  • FIGURE 6 is a flow chart illustrating a method of rewarding customers for reviewing products according to one embodiment of the disclosure.
  • FIGURE 7 is a graphic illustrating a sample opportunity presented to a customer to review products purchased during a transaction with the business according to one embodiment of the disclosure.
  • FIGURE 8 is a graphic illustrating a sample review completed by a customer according to one embodiment of the disclosure.
  • FIGURE 9 is graphic illustrating other methods for earning reward dollars through a customer loyalty program according to one embodiment of the disclosure.
  • FIGURES 10A-D are graphic illustrations of a user interface for managing a customer account in a cloud-based customer loyalty program according to one embodiment of the disclosure.
  • FIGURE 11 is a graphic illustration of a coupon generated by the cloud-based customer loyalty program according to one embodiment of the disclosure.
  • FIGURE 12 is an illustration of a social media application for accessing the cloud-based customer loyalty program according to one embodiment of the disclosure.
  • FIGURE 13 is an illustration of a social media application settings screen according to one embodiment of the disclosure.
  • FIGURE 14 is an illustration of a kiosk welcome screen according to one embodiment of the disclosure.
  • FIGURE 15 is an illustration of a kiosk login screen according to one embodiment of the disclosure.
  • FIGURE 16 is an illustration of a kiosk PIN recovery screen according to one embodiment of the disclosure.
  • FIGURE 17 is an illustration of a goal tracking screen according to one embodiment of the disclosure.
  • FIGURE 18 is an illustration of a voucher redemption screen according to one embodiment of the disclosure.
  • FIGURE 19 is an illustration of balance information screen according to one embodiment of the disclosure.
  • FIGURE 20 is an illustration of an automatic loyalty program screen according to one embodiment of the disclosure.
  • FIGURE 21 is an illustration of an employee login screen according to one embodiment of the disclosure.
  • FIGURE 22 is an illustration of a customer note screen according to one embodiment of the disclosure.
  • FIGURE 23 is an illustration of a new transaction screen according to one embodiment of the disclosure.
  • FIGURE 24 is an illustration of a leaderboard screen according to one embodiment of the disclosure.
  • FIGURE 25 is an illustration of a mobile kiosk welcome screen according to one embodiment of the disclosure.
  • FIGURE 26 is an illustration of a mobile kiosk login screen displayed to a customer according to one embodiment of the disclosure.
  • FIGURE 27A is an illustration of a mobile kiosk first-step registration screen according to one embodiment of the disclosure.
  • FIGURE 27B is an illustration of a mobile kiosk second-step registration screen according to one embodiment of the disclosure.
  • FIGURE 27C is an illustration of a mobile kiosk third-step registration screen according to one embodiment of the disclosure.
  • FIGURE 27D is an illustration of a mobile kiosk fourth-step registration screen according to one embodiment of the disclosure.
  • FIGURE 28 is an illustration of a mobile kiosk login screen according to one embodiment of the disclosure.
  • FIGURE 29 is an illustration of a mobile kiosk home screen according to one embodiment of the disclosure.
  • FIGURE 30A is an illustration of a mobile kiosk loyalty screen according to one embodiment of the disclosure.
  • FIGURE 30B is an illustration of a mobile kiosk voucher purchase screen according to one embodiment of the disclosure.
  • FIGURE 30C is an illustration of a mobile kiosk loyalty balance screen according to one embodiment of the disclosure.
  • FIGURE 30D is an illustration of a mobile kiosk voucher screen according to one embodiment of the disclosure.
  • FIGURE 31 is an illustration of a mobile kiosk send dollars screen according to one embodiment of the disclosure.
  • FIGURE 32A is an illustration of a mobile kiosk merchant spotlight screen according to one embodiment of the disclosure.
  • FIGURE 32B is an illustration of a mobile kiosk loyalty spotlight screen according to one embodiment of the disclosure.
  • FIGURE 33 is an illustration of a mobile kiosk send dollar screen according to one embodiment of the disclosure.
  • FIGURE 34 is an illustration of a mobile kiosk merchant home according to one embodiment of the disclosure.
  • FIGURE 35A is an illustration of a mobile kiosk merchant loyalty screen according to one embodiment of the disclosure.
  • FIGURE 35B is an illustration of a mobile kiosk merchant loyalty second-step screen according to one embodiment of the disclosure.
  • FIGURE 35C is an illustration of a mobile kiosk merchant loyalty third-screen according to one embodiment of the disclosure.
  • FIGURE 35D is an illustration of a mobile kiosk merchant loyalty fourth-screen according to one embodiment of the disclosure.
  • FIGURE 36 is an illustration of a mobile kiosk merchant voucher search screen according to one embodiment of the disclosure.
  • FIGURE 37 is an illustration of a mobile kiosk merchant transaction screen according to one embodiment of the disclosure.
  • FIGURE 38A is an illustration of a mobile kiosk first- step merchant transaction screen according to according to one embodiment of the disclosure.
  • FIGURE 38B is an illustration of a mobile kiosk second-step merchant transaction screen according to one embodiment of the disclosure.
  • FIGURE 38C is an illustration of a mobile kiosk merchant transaction screen with auto-complete search field according to one embodiment of the disclosure.
  • FIGURE 1 is a block diagram illustrating a server configuration for operating the cloud-based customer loyalty program according to one embodiment of the disclosure.
  • a network 100 may include point-of-sales (POS) terminals 102 located in a physical store.
  • the POS terminals 102 may be coupled to POS servers 104 located within the physical store and/or at a location separate from the physical store.
  • the POS servers 104 may also be software executing on a single computer along with terminal software, which would be present on the POS terminals 102.
  • the POS terminals 102 and POS servers 104 may interface with a cloud-based customer loyalty system 110 over a network 130, such as the Internet.
  • the interface may be provided by software installed on the POS servers 104 and/or the POS terminals 102.
  • the cloud-based customer loyalty system 110 may include an application 112, which accesses databases 114, 116, and 118.
  • the system 110 is cloud- based, because the application 112 is hosted on servers separate from the terminals 102 and the servers 104.
  • the POS terminals 102 and POS servers 104 may have no information about or participate in the operation of the system 110.
  • the POS terminals 102 and POS servers 104 interact with the system 110 through an application interface, which does not change whether the system 110 is on a single server connected to the Internet or multiple servers geographically dispersed across the Internet.
  • the cloud-based customer loyalty system may be deployed, maintained, and upgraded with little disruption to services provided to the POS terminals 102 and POS servers 104.
  • customers are offered greater flexibility. For example, when the customer loyalty program is cloud-based, a customer may link multiple businesses to a single account in the customer loyalty program. With fewer cards and log-ins to remember, a customer is more likely to actively participate in the customer loyalty program.
  • the database 114 may store ticket information received from the POS servers 104 and/or POS terminals 102.
  • the database 114 may store customer information and a list of items purchased by a customer.
  • the database 116 may be an online transaction processing (OLTP) database for providing rapid access to transactions from the other servers.
  • the database 116 may store reward information, such as point and money balances, for customers corresponding to some or all of the customers in the database 114.
  • the database 118 may be an online analytical processing (OLAP) and reporting database.
  • the database 118 may store statistical information regarding the customers, such as a referral rate and how different customers use the rewards program.
  • databases 114, 116, and 118 are illustrated as separate databases, the databases 114, 116, and 118 may be implemented in a single database on a single server.
  • the databases 114, 116, and 118 may be implemented in a MongoDB database, a MySQL database, a SQL database, or the like.
  • the cloud-based customer loyalty system 110 may also interface with other servers, such as a short message system (SMS) server 122 and a coupon generator server 124.
  • SMS server 122 may provide capabilities to the cloud-based customer loyalty system 110 permitting short messages to be transmitted to mobile phones. For example, when a new purchase is made at the POS terminal 102 by a customer, the transaction may be passed to the application 112, which instructs the SMS server 122 to send a reminder message to the customer to review the purchased product online.
  • the coupon generator server 124 may generate coupons and/or certificates for customers accessing the application 112 and participating in the cloud-based customer loyalty program.
  • the customer may request a coupon from the application 112, which instructs the coupon generator server 124 to generate the coupon.
  • the SMS server 122 and the coupon generator server 124 are illustrated as different servers, the servers 122 and 124 may be separate applications executing on a single server along with the application 112.
  • the application 112 provides an interface, such as a control panel 132, to allow administration of the application 112, the databases 114, 116, 118, and/or the servers 122 and 124.
  • the control panel 132 may be accessed by administrators, such as managers of the stores participating in the cloud-based customer loyalty program.
  • the control panel allows the administrators to set configurations, such as rewards for different reward dollar levels and how and how many reward dollars are earned for certain customer activities.
  • the control panel may also display real-time statistics regarding their customers and marketing campaigns.
  • the control panel may also interface with other components of a back office system for tracking accounts, contacts, leads, meetings, and/or tasks.
  • Data from the POS terminals 102 and POS servers 104 may be transmitted in near real-time through a network interface to the application 112.
  • the POS terminals 102 may execute a routine that forwards each completed purchase through an application program interface (API) on the POS terminals 102 to the application 112.
  • Data may also be transferred between the POS terminals 102 and POS servers 104 and the application 112 in lump-sum arrangements.
  • a data file 142 exported from the POS terminals 102 and/or the POS servers 104 may be uploaded to a file transfer protocol (FTP) server 144 accessible by the application 112.
  • the application 112 may download the data file 142 at scheduled times.
  • the application 112 may download the data file 142 from the FTP server 144 each night at midnight.
  • the application 112 may download the data file 142 from the FTP server 144 each Sunday or on the first of each month.
  • FTP file transfer protocol
  • FIGURE 2 is a block diagram illustrating a ticket database according to one embodiment of the disclosure.
  • a database 200 may include a number of tables 202, 204, 206, 208, 210, 212, 214, and/or 216.
  • the PromoCodes table 202 may store promotion codes specific to a particular business identified by a BusinessID.
  • the promotion code information may include a creation date, an expiration date, and/or an identification of a product for discount and the amount of the discount.
  • the Discountltem table 204 may store details of the promotion identified in the PromoCodes table 202 by a DiscountltemlD.
  • the TicketSummary table 206 may store information regarding receipts for items purchased by customers.
  • the table 206 may include fields for storing a store identification where the purchase originated, an employee (not shown) at the store credited for completing the sale, and purchase price information along with promotions applied to the purchase.
  • the Business table 208 identifies the businesses participating in the cloud-based customer loyalty program and associates the business with a BusinessID linked to other tables, such as the TicketSummary table 206.
  • Contacts for each business in the Business table 208 may be stored in the BusinessContact table 210, which stores information such as phone numbers, emails, and login information for contacts at each business.
  • the Customer table 216 may store identification information, such as a phone number, for customers of the businesses participating in the cloud-based customer loyalty system. Each customer may be assigned a CustomerlD linked to information stored in the CustomerHistory table 214 and the OptOut table 212.
  • the OptOut table 212 may indicate whether a particular customer has opted out of communications with the business and/or has opted out of the cloud-based referral program.
  • the CustomerHistory table 214 may store information regarding recent purchases, recent use of promotional codes, and/or recent use of rewards dollars by a customer.
  • FIGURE 3 is a block diagram illustrating access points for a customer to access the cloud-based customer loyalty program according to one embodiment of the disclosure.
  • a network 300 includes a network 302, such as the Internet, providing access to a server 304 hosting the cloud-based customer loyalty application and a coupon generator server 306.
  • the server 304 and the server 306 may interface through an application program interface (API) and may be located on the same physical server or two separate servers. According to one embodiment, the server 304 and the server 306 may be operating as virtual servers on a single physical server.
  • the server 304 and/or the server 306 may have a connection to a database 308.
  • the database 308 may be connected to the network 302 and accessible to the server 304 and/or the server 306.
  • Users may access the cloud-based customer loyalty application hosted on the server 304 through user interfaces available to computers 312 and mobile devices 314.
  • the user interface may provide access to account details including previous purchases, marketing opt-ins, reward dollars earned, and/or coupons available for purchase with reward dollars.
  • an application may execute on the computers 312 through the Windows operating system or Macintosh operating system.
  • a web-based application may be presented through a browser on the computers 312.
  • Users may also access the server 304 through applications on the mobile devices 314, such as Android and iPhone devices.
  • the mobile devices 314 may also present information through a browser, such as a wireless application protocol (WAP) browser.
  • WAP wireless application protocol
  • a direct e-mail campaign 316 may deliver information directly to customers, even those who have not previously established an account with the cloud-based referral system.
  • a business may email all of its customers and provide a link to download an application as described with reference to the computers 312 and the mobile devices 314.
  • the email from the business may include a link to a web page that accesses the cloud-based referral system and allows customers to create an account on the server 304.
  • FIGURE 4 illustrates one embodiment of a system 400 for an information system, such as a system for storing customer data in a cloud-based customer loyalty system.
  • the system 400 may include a server 402, a data storage device 406, a network 408, and a user interface device 410.
  • the server 402 may be a dedicated server or one server in a cloud computing system.
  • the system 400 may include a storage controller 404, or storage server configured to manage data communications between the data storage device 406 and the server 402 or other components in communication with the network 408.
  • the storage controller 404 may be coupled to the network 408.
  • the user interface device 410 is referred to broadly and is intended to encompass a suitable processor-based device such as a desktop computer, a laptop computer, a personal digital assistant (PDA) or tablet computer, a smartphone or other a mobile communication device having access to the network 408.
  • sensors such as a camera or accelerometer
  • the user interface device 410 may access the Internet or other wide area or local area network to access a web application or web service hosted by the server 402 and provide a user interface for enabling a user to enter or receive information.
  • the network 408 may facilitate communications of data, such as authentication information, between the server 402 and the user interface device 410.
  • the network 408 may include any type of communications network including, but not limited to, a direct PC-to-PC connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, a combination of the above, or any other communications network now known or later developed within the networking arts which permits two or more computers to communicate.
  • the user interface device 410 accesses the server 402 through an intermediate sever (not shown).
  • FIGURE 5 illustrates a computer system 500 adapted according to certain embodiments of the server 402 and/or the user interface device 410.
  • the central processing unit (“CPU") 502 is coupled to the system bus 504.
  • the CPU 502 may be a general purpose CPU or microprocessor, graphics processing unit (“GPU”), and/or microcontroller.
  • the present embodiments are not restricted by the architecture of the CPU 502 so long as the CPU 502, whether directly or indirectly, supports the operations as described herein.
  • the CPU 502 may execute the various logical instructions according to the present embodiments.
  • the computer system 500 also may include random access memory (RAM) 508, which may be synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), or the like.
  • RAM random access memory
  • the computer system 500 may use RAM 508 to store the various data structures used by a software application.
  • the computer system 500 may also include read only memory (ROM) 506, which may be PROM, EPROM, EEPROM, optical storage, or the like.
  • ROM read only memory
  • the ROM may store configuration information for booting the computer system 500.
  • the RAM 508 and the ROM 506 store user and system data.
  • the computer system 500 may also include an input/output (I/O) adapter 510, a communications adapter 514, a user interface adapter 516, and a display adapter 522.
  • the I/O adapter 510 and/or the user interface adapter 516 may, in certain embodiments, enable a user to interact with the computer system 500.
  • the display adapter 522 may display a graphical user interface (GUI) associated with a software or web-based application on a display device 524, such as a monitor or touch screen.
  • GUI graphical user interface
  • the I/O adapter 510 may couple one or more storage devices 512, such as one or more of a hard drive, a solid state storage device, a flash drive, a compact disc (CD) drive, a floppy disk drive, and/or a tape drive, to the computer system 500.
  • the data storage 512 may be a separate server coupled to the computer system 500 through a network connection to the I/O adapter 510.
  • the communications adapter 514 may be adapted to couple the computer system 500 to the network 408, which may be one or more of a LAN, WAN, and/or the Internet.
  • the communications adapter 514 may also be adapted to couple the computer system 500 to other networks such as a global positioning system (GPS) or a Bluetooth network.
  • GPS global positioning system
  • the user interface adapter 516 couples user input devices, such as a keyboard 620, a pointing device 518, and/or a touch screen (not shown) to the computer system 500.
  • the keyboard 520 may be an on-screen keyboard displayed on a touch panel.
  • Additional devices such as a camera, microphone, video camera, accelerometer, compass, and/or gyroscope may be coupled to the user interface adapter 516.
  • the display adapter 522 may be driven by the CPU 502 to control the display on the display device 524. Any of the devices 502-522 may be physical and/or logical.
  • the applications of the present disclosure are not limited to the architecture of computer system 500. Rather the computer system 500 is provided as an example of one type of computing device that may be adapted to perform the functions of a server 402 and/or the user interface device 410.
  • any suitable processor-based device may be used including, without limitation, personal data assistants (PDAs), tablet computers, smartphones, computer game consoles, and multiprocessor servers.
  • PDAs personal data assistants
  • the systems and methods of the present disclosure may be implemented on application specific integrated circuits (ASIC), very large scale integrated (VLSI) circuits, or other circuitry.
  • ASIC application specific integrated circuits
  • VLSI very large scale integrated circuits
  • Computer-readable media includes physical computer storage media.
  • a storage medium may be any available medium that can be accessed by a computer.
  • such computer-readable media can comprise RAM, ROM, EEPROM, CD- ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • disk and disc includes compact discs (CD), laser discs, optical discs, digital versatile discs (DVD), floppy disks, and blu-ray discs. Disks reproduce data magnetically, and discs reproduce data optically. Combinations of the above may also be included within the scope of computer-readable media.
  • instructions and/or data may be provided as signals on transmission media included in a communication apparatus.
  • a communication apparatus may include a transceiver having signals indicative of instructions and data. The instructions and data are configured to cause one or more processors to implement the functions outlined in the claims.
  • Customer activity may be monitored in the cloud-based customer loyalty systems described above to provide incentives that encourage customers to refer new customers to a business.
  • New customers may be referred by existing customers through a number of different referral techniques.
  • an existing customer may be provided an opportunity to review the product and/or service purchased from the business and post the review online. Potential customers may read the customer's review of the product and/or service and contact the business to obtain the same product and/or service.
  • referral systems are described for products in the remainder of the application, it should be understood that systems for referring new customers to a business that provides products can similarly be applied for referring new customers to a business that provides services or both products and services.
  • FIGURE 6 is a flow chart illustrating a method of rewarding customers for reviewing products according to one embodiment of the disclosure.
  • a method 600 begins at block 602 with the cloud-based referral system receiving information for a completed transaction involving the customer.
  • the information may be received from a point of sale (POS) terminal or server and include information describing a purchase by the customer.
  • the information may include the model number or stock-keeping unit (SKU) of a product purchased by the customer.
  • SKU stock-keeping unit
  • the information may also include the price paid and any promotional codes redeemed by the customer during the purchase.
  • the POS terminal completing the transaction may have software installed to interface with the customer loyalty referral system and provide near real-time transfer of the transaction information. Alternatively, data may be exported at scheduled or occasional intervals and uploaded to the cloud-based customer loyalty system.
  • the customer may be provided by the cloud-based customer loyalty program with an opportunity to review the transaction received at block 604.
  • the opportunity may be provided through an SMS text message transmitted to the user's mobile device by the SMS server 122 of FIGURE 1.
  • the opportunity may be provided through a notification in the application loaded on the customer's mobile device 314 of FIGURE 3.
  • the opportunity may be provided through an email sent to the customer.
  • the opportunity may include a link to a web page from which the customer may enter review information.
  • the customer may rate products purchased in the transaction based on criteria including reliability, performance, value, warranty service, and customer service.
  • the criteria may allow the customer to rate the criteria on predefined rating system, such as one star to five stars or provide for free-form text entry.
  • a cumulative review score may be generated by adding up scores assigned to a number of categories. For example, five possible points may be awarded for each of five different categories for a total of twenty- five possible points.
  • FIGURE 7 is a graphic illustrating a sample opportunity presented to a customer to review products purchased during a transaction with the business according to one embodiment of the disclosure.
  • a screen shot 700 includes a description 702 of the business and a short message 704 from the business.
  • the short message 704 may include text provided by the business, such as a note of appreciation to the customer and the order number.
  • the description 702 may include the business name and contact information including an address and/or a telephone number.
  • the screen shot 700 may also include a total price 706 for the order and a request 708 to review the products purchased in exchange for reward dollars. Additional opportunities 710 to earn reward dollars may be presented to the customer.
  • the screen shot 700 may be a portion of an email delivered to the customer after the purchase.
  • FIGURE 8 is a graphic illustrating a sample review completed by a customer according to one embodiment of the disclosure.
  • a screen shot 800 includes a description 802 of the items purchased by the customer 804. The customer may assign stars to each of a number of criteria 806. The customer may also enter comments 808 describing the purchase. Additional information may be displayed in the screen shot 800, such as customer loyalty data 810 and an overall score 812 assigned to the business.
  • the review is received at the cloud-based customer loyalty system after the customer completes the review.
  • the review is stored in a database in the cloud-based customer loyalty system.
  • the review is checked before being stored in the database. For example, all reviews may be checked by an employee at the business soliciting the review. In another example, a script may scan the review for use of certain flagged words. If the review is rejected, then the method 600 stops before providing loyalty rewards. The review may be made available to the public quickly if the review is deemed acceptable. If the review is deemed unacceptable, the review may be forwarded to the business along with contact information for the customer to allow the business to resolve any problems. Criteria for determining whether a review is acceptable may include length, grammar, use of profanity, and rating.
  • loyalty rewards are provided to the customer.
  • the loyalty rewards may be reward dollars that are used to purchase coupons. For example, 100 reward dollars may be exchanged for a five dollar gift certificate to the business.
  • the ratio of reward dollars to gift certificate value may be set by the business participating in the cloud-based referral program. Additionally, the number of reward dollars earned for completing a review may be set by the business. The ratio may be changed by the business through the control panel 132 of FIGURE 1.
  • employees of the business may also be rewarded with reward dollars when customers make purchases linked to the cloud-based customer loyalty system.
  • Employees at the business enter their identification information into the POS terminal before the customer completes a purchase.
  • employees may be rewarded with reward dollars in their account. For example, an employee may receive ten reward dollars for signing up 75 new customers into the cloud-based customer loyalty system.
  • an employee may receive one reward dollar for each transaction completed at the business and transmitted to the cloud-based loyalty system.
  • Employees may be entered into a database with information such as a name, photograph, icon, employee number, employee card, employee POS personal identification number (PIN), manager permissions level, email, phone, username, password, clique, and/or an active or inactive setting.
  • Statistics for each employee may be tracked through the reward system, such as a total number of positive reviews received by the employee, a total number of negative reviews received by the employee, a total number of transactions processed by the employee, and/or a total number of new reward system enrollments by the employee.
  • Transactions may include completed purchases and other actions, such as card swipes.
  • Information stored about employees' interactions with the cloud-based customer loyalty system may be used to provide periodic or intermittent review of employees.
  • the merchant's management may then address mistakes, concerns, issues, and/or complaints from customers.
  • employee information and statistics assist merchant management in evaluating employee performance.
  • FIGURE 9 is a graphic illustrating other methods for earning reward dollars through a referral program according to one embodiment of the disclosure.
  • a screen shot 900 includes a request 902 for a review of the customer's experience.
  • the screen 900 also includes an opportunity 904 for the customer to review the experience through ratings and comments.
  • Other methods for earning reward dollars are presented along with the review opportunity 904 in the screen 900.
  • the customer may refer friends by entering email addresses in text boxes 906.
  • the potential customers are sent a link to purchase products or a link to print out a coupon for use in the physical store.
  • the referring customer is credited with reward dollars.
  • Challenges may be established by a business that provide rewards for accomplishing certain referrals. For example, the business may provide a specific reward to the first person to refer five friends.
  • the customer may refer friends by sharing his or her purchase on social networks by clicking one or more of the "like" buttons 908a-c. Clicking on one or more of the "like" buttons 908a-c posts information to the customer's social media account that the customer has purchased and enjoyed a certain product from the business. The information may be posted to social media accounts, such as TWITTER, FACEBOOK, and/or LINKEDIN. The customer may be provided with reward dollars for sharing information in their social media account.
  • social media accounts such as TWITTER, FACEBOOK, and/or LINKEDIN.
  • reward dollars may be earned for making purchases from the business.
  • a reward ratio may be set by the business awarding a percentage of the purchase total in reward dollars.
  • the reward ratio may be set for specific times during the day to encourage customer visits during certain times of the day. For example, a higher reward ratio may be set between 3 pm and 5 pm on weekdays and/or in specific geographic regions.
  • the business may be charged for participation in the cloud-based customer loyalty program by identifying the number of reward dollars awarded to the business' customers. For example, a business may purchase a pack of one thousand reward dollars for a fixed price. After the reward dollars are spent on the business' customers, the business may choose to refill with an additional purchase of reward dollars.
  • FIGURES 10A-D are illustrations of a user interface for managing a customer account in a cloud-based customer loyalty program according to one embodiment of the disclosure.
  • FIGURE 10A is an illustration of a customer profile according to one embodiment of the disclosure.
  • a profile 1000 may include a card number 1002 linked to the customer.
  • the card number may be encoded in a magnetic strip, radio frequency identification (RFID), and/or a barcode affixed to an identification card.
  • RFID radio frequency identification
  • the card number may be entered during online purchases or scanned at a physical store to link purchases made at the business to the customer. According to one embodiment, the card may be used by the customer at multiple businesses.
  • the profile 1000 may also include contact information 1004 including a name, phone number, email address, and zip code.
  • the profile 1000 may further include member information 1006, such as a birthday, anniversary date, gender, and a password/pin for accessing the customer's loyalty account. Changes made to the profile 1000 may be confirmed by clicking the save button 1008a or rejected by clicking the cancel button 1008.
  • FIGURE 10B is an illustration of a customer account according to one embodiment of the disclosure.
  • Account information 1010 may include a card number 1012 of the customer.
  • the account information 1010 may also include a listing of the balances 1014 of reward dollars for each business for which the customer is participating in a loyalty program.
  • a customer may transfer reward dollars to other customers of a particular business by clicking one of the send buttons 1016a-c.
  • Coupons 1018 previously earned by a customer from one of the participating business may also be listed in the account information 1010.
  • a customer may print one of the coupons 1018 by clicking on a print button 1018a.
  • FIGURE IOC is an illustration of a customer sending reward dollars to another user according to one embodiment of the disclosure.
  • Loyalty rewards may be transferred between customers of the same business.
  • a send money screen 1020 may include a display of the customer's balance 1022 of reward dollars for the business.
  • the customer may specify a recipient 1024 and an amount 1026 for transfer.
  • the loyalty reward transfer may be confirmed with the next button 1028b or rejected with the cancel button 1028a.
  • a business may prevent transfer of loyalty rewards between customers of the business.
  • FIGURE 10D is an illustration of available coupons for purchase with reward dollars according to one embodiment of the disclosure.
  • a coupon screen 1040 may include display of offers available to the customer.
  • Specials 1042 may include coupons available to the customer not requiring expenditure of reward dollars. For example, at a restaurant the coupons may include a buy-one-burger-get-a-free-soft-drink coupon. The customer may obtain one of the offers by clicking the print buttons 1042a- b.
  • the specials 1042 may be customized to the customer's purchase habits. For example, the specials 1042 may be determined based on a customer's purchase history. According to one embodiment, customers may be organized into cliques based on profile or purchase information. Different cliques may receive different offers. Cliques may group customers by spending dollars, frequent visits, and/or lapsed customers.
  • Specials 1044 may include reward coupons available with the purchase of reward dollars. For example, the customer may spend 50 reward dollars for a gift certificate worth ten dollars at the business. The customer may purchase one of the reward coupons by selecting the unlock button 1044a. After a reward coupon is unlocked it may be emailed to the customer or displayed on the customer's screen for printing. According to one embodiment, the gift certificate value may be associated with the reward card number, such that the value is automatically credited to a purchase when the customer next visits the business.
  • FIGURE 11 is an illustration of a coupon generated by the cloud- based customer loyalty program according to one embodiment of the disclosure.
  • a coupon 1100 may include information useful to the customer and the business in identifying the reward.
  • the coupon 1100 may include a number 1102, an expiration date 1104, a recipient 1106, a business name 1108, a description 1110 of the reward, terms and conditions 1112 and 1124, a quick response (QR) code 1114, a bar code 1116, and/or instructions 1120 and 1122 to the business for redeeming the coupon 1100.
  • QR quick response
  • a bar code 1116 a bar code 1116
  • the employee may scan the bar code 1116 or the QR code 1114 into the POS terminal at the time of purchase.
  • the coupon 1 100 may be verified by the cloud-based customer loyalty system before the discount is granted.
  • FIGURE 12 is an illustration of a social media application for accessing the cloud-based customer loyalty program according to one embodiment of the disclosure.
  • An application 1200 may display reviews 1210a-c. Each review 1210a-c may include information such as an identification of the merchant 1215 and a graphic icon 1212 associated with the merchant. Additionally, each review 1210a-c may identify a reviewer 1214, a date and/or time 1216 of the review, a rating 1217, an overall score 1218 of the merchant, ratings 1213 for each category, and comments 1219 from the reviewer.
  • Settings for the application may be accessed by selecting button 1202 labeled "Edit Review Application Settings.”
  • FIGURE 13 is an illustration of a social media application settings screen according to one embodiment of the disclosure.
  • a display 1300 may include settings available to the merchant, such as filtering reviews for display in the application.
  • An option 1310 may allow display of all reviews submitted to the cloud- based loyalty program. According to one embodiment, when all reviews are displayed, the reviews may be displayed in reverse chronological order such that the display 1200 of FIGURE 12 evolves over time to show the newest reviews.
  • An option 1320 may limit the display 1200 of reviews in FIGURE 12 to those associated with a particular merchant.
  • An option 1330 may limit the display 1200 of reviews in FIGURE 12 to those associated with a particular clique associated with the merchant.
  • a merchant may have multiple locations with each location organized as a clique for receiving marketing materials.
  • a button 1340 may allow saving the selected option 1310, 1320, or 1330 and leaving the display 1300.
  • a button 1350 may allow cancelling the change in application settings and leaving the display 1300.
  • the social media application may also provide the customer with additional opportunities to review and/or recommend a merchant enrolled in the cloud- based loyalty system. For example, a customer may create a review for a merchant through the social media application without accessing the review page through the cloud-based loyalty program. The social media application transmits the review to the cloud-based loyalty program. Additionally, a social media application may allow a FACEBOOK user to receive new reviews posted regarding a merchant or the products offered by the merchant. For example, a social media user may subscribe to updates from a merchant or a particular clique of a merchant. When another user posts a review for the merchant, a notification may be provided on the user's news feed. Although a social media application is discussed above, the application may be designed for any website or other application, such as through an application programming interface (API). According to one embodiment, the social media application interacts with FACEBOOK.
  • API application programming interface
  • a kiosk may be installed at a merchant's location to allow a customer to sign up for the cloud-based loyalty program and/or check their status in the cloud- based loyalty program. Additionally, employees may use the kiosk to complete transactions for customers.
  • the kiosks may be personal computers or other devices, such as remote terminals. According to one embodiment, the kiosk functionality may be implemented on a mobile device as described below with reference to FIGURES 25-38.
  • the kiosk may include a touch-screen for easy entry of data by customers and employees.
  • the interface for the kiosk may be implemented as a series of web pages or implemented as stand-alone program for execution on the kiosk.
  • FIGURE 14 is an illustration of a kiosk welcome screen according to one embodiment of the disclosure.
  • a display 1400 may prompt a user to select one of buttons 1410, 1420, and 1430.
  • a new user may select button 1410
  • a current user may select button 1420
  • an employee may select button 1430.
  • the user may be presented with a series of screens to register a new card and provide registration information, such as a name, address, email address, username, and/or password. After registration is complete, the user may be emailed a confirmation including a link to access their account in the cloud-based loyalty program and opportunities to join cliques from merchants nearby and/or merchants similar to the merchant where the user registered.
  • FIGURE 15 is an illustration of a kiosk login screen according to one embodiment of the disclosure.
  • a display 1500 may include prompts to obtain information to identify the user.
  • the display 1500 may include a text box 1520 for the entry of an email address or mobile number associated with the user's cloud-based loyalty program account.
  • the display 1500 may also include a text box 1530 to allow a user to enter their unique loyalty card number.
  • the display 1500 may also request additional information from the user to verify their identity.
  • the display 1500 may include a text box 1540 to allow a user to enter a PIN code.
  • the user may select a button 1550 for resetting and/or obtaining a lost PIN code.
  • the user may select a login button 1560 or a cancel button 1570.
  • FIGURE 16 is an illustration of a kiosk PIN recovery screen according to one embodiment of the disclosure.
  • a display 1600 may include an identification text box 1620 to allow a user to enter an identifier.
  • the identifier may be, for example, a card number, an email address, and/or a mobile number.
  • the user may select a send button 1630.
  • the user may also cancel the PIN code recovery by selecting a cancel button 1540.
  • the cloud-based loyalty program may attempt to identify the user by the entered information and send an email to the user's registered email address.
  • the email may include a reminder of the PIN code, a new PIN code, and/or a link to select a new PIN code.
  • FIGURE 17 is an illustration of a goal tracking screen according to one embodiment of the disclosure.
  • a display 1700 may display loyalty goals, balances, and/or earned vouchers.
  • the display 1700 may update to display goals 1730, 1740, and 1750.
  • Goals may be displayed for each of the merchants the user has visited. Additionally, multiple goals may be displayed for each of the merchants associated with the user's account.
  • the goals 1750 may include goals 1750a and 1750b for a free dessert and a free appetizer.
  • FIGURE 18 is an illustration of a voucher redemption screen according to one embodiment of the disclosure.
  • a display 1800 may include a display of the user's current reward balance 1810, a cost 1820 of redeeming the voucher, a remaining balance 1830 after redemption, an identification 1840 of the voucher selected, and an identification 1850 of the merchant providing the voucher.
  • the user may select a confirmation button 1870.
  • the cloud-based loyalty program may deduct the reward dollars from the user's account and generate the voucher. If the user does not accept the voucher, the user may select a cancel button 1880 or a back button 1860 to return the kiosk to an earlier screen.
  • FIGURE 19 is an illustration of balance information according to one embodiment of the disclosure.
  • a display 1900 displays balance information for each of the merchants a user has visited.
  • a balance 1930 displays a total reward balance in the cloud- based loyalty program
  • a balance 1940 displays a loyalty reward balance at a particular merchant.
  • the world dollar balance 1930 may be used to purchase vouchers for any merchant.
  • the loyalty dollar balance 1940 also referred to as clique dollars, may be used to purchase vouchers for a particular merchant.
  • Merchants may establish automatic rewards for their customers. Customers may view these automatic rewards and their progress towards earning the rewards through the kiosk.
  • FIGURE 20 is an illustration of an automatic loyalty program screen according to one embodiment of the disclosure.
  • a display 2000 may include rewards 2040 and 2050.
  • the rewards 2040 may indicate the progress of a customer in the merchant's clubs. For example, a merchant may offer a buy-ten-get-one free club.
  • a display 2000 may also include rewards 2050.
  • the rewards 2050 may indicate the progress of a customer in establishing certain business levels with the merchant. For example, a customer may automatically receive vouchers when a certain number of reward dollars are earned.
  • Clubs such as those illustrated in the rewards 2040, may be created by the merchants.
  • the clubs may be specified by club name, club product, product purchase requirements, participating cliques, beginning date, ending date, and/or active or inactive status. Further clubs may be enrolled manually by a user or by an employee for a user, or the clubs may automatically enroll all customers assigned to a particular clique or that complete a transaction with a particular merchant.
  • Automatic rewards such as those illustrated in the rewards 2050, may also be created by the merchants. Levels in the automatic rewards may be specified by a title, a required task or amount of reward dollars, participating cliques, beginning date, ending date, and/or active or inactive status. Vouchers may be created by the merchants and attached to particular levels in the rewards 2050. The cloud-based loyalty program may automatically generate and issue the vouchers when the requirements, such as completion of a task or reaching a certain level of reward dollars, are met.
  • additional programs may be defined by a merchant and implemented in the cloud-based loyalty program.
  • a program may be created to provide a voucher to a customer on his birthday based, in part, on the user's assigned clique and status.
  • a program may be created to provide a voucher to a customer on his anniversary of membership in a particular clique.
  • a program may be created to provide a voucher to a customer as a welcome to new members of a clique.
  • the welcome program may include an initial balance of reward dollars for the new member's account.
  • FIGURE 21 is an illustration of an employee login screen according to one embodiment of the disclosure.
  • a display 2100 may include a text box 2120 for receiving an employee identification such as a number.
  • the display 2100 may also include a login button 2130 for submitting the identification entered in the text box 2120.
  • a back button 2110 may return the kiosk to the display of FIGURE 14.
  • FIGURE 22 is an illustration of a customer note screen according to one embodiment of the disclosure.
  • a display 2200 may include a previously-entered note 2210 along with an employee 2220 who entered the note and a date 2230 the note 2210 was entered.
  • the note 2210 may be edited by an employee at a later time by selecting an edit button 2240 and/or may be deleted by an employee at a later time by selecting a delete button 2250.
  • a new note may be added by an employee by entering text in a text box 2260 and selecting an add button 2270.
  • a back button 2280 may allow an employee to return the kiosk to a main menu.
  • FIGURE 23 is an illustration of a new transaction screen according to one embodiment of the disclosure.
  • a display 2300 may include text boxes to allow the entry of items for the transaction and a preview of balance information.
  • the display 2300 may include a textbox 2310 for entering a stock-keeping unit (SKU) or universal product code (UPC) for an item.
  • the display 2300 may also include a textbox 2320 for entering a description of an item to look up the corresponding SKU or UPC.
  • the kiosk may suggest items 2320a for completing the entry. After an item is entered, the employee may enter a quantity 2330 of each item.
  • a preview of the rewards earned from the transaction may be displayed in a text box 2340.
  • Text boxes 2350a-c may allow a redemption of earned reward dollars to apply against the current transaction.
  • a final balance may be displayed in a text box 2360 before a customer accepts the transaction by selecting a submit button 2370.
  • the textbox 2350a may display general reward dollars applied to the balance 2360
  • the text box 2350b may display merchant-specific reward dollars applied to the balance 2360
  • the text box 2350a may display vouchers applied to the balance 2360.
  • Buttons 2352a-b may allow a user to apply any available dollars to the balance 2360. For example, when a user clicks the buttons 2352a-b, the cloud-based loyalty program may identify any applicable and/or available reward dollars and apply them to the balance 2360.
  • FIGURE 24 is an illustration of a leaderboard screen according to one embodiment of the disclosure.
  • Leaderboards may be created by an administrator to encourage certain purchases by their customers. For example, leaderboards may rank customers by total dollars spent, frequency of visits to the merchant, and/or frequency of purchases of a particular product.
  • a merchant may track customers most frequently purchasing a dessert or a steak at a restaurant.
  • a leaderboard screen 2400 may include a number of merchants 2402, 2412, 2422, and 2432 linked to the customer's profile. Each of the merchants may have none or one or more leaderboards for the customer to participate in. For example, the merchant 2432 has leaderboards 2434a, 2434b, and 2434c.
  • the leaderboards 2434a-c may display the customer's rank in the respective leaderboard.
  • Each of the leaderboards 2434a-c may also include a button 2436a-c allowing the customer to view the top ten customers on the leaderboard.
  • the buttons 2436a-c may toggle between a "view top 10" button and a "close top 10" button based on whether a list 2438 is currently being displayed for the leaderboards.
  • Customer information in the list 2438 may be partially redacted to preserve the confidentiality of the customers.
  • the leaderboard list 2438 may only display a customer's first name and initial of the customer's last name. Administrators may configure leaderboard for specific cliques. Administrators may also toggle a leaderboard between active and inactive status.
  • a mobile device may provide functionality similar to the kiosk described above with reference to FIGURES 14-24.
  • a mobile version of the kiosk may be a convenient and efficient tool to capture leads or customers into a merchant's customer database and to provide an access point for customers to check their account information.
  • the mobile kiosk application may be an HTML web- based platform with a template that is modified to fit mobile devices, such as Blackberry, iPhone, Android, and/or Windows Mobile-based devices.
  • a mobile device may access a web address through a mobile browser and be redirected to the mobile kiosk template when the server detects the requesting device is a mobile device.
  • the customer may be welcomed with a user friendly, touch optimized experience.
  • the registration process may be completed in less than a minute, and the customer walks away with a loyalty card and with membership into the merchant's loyalty program and marketing system. Additionally, once the customer is registered, the customer may be enrolled a global network, which stores loyalty information for multiple participating vendors. Login credentials may be assigned so the customer may access their account information and manage their profile.
  • customers may have mobile access to their account information via their smartphone. Further, merchants and their employees may use mobile kiosk to perform the same operations as performed on the full version of the kiosk. Adding customers and processing transactions from a smartphone device or tablet gives merchants the power of customer capture while on the move.
  • FIGURE 25 is an illustration of a mobile kiosk welcome screen according to one embodiment of the disclosure.
  • a mobile kiosk screen 2500 may include a consumer button 2501 and a merchant button 2502.
  • the screen 2500 may also include links 2503-2505 to various social media and contact pages.
  • FIGURE 26 is an illustration of a mobile kiosk login screen displayed to a customer according to one embodiment of the disclosure.
  • a login screen 2600 may be displayed to the customer after the customer selects the consumer button 2501 on screen 2500.
  • a title 2601 designates the page the customer is viewing.
  • the screen 2600 is a home screen displayed to a customer who is not logged in.
  • An avatar 2602 may include a logo or image of a business listed in information 2603.
  • a register button 2604 button when touched or clicked on, may begin the registration process for a new user who wishes to join the merchant's loyalty program and may navigate the user to an appropriate screen.
  • a login button 2605 when touched or clicked on, may allow an existing customer to access their account to be able to update their profile, add a new card, access vouchers, view loyalty and world dollar balances, and/or merchant deals.
  • a merchant login button 2606 when touched or clicked on, may go to the merchant login screen where employees entered in the employee module may be able to use their employee number to access the kiosk to apply quick loyalty to a customer.
  • a find merchants button 2607 when touched or clicked on, may navigate the customer to a screen where they can view nearby and surrounding merchants that are offering loyalty rewards.
  • FIGURE 27A is an illustration of a mobile kiosk first-step registration screen according to one embodiment of the disclosure.
  • a register screen 2700 includes a back button 2701, which, when clicked or touched may redirect the customer back to the previous screen, which may be the login screen 2600.
  • a title 2702 may display "Register.”
  • a progress bar 2705 may provide the customer with an update on their registration progress.
  • Information 2706 may be collected from the customer, such as first name, last name, zip code, birthday, and/or gender.
  • a next button 2707 may progress through the registration process, and a clear button 2708 may reset the screen 2700.
  • FIGURE 27B is an illustration of a mobile kiosk second-step registration screen according to one embodiment of the disclosure.
  • a register screen 2700 may be updated to include a new progress bar 2705 and to collect additional information 2716, such as phone number, email address, card number, and/or personal identification number (PIN).
  • additional information 2716 such as phone number, email address, card number, and/or personal identification number (PIN).
  • PIN personal identification number
  • a link 2717 may be provided to allow the customer to view the terms and/or conditions of the loyalty program.
  • FIGURE 27C is an illustration of a mobile kiosk third-step registration screen according to one embodiment of the disclosure.
  • a register screen 2700 may include an updated progress bar 2705 and collect additional information.
  • a box 2726 may allow the customer to select an employee from a list of employees that the merchant has set up to give them credit for the enrollment.
  • a box 2727 may check if the customer has children under the age of eighteen or if the customer is interested in learning more about the loyalty program.
  • a box 2728 may input email addresses to refer friends to the merchant.
  • FIGURE 27D is an illustration of a mobile kiosk fourth-step registration screen according to one embodiment of the disclosure.
  • a register screen 2700 may include an updated progress bar 2705 and a verification 2736 that the registration was successful.
  • a finish button 2737 will complete the registration and trigger processes to happen on the server providing the registration screen 2700, such as sending a confirmation email and/or processing the new member information.
  • FIGURE 28 is an illustration of a mobile kiosk login screen according to one embodiment of the disclosure.
  • a login screen 2800 allows a customer to login after the customer has registered and includes a back button 2801, a title 2802, an avatar 2803, and merchant information 2804.
  • the customer may log in by inputting information in box 2805, such as email address, phone number, or card number, and a PIN.
  • the customer may then press a login button 2806. If the customer forgets their PIN, the customer may select a forgot PIN button 2807.
  • the customer information supplied by the customer may be transmitted to a server in the cloud-based customer loyalty program.
  • the server may transmit back to the mobile device rewards program information pertaining to the customer identified by the customer information.
  • the customer may then interact with the customer loyalty program through the mobile device.
  • FIGURE 29 is an illustration of a mobile kiosk home screen according to one embodiment of the disclosure.
  • a home screen 2900 may include an icon 2905 indicating the customer is a member of the merchant displayed in box 2804 with avatar 2803.
  • the home screen 2900 may allow a customer to select between viewing profile information 2906, viewing loyalty information 2907, viewing merchant specials 2908, or finding nearby merchants 2909.
  • the profile navigation button 2906 is touched or clicked on, the customer may be navigated to their member profile account screen, where the customer may edit personal information, contact information, PIN number, avatar, preferences.
  • the loyalty navigation button 2907 is touched or clicked on, the customer may be navigated to a loyalty screen.
  • a log out button 2902 allows the customer to secure the mobile device.
  • FIGURE 30A is an illustration of a mobile kiosk loyalty screen according to one embodiment of the disclosure.
  • a loyalty screen 3000 may be displayed after the customer selects loyalty button 2907 of FIGURE 29.
  • the loyalty screen 3000 may display information related to goals 3006, balances 3007, and/or vouchers 3008.
  • a goal tracker 3009 may be displayed on the screen 3000 and include tracking information for each level created by the merchant based on the requirements set for total subtotal purchase dollars required for each level to unlock vouchers at each level.
  • the tracking information may be displayed as a progress bar for each reward level of each merchant.
  • the information may also include a calculation of the amount needed to spend by the customer to obtain the reward.
  • FIGURE 30B is an illustration of a mobile kiosk voucher purchase screen according to one embodiment of the disclosure.
  • the screen 3000 may be updated to include voucher information when confirming a purchase, including a balance 3016, a redemption cost 3017, a remaining balance 3018, a voucher chosen 3019, and the merchant name 3020.
  • a yes button 3021 may be selected by the customer to confirm the purchase and initiate steps on a server to award the voucher.
  • a cancel button 3022 cancels the voucher purchase without consuming the customer's reward balance.
  • FIGURE 30C is an illustration of a mobile kiosk loyalty balance screen according to one embodiment of the disclosure.
  • the screen 3000 may be updated to display balances and/or recent transactions at various merchants 3032 and/or a global dollar balance 3031.
  • the screen 3000 may include send buttons 3031a and 3032c for sending either world dollars or loyalty dollars to a recipient, respectively.
  • FIGURE 30D is an illustration of a mobile kiosk voucher screen according to one embodiment of the disclosure.
  • the screen 3000 may be updated to display stored vouchers 3043.
  • the screen 3000 may be updated to display details regarding the selected voucher.
  • FIGURE 30E is an illustration of a mobile kiosk voucher detail screen according to one embodiment of the disclosure. To redeem a voucher, the customer may select view scan code button 3054 for a voucher 3053 to display a UPC and/or QR code, which is scanned by the merchant for redemption.
  • FIGURE 31 is an illustration of a mobile kiosk send dollars screen according to one embodiment of the disclosure.
  • a send screen 3100 may display a balance 3102 of reward dollars accumulated at the merchant selected by the customer and allow entry of a recipient in box 3103 and an amount in 3014. After entering information, the customer may select the next button 3015 to review and confirm details of the transfer. The customer may select the cancel button 3016 to cancel the transaction and not alter the customer's balance.
  • FIGURE 32A is an illustration of a mobile kiosk merchant spotlight screen according to one embodiment of the disclosure.
  • a spotlight screen 3200 may be displayed when the customer selects the merchant specials button 2908 of FIGURE 29.
  • a spotlight screen 3200 may include specials, world dollar spotlights 3203, and/or loyalty spotlights 3204. For example, the customer may unlock merchant specials through buttons 3201.
  • FIGURE 32B is an illustration of a mobile kiosk loyalty spotlight screen according to one embodiment of the disclosure.
  • the screen 3200 may be updated to display loyalty programs when the loyalty button 3204 is selected.
  • the updated screen 3200 may include clubs 3212 and rewards levels 3214 set by the merchant.
  • FIGURE 33 is an illustration of a mobile kiosk send dollar screen according to one embodiment of the disclosure.
  • a send dollar screen 3300 may display a customer balance 3301 and may allow the customer to enter recipient information 3302 and a send amount 3303.
  • FIGURE 34 is an illustration of a mobile kiosk merchant home according to one embodiment of the disclosure.
  • a merchant home screen 3400 may include a title 3401, a logout button 3402, an avatar 3403, merchant information 3404, a search/add loyalty information button 3405, a transaction button 3406, a voucher button 3407, and/or an add customer button 3408.
  • FIGURE 35A is an illustration of a mobile kiosk merchant loyalty screen according to one embodiment of the disclosure.
  • a loyalty screen 3500 may display a listing of a customer enrolled in the loyalty program, including a name 3521, a phone number 3522, card numbers 3523, an email address 3524, a zip code 3525, a gender 3526, and/or a birthday 3527.
  • Customers may be searched by loyalty card number 3502 and/or a mobile number 3503.
  • the search may be executed by clicking the search button 3505.
  • the results may be cleared by pressing the clear button 3504.
  • a quick loyalty reward 3506 may be applied to a customer by clicking the apply button 3507.
  • an edit button 3528 is selected, the customer information displayed on the screen 3500 may be modified.
  • FIGURE 35B is an illustration of a mobile kiosk merchant loyalty second-step screen according to one embodiment of the disclosure.
  • a merchant may modify the customer information, such as name 3531a, number 3531b, email 3531c, birthday 353 Id, zip code 353 le, gender 353 If, and card number(s) 353 lg.
  • the merchant may cancel the update by selecting the cancel button 3532.
  • the merchant may confirm the changes by selecting the update button 3533, which may transmit the changes to a server.
  • FIGURE 35C is an illustration of a mobile kiosk merchant loyalty third-screen according to one embodiment of the disclosure.
  • a user photo and a merchant photo may be displayed on the screen 3500.
  • Information associated with a photograph may include an owner 3542, 3546, an uploader 3543, 3547, and a upload date 3544, 3548.
  • New photos may be selected for the customer by selecting the browse button 3550.
  • Photos may be deleted by selecting the delete button 3549.
  • a back button 3551 may return the merchant to a previous screen.
  • a logout button 3552 may secure the mobile device.
  • FIGURE 35D is an illustration of a mobile kiosk merchant loyalty fourth-screen according to one embodiment of the disclosure.
  • a note 3561 may be submitted by a user 3562 on a date 3563.
  • the note 3561 may be edited by selecting an edit button 3564 or deleted by selecting a delete button 3565.
  • a new note may be entered in the box 3566 and the add note button 3567 selected.
  • a back button 3568 may return the merchant to a previous screen.
  • a logout button 3569 may secure the mobile device.
  • FIGURE 36 is an illustration of a mobile kiosk merchant voucher search screen according to one embodiment of the disclosure.
  • a voucher may be searched for by entering a voucher number 3601 and selecting a check button 3602, or the display cleared by selecting a clear button 3603.
  • the voucher number 3601 may be read by the mobile device by scanning a UPC or QR code with a camera.
  • Information about a voucher may be displayed, such as a voucher number 3604, a status 3206, a merchant name 3607, a title 3608, a redemption date 3609, a redeemer 3610, a recipient 3611, a credit amount 3612, an expiration date 3613, and/or a description 3614.
  • the voucher may be redeemed by selecting the redeem button 3605.
  • a confirmation screen may be presented to the merchant. After the redemption is confirmed, the server may invalidate the voucher number and/or mark the voucher's status as "used.”
  • FIGURE 37 is an illustration of a mobile kiosk merchant transaction screen according to one embodiment of the disclosure.
  • a transaction screen may include display of item information, display of discounts 3709, and/or confirmation 3710.
  • Displayed information may include, for example, a receipt number 3701, a SKU/UPC 3702, an item label 3703, a quantity, 3705, a price 3706, and/or a subtotal 3707.
  • the item may be added to the transaction by selecting an add item button 3708 or removed by selected a remove button 3704.
  • discount information is requested by selecting button 3709, additional information may be displayed to the merchant.
  • FIGURE 38A is an illustration of a mobile kiosk first-step merchant transaction screen according to according to one embodiment of the disclosure.
  • the merchant may return to view items by selecting button 3817 or confirm by selecting 3816.
  • Discount information displayed may include, for example, item total 3801, world dollars 3802, clique dollars 3803, voucher value 3804, subtotal 3805, tax 3806, total 3807, gift dollars 3808, balance 3809, and loyalty rewards earned on this purchase 3814. Discounts may be applied by selecting a apply world dollars 381 button, a apply clique dollars button 3812, and/or a apply gift dollars button 3813.
  • the discounts may be cleared by selecting clear button 3815 of the mobile device may be secured by selecting logout button 3818.
  • FIGURE 38B is an illustration of a mobile kiosk second-step merchant transaction screen according to one embodiment of the disclosure.
  • Confirmation information 3821 may include items in the transaction, costs, and/or applied discounts.
  • the transaction may be confirmed with a submit button 3823 or cancelled with a cancel button 3822.
  • FIGURE 38C is an illustration of a mobile kiosk merchant transaction screen with auto-complete search field according to one embodiment of the disclosure.
  • an item name 3802 may be partially-typed to invoke an auto-complete listing 3833 of items matching the partially-typed name.
  • “Chi” is typed
  • “Chi Tea” and “Chicken Salad” may be displayed in the auto-complete listing 3833.
  • the merchant may also type in a SKU/UPC in 3831 to select items for a transaction. The merchant then adds or removes the item through add button 3835 and remove button 3834, respectively.
  • the cloud-based loyalty system may be adapted for use in other environments.
  • the cloud-based loyalty system may be used to incentivize and track the progress of students at a school.
  • the student may have a special rewards card or the cloud-based account may be linked to the student's existing student ID card.
  • Points may be earned and/or lost through certain student actions. For example, ten points may be rewarded for daily attendance and penalized one point for every hour the student is late. In another example, five points may be rewarded for following direction prompts from teachers on a daily basis and one point may be lost for asking for a direction prompt to be repeated.
  • two points may be earned per hour of time spent in a time management program.
  • thirty points may be earned for completing work with on target progress, twenty-five points may be earned for completing work, twenty points may be earned for work progress demonstrating the student is academically at risk, ten points may be earned for work progress demonstrating a slow pace, and no points may be earned when the work has not been completed.
  • Students may redeem earned points for gift cards at participating merchants through a web portal similar to that described above for the cloud-based loyalty program.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Game Theory and Decision Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

Un programme de fidélité de la clientèle peut être implémenté dans un système basé sur un nuage. Le système basé sur un nuage établit une interface avec des dispositifs de point de vente (POS) dans un magasin physique et une interface avec des systèmes de traitement de transactions en ligne. Le système de fidélité de la clientèle basé sur un nuage suit les achats des clients et offre aux clients d'une société la possibilité d'évaluer des produits ou de présenter la société à des amis. En récompense de leurs présentations et de leurs évaluations, les clients reçoivent de l'argent susceptible d'être échangé contre des coupons pouvant être rachetés au sein de la société. Le programme de fidélité de la clientèle basé sur un nuage peut associer un client à des programmes de récompenses de multiples sociétés afin que le client n'ait ni à mémoriser de multiples identifiants, ni à transporter de multiples cartes.
PCT/US2013/024422 2012-02-03 2013-02-01 Programmes d'incitation commerciale basés sur un nuage WO2013116708A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201261594515P 2012-02-03 2012-02-03
US61/594,515 2012-02-03
US201261673451P 2012-07-19 2012-07-19
US61/673,451 2012-07-19

Publications (1)

Publication Number Publication Date
WO2013116708A1 true WO2013116708A1 (fr) 2013-08-08

Family

ID=48905893

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2013/024422 WO2013116708A1 (fr) 2012-02-03 2013-02-01 Programmes d'incitation commerciale basés sur un nuage

Country Status (1)

Country Link
WO (1) WO2013116708A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
ES2566066A1 (es) * 2015-10-29 2016-04-08 Universitat D'alacant / Universidad De Alicante Sistema y método para la gestión electrónica de tiques en arquitecturas cloud
US10319012B2 (en) 2013-06-27 2019-06-11 Walmart Apollo, Llc View items based on purchases of social media contacts
US10679264B1 (en) * 2015-11-18 2020-06-09 Dev Anand Shah Review data entry, scoring, and sharing
CN112035767A (zh) * 2020-08-14 2020-12-04 北京三快在线科技有限公司 一种展示提示信息的方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100057580A1 (en) * 2008-08-28 2010-03-04 Radha Raghunathan Unified payment card
US20110029364A1 (en) * 2009-07-29 2011-02-03 Cyriac Roeding Method and system for presentment and redemption of personalized discounts
US20110178885A1 (en) * 2010-01-18 2011-07-21 Wisper, Inc. System and Method for Universally Managing and Implementing Rating Systems and Methods of Use

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100057580A1 (en) * 2008-08-28 2010-03-04 Radha Raghunathan Unified payment card
US20110029364A1 (en) * 2009-07-29 2011-02-03 Cyriac Roeding Method and system for presentment and redemption of personalized discounts
US20110178885A1 (en) * 2010-01-18 2011-07-21 Wisper, Inc. System and Method for Universally Managing and Implementing Rating Systems and Methods of Use

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10319012B2 (en) 2013-06-27 2019-06-11 Walmart Apollo, Llc View items based on purchases of social media contacts
ES2566066A1 (es) * 2015-10-29 2016-04-08 Universitat D'alacant / Universidad De Alicante Sistema y método para la gestión electrónica de tiques en arquitecturas cloud
WO2017072387A1 (fr) * 2015-10-29 2017-05-04 Universidad De Alicante Système et procédé pour la gestion électronique de tickets dans des architectures nuagiques
US10679264B1 (en) * 2015-11-18 2020-06-09 Dev Anand Shah Review data entry, scoring, and sharing
CN112035767A (zh) * 2020-08-14 2020-12-04 北京三快在线科技有限公司 一种展示提示信息的方法及装置

Similar Documents

Publication Publication Date Title
US8880421B2 (en) System and method for rewarding customer loyalty in a mobile environment
US11157937B2 (en) Smart rewards incentive system, client tools for implementing a smart rewards incentive system, and analytics engine
RU2621630C2 (ru) Система лояльности покупателя в ресторанных и розничных сетях с использованием web-серверов, устройств мобильной связи и терминалов в точке продаж
US20160283973A1 (en) Marketing campaign using engagement value
US20130041733A1 (en) System, method, and computer program product for tip sharing using social networking
US20150088624A1 (en) Location-based task and game functionality
US20140038703A1 (en) Contests and sweepstakes
US20140200997A1 (en) System and Method for Selecting, Distributing, Redeeming, and Reconciling Digital Offers
WO2013148887A1 (fr) Fonctionnalité de jeux et de tâches reposant sur l'emplacement
KR20150023308A (ko) 메뉴 수준 후기 및 보상 시스템
US20170068984A1 (en) Customer reward systems and methods
US20210019778A1 (en) Consumer game
US20120265597A1 (en) Systems and methods for facilitating promotions
US20240005352A1 (en) Managing vendor offers
US20150193806A1 (en) Reward Trading Platform for Generating Improved Customer Information and Feedback
WO2013116708A1 (fr) Programmes d'incitation commerciale basés sur un nuage
US20130211886A1 (en) System and methods for universally administering merchants' loyalty programs
US20210201352A1 (en) Systems and methods for providing group promotions
US11244356B2 (en) Motion data based consumer interfaces
US20150006269A1 (en) System for Facilitating Deals Including the Management of Commissions Associated With Referrals

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13743657

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13743657

Country of ref document: EP

Kind code of ref document: A1