US20080299970A1 - Consumer Registration Via Mobile Device - Google Patents

Abstract

Exemplary embodiments provide systems and methods to receive a transmission that is associated with an identification number and includes a number associated with a land line, determine a physical address based on the number associated with the land line, confirm the physical address that was determined, and associate the physical address with a user account, the user account being identified by the identification number.

Description

FIELD OF THE DISCLOSURE
• Exemplary embodiments of the disclosure are related generally to consumer registration via a mobile device.
BACKGROUND OF THE DISCLOSURE
• Consumer registration via a mobile device may be tedious and time consuming given the complexities associated with providing address and/or payment information via text messaging, for example. If a user is forced into a complex interaction with a mobile device to register, the consumer may opt not to register. Similarly, if a consumer is required to register via an alternative platform, the consumer may opt not to register.
• These and other drawbacks exist.
SUMMARY
• Various exemplary embodiments of the disclosure provide a system including a communication module to receive a transmission associated with an identification number and including a number associated with a land line, an address determination module to determine a physical address based on the number associated with the land line, a confirmation module to confirm the physical address that was determined, and a user account module to associate the physical address with a user account, the user account being identified by the identification number.
• Various exemplary embodiments of the disclosure also provide a method including receiving a transmission associated with an identification number and including a number associated with a land line, determining a physical address based on the number associated with the land line, confirming the physical address that was determined, and associating the physical address with a user account, the user account being identified by the identification number.
• Various exemplary embodiments also provide a computer-accessible medium encoded with computer program code effective to receive a transmission associated with an identification number and including a number associated with a land line, determine a physical address based on the number associated with the land line, confirm the determination of the physical address, and associate the physical address with a user account, the user account being identified by the identification number.
BRIEF DESCRIPTION OF THE DRAWINGS
• FIG. 1 depicts an exemplary consumer registration system according to an embodiment of the disclosure.
• FIG. 2 depicts an exemplary integrated mobile application server according to an embodiment of the disclosure.
• FIG. 3A depicts an exemplary method of consumer registration according to an embodiment of the disclosure.
• FIG. 3B depicts an exemplary method of consumer registration according to an embodiment of the disclosure.
• FIG. 3C depicts an exemplary method of consumer registration according to an embodiment of the disclosure.
• FIG. 4A depicts an exemplary method of consumer registration according to an embodiment of the disclosure.
• FIG. 4B depicts an exemplary method of consumer registration according to an embodiment of the disclosure.
• FIG. 4C depicts an exemplary method of consumer registration according to an embodiment of the disclosure.
• FIG. 5 depicts an exemplary method of obtaining an address of an intended recipient according to an embodiment of the disclosure.
• FIG. 6 depicts an exemplary screen display illustrating exemplary user account information according to an embodiment of the disclosure.
DETAILED DESCRIPTION
• Exemplary embodiments are discussed in detail below. While specific exemplary embodiments are discussed, it should be understood that this is done for illustration purposes only. A person skilled in the relevant art will recognize that other components and configurations can be used without departing from the spirit and scope of the claimed inventions.
• Exemplary embodiments provide systems and methods for consumer registration via, for example, a mobile device. For example, a mobile phone user may register to engage in a promotion or make a purchase using his or her mobile phone. The user may first initiate contact with an integrated mobile application server by transmitting a request to the integrated mobile application server to engage in the promotion or make a purchase. Using the user's mobile phone number as an identifier, the integrated mobile application server may determine whether the user has an existing account. Upon a determination that the user does not have an existing account, the integrated mobile application server may initiate the registration process.
• To register the user, the integrated mobile application server may request that the user provide a phone number associated with a land line. The integrated mobile application server may use this land line number to query a database to obtain a physical address associated with the land line number. Upon obtaining the physical address, the integrated mobile application server may confirm with the user that the address is accurate. Once confirmed, the user may be registered and the integrated mobile application server may create a user account.
• Registering via a mobile device in this manner may enable the user to register and engage in the promotion and/or purchase consumer products within a single interactive session. To register, a user may communicate registration information, including without limitation, a physical address and billing information to an integrated mobile application server to create a user account associated with the user and the integrated mobile application server.
• FIG. 1 depicts anexemplary system100 for consumer registration according to an embodiment of the disclosure.System100 may include anetwork101, one or more users104a-104bassociated with respective requesting devices102a-102band user systems103a-103b, an integratedmobile application server105, a land linepublic database106, azip code database107, acarrier system108, and afulfillment system109. As shown inFIG. 1, requesting devices102a-102buser systems103a-103b, integratedmobile application server105, land linepublic database106,zip code database107,carrier system108, andfulfillment system109 may be coupled vianetwork101. The components ofsystem100 may be part of a single system, or the components may be physically and/or logically separated.
• Network101 may include an analog telephone network, a digital telephone network, a cellular telephone network (e.g., a code-division multiple access (“CDMA”) network, a time division multiple access (“TDMA”) network, a global system for mobile communication (“GSM”) network, a digital cellular or personal communication service (“PCS”) network, and/or an enhanced data GSM environment (EDGE) network), a public wide area network (“WAN”), such as the Internet, or, different connections, such as combinations of public and private WANs, local areas networks (“LANs”), wireless LANs, encrypted networks, body area networks, or other wired or wireless networks. Network101 may be a packet-switched network and receive and transmit data via packets. Network101 may enable communication via the Internet. Network101 may also enable communication via short message service (“SMS”), enhanced messaging service (“EMS”), multimedia messaging service (“MMS”), electronic mail, instant messaging, and/or Wireless Application Protocol (“WAP”). In exemplary embodiments of the disclosure,network101 may include one, or any number of the exemplary types of networks mentioned above operating as a stand-alone network or in cooperation with each other. Use of the term network herein is not intended to limit the network to a single network.
• Requesting devices102a-102bmay be any device capable of communicating with, for example, integratedmobile application server105, vianetwork101. For example, requesting devices102a-102bmay include, but are not limited to: e.g., any computer device, or communications device including, e.g., a personal computer (PC), a workstation, a mobile device, a phone (e.g., a cellular phone), a handheld PC, a personal digital assistant (PDA), a thin system, a fat system, network appliance, an Internet browser, a paging device, an alert device, a television, an interactive television, a receiver, a tuner, a high definition (HD) television, an HD receiver, a video-on-demand (VOD) system, a server, or other device. In various embodiments, requesting devices102a-102bmay also include an interface to display information received from, for example, integratedmobile application server105 and/orcarrier system108 overnetwork101.
• In various exemplary embodiments, requesting devices102a-102bmay be a wireless device, such as a mobile phone or like device, that may be capable of communicating via the Internet, short message service (“SMS”), enhanced messaging service (“EMS”), multimedia messaging service (“MMS”), electronic mail, instant messaging, and/or Wireless Application Protocol (“WAP”). Where requesting devices102a-102bare mobile phones, requesting devices102a-102b, may be capable of initiating and receiving telephone calls and transmitting and receiving text messages.
• User systems103a-103bmay also be any device capable of communicating with, for example, integratedmobile application server105, vianetwork101. For example, user systems103a-103bmay include, but are not limited to: e.g., any computer device, or communications device including, e.g., a personal computer (PC), a workstation, a mobile device, a phone (e.g., a cellular phone), a handheld PC, a personal digital assistant (PDA), a thin system, a fat system, network appliance, an Internet browser, a paging device, an alert device, a television, an interactive television, a receiver, a tuner, a high definition (HD) television, an HD receiver, a video-on-demand (VOD) system, a server, or other device. In various embodiments, user systems103a-103bmay also include an interface to display information received from, for example, integratedmobile application server105 land linepublic database106,zip code database107, and/orfulfillment system109 overnetwork101.
• In various exemplary embodiments, user systems103a-103bmay be computer systems that may be capable of communicating via the Internet. User systems103a-103bmay include a web browser client installed on user system103a-103b, such as INTERNET EXPLORER, NAVIGATOR, or FIREFOX web browser programs, offered by Microsoft Corporation of Redmond, Wash., Time Warner of New York, N.Y., and the Mozilla Foundation of Mountain View, Calif., respectively.
• Users104a-104bmay interact with respective requesting devices102a-102band/or respective user systems103a-103bto communicate with integratedmobile application server105. Users104a-104bmay, for example, interact with their respective requesting devices102a-102bto transmit text messages vianetwork101 to integratedmobile application server105 to engage in a promotion and/or purchase consumer products. For example, user104amay interact with requestingdevice102ato transmit a text message including the phrase “promo” to a number associated with a common short code (“CSC”) that may be associated with integratedmobile application server105. Similarly, user104bmay interact with requestingdevice102bto transmit a text message including the phrase “buy” to a number associated with a common short code (“CSC”) that may be associated with integratedmobile application server105. As will be understood by those having ordinary skill in the art, a CSC may represent a special telephone number that may be used to address SMS and/or MMS messages from mobile phones. Users104a-104bmay also interact with respective requesting devices102a-102bto receive text messages from integratedmobile application server105. Users104a-104bmay also interact with respective requesting devices102a-102bto interact with an interactive voice recognition (“IVR”) system that may be associated with integratedmobile application server105.
• Users104a-104bmay, for example, interact with respective user systems103a-103bto access user account information associated with integratedmobile application server105. For example, using an Internet-enabled computer, users104a-104bmay log into integratedmobile application server105 to access and/or edit user account details such as, address information, payment information, gift recipient information, order history, and/or any other account information as will be described in greater detail below.
• In various exemplary embodiments, integratedmobile application server105 may coupled tonetwork101 and may enable consumer registration via a mobile device as will be described in greater detail below. Integratedmobile application server105 may include an integrated mobile application server as shown and described in U.S. patent application Ser. No. 11/125,833, filed on Mar. 17, 2005, now U.S. Pat. No. ______, the content of which is incorporated herein by reference. As illustrated inFIG. 1, integratedmobile application server105 may be coupled tonetwork101 to communicate with users104a-104bvia respective requesting devices102a-102band/or user systems103a-103b, land linepublic database106,zip code database107,carrier system108, andfulfillment system109.
• Land linepublic database106 may include any data storage device or devices that may store physical address information and associated land line phone numbers. For example, land line public database may store anaddress 123 Any Street, Anytown, AnyState associated with land line number (111) 222-333. Land linepublic database106 may include software, hardware, and/or firmware that may receive a transmission including a land line number (e.g., (111) 222-3333) requesting the associated physical address and return the physical address associated with the land line number to the requester, sender of the transmission, and/or entity accessing land linepublic database106. In various exemplary embodiments, land linepublic database106 may be physically separated from integratedmobile application server105 as illustrated inFIG. 1. Also, land linepublic database106 may be integrated logically separated, but integral with integratedmobile application server105.
• Zip code database107 may include any data storage device or devices that may store zip codes (e.g., postal codes) and associated city and state information. For example,zip code database107 may store a zip code (e.g., 22222) associated with city Anytown and state AnyState.Zip code database107 may include software, hardware, and/or firmware that may receive a request including a zip code (e.g., 22222) and return the associated city and state information.
• Carrier system108 may include any system associated with a mobile service carrier. For example,carrier system108 may include systems associated with mobile service carriers including, without limitation, Verizon Wireless, Nextel Communications, AT&T Wireless, Cingular Wireless, T-Mobile Communications and/or the like.Carrier system108 may store a user's carrier account information. For example,carrier system108 may include one or more data storage devices that may store a user's mobile phone number and associated account information. The associated carrier account information may include, without limitation, the user's billing address. In various exemplary embodiments, with permission from the user, integratedmobile application server105 may access a user's mobile phone account to obtain the user's billing address information. Accordingly,carrier system108 may include software, hardware, and/or firmware that may receive a request associated with a user's mobile phone number and return the user's billing address information.
• Fulfillment system109 may include any system associated with filling orders for consumer products, for example. To fill orders for consumer products,fulfillment system109 may include software, hardware, and/or firmware that may enable fulfillment system to receive user, consumer product, and/or address information and fulfill the order. For example, vianetwork101, a fulfillment system may receive a user's name, the user's address (e.g., 123 Any Street, Anytown, AnyState 22222), and consumer product information (e.g., a Stock Keeping Unit (SKU) and a quantity) to fulfill an order.
• FIG. 2 depicts an exemplary integratedmobile application server200 according to an embodiment of the disclosure. Integratedmobile application server200 may integrate one or more requesting devices and/or user systems with a fulfillment system to enable users to engage in a promotion and/or purchase consumer goods. Integratedmobile application server200 may provide an application server framework that may support multiple telecommunication channels.
• As shown inFIG. 2, integratedmobile application server200 may include one or more of the following modules: acommunication module201, anaddress determination module202, aconfirmation module203, a user account module204, adatabase205, an interactive voice recognition (“IVR”)system206, and aprocessor207. In various exemplary embodiments, each module of integratedmobile application server200 may interact and cooperate with the other modules to enable the integration of requesting devices with fulfillment systems, for example. The various modules of integratedmobile application server200 may be part of a single system, or may be part of a plurality of systems that may be physically and/or logically separated.
• Communication module201 may include hardware, software, and/or firmware to enable communication between and among the modules of integratedmobile application server200 and between of integratedmobile application server200 other elements of a network. For example,communication module201 may allow communication between user account module204 anddatabase205, and/or betweencommunication module201 and interactivevoice recognition system205 and/or betweenconfirmation module203 and addressdetermination module202.
• Also, communication module may allow communication between of integratedmobile application server200 and elements of a network including, without limitation, requesting devices, user systems, land line public databases, zip code databases, carrier systems, and fulfillment systems.Communication module201 may communicate with network elements via any number of protocols.Communication module201 may also enable integratedmobile application server200 to make requests to network elements. For example,communication module201 may enable of integratedmobile application server200 to request a land line number and/or zip code from a requesting device.Communication module201 may also enable integratedmobile application server200 to query external databases that may be associated with, for example, land line public databases, zip code databases, and/or carrier systems.Communication module201 may enable integratedmobile application server200 to receive responses from requesting devices and/or other network elements (e.g., user systems and/or databases).
• Address determination module202 may include hardware, software, and/or firmware to enable integratedmobile application server200 to determine a physical address associated with a land line number, for example.Address determination module202 may also enable integratedmobile application server200 to determine city and state information associated with a zip code.Address determination module202 may also enable integratedmobile application server200 to compile a physical address based on a zip code, city and state information, and a street address.
• Confirmation module203 may include hardware, software, and/or firmware to enable integratedmobile application server200 to transmit and receive confirmations to and from requesting devices. For example,confirmation module203 may enable integratedmobile application server200 to transmit an address or PIN confirmation to a requesting device.Confirmation module203 may also enable integratedmobile application server200 to receive confirmation responses from requesting devices, for example.
• User account module204 may include hardware, software, and/or firmware to enable integratedmobile application server200 to create, update, and/or maintain user account information (See,FIG. 6, for example). User account module204 may interact withdatabase205 to store user account information associated with integratedmobile application server200. User account module204 may also determine user account information based on an identification number. For example, given a mobile phone number, user account module204 may retrieve associated user account information fromdatabase205. Also, user account module204 may cooperate and/or interact with address determination module to store addresses associated with user accounts.
• Database205 may include one or more data storage devices associated with integratedmobile application server200.Database205 may store user account information, consumer product information (e.g., unique identifiers and associated consumer product information), land line number information, zip code information, carrier system information, and/or any other information that may be used by integratedmobile application server200.
• Integratedvoice recognition system206 may include hardware, software, and/or firmware that may provide interactive voice response via telephone systems. For example,IVR206 may enable customers to interact with integratedmobile application server200 to provide information to integratedmobile application server200. For example,IVR206 may call a requesting device to initiate an interactive voice response session during which a customer inputs land line number information, zip code information, payment information, and/or the like.IVR206 may cooperate withdatabase205 to store information received viaIVR206.
• Processor207 may include hardware, software, and/or firmware to enable the operation of integratedmobile application server200. For example,processor207 may include hardware, software, and/or firmware to enable the execution of instructions to perform the operations of integratedmobile application server200.
• FIGS. 3A,3B, and3C depict aflow chart300 illustrating an exemplary method for consumer registration according to an embodiment of the disclosure. In various exemplary embodiments, a user (e.g., a consumer) may register via a mobile device to engage in a promotion or purchase consumer products.
• Inblock301, a request may be received. For example, an integrated mobile application server may receive a request from a requesting device. This request may be associated with an identification number that may be associated with the requesting device. For example, the request may be associated with a mobile number of a mobile phone or like device. In various exemplary embodiments, the request may be transmitted from a requesting device to the integrated mobile application server in the form of a text message, SMS message, EMS message, MMS message, electronic mail, instant message, wireless web upload, WAP mini site link. The request received may also include a unique identifier or code that is associated with a consumer product. For example, the request may include a unique identifier “BIC” which is associated with a Blue Bic® ballpoint pen. To transmit the request to be received by the integrated mobile application server, a user of a requesting device (e.g., a mobile phone) may transmit a text message to a CSC associated with the integrated mobile application server.
• Inblock302, a determination may be made as to whether the received request is related to a promotion or a purchase. An integrated mobile application server may store information associating the unique identifier or code with the an indication as to whether the unique identifier is associated with a promotion or a purchase. For example, the integrated mobile application server may store information associating the unique identifier “BIC” with a consumer product promotion. Also, the integrated mobile application server may store information associating the unique identifier “BIC” with a consumer product being purchased. To make this determination, an integrated mobile application server may query a database using the unique identifier as a key into the database. Upon a determination that the request is for a promotion,flow chart300 may proceed to block303. Upon making a determination that the request is for a purchase,flow chart300 may proceed to block324.
• In block303, a user may be identified. For example, upon receiving a request for a promotion, in block303, an integrated mobile application server may identify the user by determining the user's identification number, and if applicable, an associated carrier service. For example, where a request is in the form of a text message transmitted by the user from a mobile phone (e.g., (123) 456-7890), an integrated mobile application server may identify the user by determining the user's mobile phone number and, if applicable, the user's mobile phone carrier service (e.g., T-Mobile).
• Inblock304, a determination may be made as to whether the user has an account associated with the identification number. As described above, an integrated mobile application server may store user accounts that may be identified by an identification number. Upon identifying the user in block303, an identification number may be determined. This identification number may be used to query a user account database associated with an integrated mobile application server to determine whether the user has an account. For example, where a user's associated identification number is (123) 456-7890, an integrated mobile application server may query an associated user account database using a key such as 1234567890 to determine whether the user has an associated account. Upon a determination that the user has an associated user account,flow chart300 may proceed to block315. Upon a determination that the does not have an associated user account, flow chart may proceed to block305.
• Inblock305, a user account may be created. In various exemplary embodiments, an integrated mobile application server may create account in an associated user account database. This account may be identified by an identification number associated with the user and/or requesting device. For example, the account may be identified by the mobile phone associated with the user and/or requesting device (e.g., (123) 456-7890 or 1234567890) The user account may store associated user account information as will be described in greater detail below with respect toFIG. 6.
• Inblock306, a land line number may be requested. A land line number may be used to obtain physical address information associated with the user and/or a gift recipient. To request a land line, an integrated mobile application server may communicate with the requesting device to prompt the user to transmit a land line number to the integrated mobile application server. In an exemplary embodiment, the integrated mobile application server may transmit a message (e.g., a text message) to the requesting device and/or a device associated with the identification number prompting the user to reply with a land line number. Also, an integrated mobile application server may interact with an UVR system to communicate with the requesting device and/or a device associated with the identification number to prompt the user to input a land line number into the IVR.
• Inblock307, a land line number may be received. An integrated mobile application server may receive the land line number from a requesting device and/or device associated with the identification number. In an exemplary embodiment, the land line number may be received in a text message transmitted to a CSC associated with the integrated mobile application server. For example, a mobile phone associated with the identification number may transmit a text message including “1112223333” in the body of the message as a land line number. Also, by interacting with an IVR, a user may input (e.g., speak and/or enter via a keypad associated with the requesting device) the land line number “1112223333” into the IVR. The land line number may be transmitted to the integrated mobile application server.
• Inblock308, a physical address associated with the received land line number may be obtained. To obtain the physical address, using the land line number, an integrated mobile application server may access a land line public database and query the land line public database for a physical address associated with the land line number. In various exemplary embodiments, the integrated mobile application server may communicate with the land line public database via a network. Also, the land line database may be integral with the integrated mobile application server.
• Inblock309, a determination may be made as to whether a physical address was obtained from the land line public database. For example, if the land line public database is queried and a physical address is associated with the land line number, a determination may be made that the physical address was obtained. If the land line public database is queried and a physical address is not associated with the land line number or there is not an entry in the land line public database associated with the land line number, a determination may be made that a physical address was not obtained. Upon a determination that a physical address was obtained,flow chart300 may proceed to block310. Upon a determination that a physical address was not obtained, flow chart may proceed to block319.
• Inblock310, an address confirmation may be transmitted. To confirm an address, an integrated mobile application server may communicate with the requesting device to confirm that the physical address obtained from the land line public database is correct and/or accurate. In an exemplary embodiment, the integrated mobile application server may transmit a message (e.g., a text message) to the requesting device and/or a device associated with the identification number prompting the user to reply with a confirmation indicating that the physical address is correct and/or accurate. For example, the integrated mobile application server may transmit a text message to the requesting device prompting the user to reply “1” if the physical address is “123 Any Street, Anytown,AnyState 22222” or reply “2” if the address is not s “123 Any Street, Anytown,AnyState 22222.” Also, an integrated mobile application server may interact with an IVR system to communicate with the requesting device and/or a device associated with the identification number to communicate the address “123 Any Street, Anytown,AnyState 22222” to the requesting device and prompt the user to reply “Yes” or “No” into the IVR (by speaking a response or inputting a “1” for “Yes” or “2” for “No” into a keypad associated with the requesting device).
• Inblock311, an address confirmation may be received. An integrated mobile application server may receive the text message and/or IVR confirmation response from the requesting device.
• Inblock312, a determination may be made as to whether the physical address has been confirmed. For example, if the user replies to a text message with “1” to confirm or inputs “Yes” or “1” into an IVR, the physical address may be confirmed. If, for example, the user replies to a text message with a “2” to confirm or inputs “No” or “2” into an IVR, the physical address may not be confirmed. Upon a confirmation of the physical address,flow chart300 may proceed to block313. Upon a failed confirmation of the physical address,flow chart300 may proceed to block319.
• Inblock313, an account may be updated. An integrated mobile application server may update an account identified by an identification number associated with a requesting device to include the physical address. For example, account 1234567890 may be updated to include a physical address “123 Any Street, Anytown,AnyState 22222.”
• Inblock314, the physical address may be transmitted to a fulfillment system. In various exemplary embodiments, an integrated mobile application server may communicate with a fulfillment system via a network to transmit the address to a fulfillment system. Also, consumer product information (e.g., one Blue Bic® ballpoint pen) may be transmitted to the fulfillment system so that the fulfillment system may ship one Blue Bic® ballpoint pen to “123 Any Street, Anytown,AnyState 22222.”
• Inblock319, a zip code associated with a physical may be requested. To request a zip code, an integrated mobile application server may communicate with the requesting device to prompt the user to transmit a zip code to the integrated mobile application server. In an exemplary embodiment, the integrated mobile application server may transmit a message (e.g., a text message) to the requesting device and/or a device associated with the identification number prompting the user to reply with a zip code. Also, an integrated mobile application server may interact with an IVR system to communicate with the requesting device and/or a device associated with the identification number to prompt the user to input a zip code into the IVR.
• Inblock320, a zip code may be received. An integrated mobile application server may receive the zip code from a requesting device and/or device associated with the identification number. In an exemplary embodiment, the zip code may be received in a text message transmitted to a CSC associated with the integrated mobile application server. For example, a mobile phone associated with the identification number may transmit a text message including “22222” in the body of the message as a zip code. Also, by interacting with an IVR, a user may input (e.g., speak and/or enter via a keypad associated with the requesting device) the zip code “22222” into the IVR. The zip code may be transmitted to the integrated mobile application server.
• Inblock321, a city and state associated with a zip code may be determined. In an exemplary embodiment, a zip code database may store information associating zip codes with respective city and state information. For example, a zip code database may store information associating zip code “22222” with the city “Anytown” and state “AnyState.” Using the zip code as a key, a zip code database may be queried for the associated city and state information. This associated city and state information may be returned to the integrated mobile application server.
• Inblock322, a street address associated with a physical may be requested. To request a street address, an integrated mobile application server may communicate with the requesting device to prompt the user to transmit a street address to the integrated mobile application server. In an exemplary embodiment, the integrated mobile application server may transmit a message (e.g., a text message) to the requesting device and/or a device associated with the identification number prompting the user to reply with a street address. For example, the integrated mobile application server may transmit a text message to a requesting device prompting a user to reply with a street address located in “Anytown, AnyState.” Also, an integrated mobile application server may interact with an IVR system to communicate with the requesting device and/or a device associated with the identification number to prompt the user to input a street address located in “Anytown, AnyState” into the IVR.
• Inblock323, a street address may be received. An integrated mobile application server may receive the street address from a requesting device and/or device associated with the identification number. In an exemplary embodiment, the street address may be received in a text message transmitted to a CSC associated with the integrated mobile application server. For example, a mobile phone associated with the identification number may transmit a text message including “123 Any Street” in the body of the message as a street address. Also, by interacting with an IVR, a user may input (e.g., speak and/or enter via a keypad associated with the requesting device) the street address “123 Any Street” into the IVR. The zip code may be transmitted to the integrated mobile application server. Other information including, without limitation, the user's name, email address, and/or any other account information to create a user account may be requested and received in a similar manner as described. Upon receipt of a street address, a user account may be updated in a similar manner as described above forblock313. Once the user account is updated, the physical address may be transmitted to a fulfillment system in a similar manner as described above forblock314.
• Inblock315, an address confirmation may be transmitted in a similar manner as described above forblock310.
• Inblock316, an address confirmation may be received in a similar manner as described above forblock311.
• Inblock317, a determination may be made as to whether the physical address has been confirmed in a similar manner as described above forblock312. Upon a determination that a physical address has not been confirmed,flow chart300 may proceed to block306. Upon a determination that a physical address has been confirmed,flow chart300 may proceed to block318.
• Inblock318, a physical address may be transmitted to a fulfillment system in a similar manner as described above forblock314.
• As noted above, upon a determination that a request is associated with a purchase of a consumer product,flow chart300 may proceed to block324. As illustrated inFIG. 3C, in block324, a user may be identified in a similar manner as described above for block303.
• Inblock325, a determination may be made as to whether the user has an associated user account associated in a similar manner as described above forblock304. Upon a determination that the user has an associated user account,flow chart300 may proceed to block339. Upon a determination that a user does not have an associated user account,flow chart300 may proceed to block326.
• Inblock326, a user account may be created in a similar manner as described above forblock305.
• Inblock327, a land line number may be requested in a similar manner as described above forblock306.
• Inblock328, a land line number may be received in a similar manner as described above forblock307.
• Inblock329, a physical address associated with the received land line number may be obtained in a similar manner as described above forblock308.
• Inblock330, a determination may be made as to whether a physical address was obtained in a similar manner as described above forblock309. Upon making a determination that a physical address was obtained,flow chart300 may proceed to block336. Upon making a determination that a physical address was not obtained,flow chart300 may proceed to block331.
• Inblock331, a zip code may be requested in a similar manner as described above forblock319.
• Inblock332, a zip code may be received in a similar manner as described above forblock320.
• Inblock333, a city and state associated with the zip code may be determined in a similar manner as described above forblock321.
• Inblock334, a street address associated with the city and state may be requested in a similar manner as described above forblock322.
• Inblock335, a street address may be received in a similar manner as described above forblock323.
• As noted above, upon a determination inblock330 that a physical address was obtained, flow chart may proceed to block336. Inblock336, an address confirmation may be transmitted in a similar manner as described above forblock310.
• Inblock337, an address confirmation may be received in a similar manner as described above forblock311.
• Inblock338, a determination may be made as to whether a physical address has been confirmed in a similar manner as described above forblock312. Upon a determination that a physical address has not been confirmed,flow chart300 may proceed to block331. Upon a determination that a physical address has been confirmed,flow chart300 may proceed to block341.
• As noted above, upon a determination inblock325 that a user has an associated user account,flow chart300 may proceed to block339. Inblock339, a determination may be made as to whether a physical address is associated with the user account. In various exemplary embodiments, a user account may be identified by an identification number. To determine whether a physical address is associated with a user account, a user account database may be queried using the identification number. If a user account has an associated physical address, the physical address may be returned in response to the query. If a user account does not have an associated physical address, a null response may be returned in response to the query, for example. Upon a determination that physical address is not associated with the user account,flow chart300 may proceed to block327. Upon a determination that a user account has an associated physical address,flow chart300 may proceed to block340.
• Inblock340, a determination may be made as to whether payment information is associated with the user account. To determine whether payment information is associated with a user account, a user account database may be queried using the identification number. If a user account has associated payment information, the payment information may be returned in response to the query. If a user account does not have associated payment information, a null response may be returned in response to the query, for example. Upon a determination that payment information is not associated with the user account,flow chart300 may proceed to block341. Upon a determination that a user account has associated payment information,flow chart300 may proceed to block346.
• Inblock341, payment information may be requested. To request payment information, an integrated mobile application server may communicate with the requesting device to prompt the user to transmit payment information to the integrated mobile application server. In an exemplary embodiment, the integrated mobile application server may transmit a message (e.g., a text message) to the requesting device and/or a device associated with the identification number prompting the user to reply with payment information. Also, an integrated mobile application server may interact with an IVR system to communicate with the requesting device and/or a device associated with the identification number to prompt the user to input payment information number into the IVR.
• Inblock342, payment information may be received. An integrated mobile application server may receive the payment information from a requesting device and/or device associated with the identification number. In an exemplary embodiment, the payment information may be received in a text message transmitted to a CSC associated with the integrated mobile application server. For example, a mobile phone associated with the identification number may transmit a text message including “111122223333444 exp1010” in the body of the message as payment information. In various exemplary embodiment, this payment information may be securely transmitted using, for example, any number of various encryption techniques. Also, by interacting with an IVR, a user may input (e.g., speak and/or enter via a keypad associated with the requesting device) the payment information (e.g., account number and/or associated expiration date) into the IVR. The payment information may be transmitted to the integrated mobile application server.
• Inblock343, a personal identification number (PIN) associated with a user account may be determined. In an exemplary embodiment, an integrated mobile application server may randomly determine a PIN to be associated with the user account. In such an embodiment, the integrated mobile application server may communicate the PIN via a text message and/or IVR system. Also, to determine a PIN, user may select the PIN and communicate the PIN to the integrated mobile application server. This PIN may be associated with the user account and stored within the integrated mobile application server.
• Inblock344, a user account may be updated in a similar manner as described above forblock313.
• Inblock345, a transaction may be processed. As noted above, a request may include a unique identifier “BIC” that is associated with a Blue Bic® ballpoint pen. To process the transaction, an integrated mobile application server may interact with a fulfillment system to transmit the request for a Blue Bic® ballpoint pen to be shipped to a physical address associated with the user account. Integrated mobile application server may also interact with a payment interface to process payment of the transaction in accordance with the associated payment information.
• As noted above, upon a determination that a user has an associated user account, a physical address is associated with the user account, and payment information is associated with the user account,flow chart300 may proceed to block346. Inblock346, a PIN confirmation may be transmitted. To confirm a PIN, an integrated mobile application server may communicate with the requesting device to request the PIN. In an exemplary embodiment, the integrated mobile application server may transmit a message (e.g., a text message) to the requesting device and/or a device associated with the identification number prompting the user to reply with the PIN. For example, the integrated mobile application server may transmit a text message to the requesting device prompting the user to reply with the user's PIN if the user desires to purchase “one Blue Bic® ballpoint pen to be shipped to 123 Any Street, Anytown,AnyState 22222.” Also, an integrated mobile application server may interact with an IVR system to communicate with the requesting device and/or a device associated with the identification number to communicate the PIN via the IVR (by speaking a response or inputting the PIN into a keypad associated with the requesting device).
• Inblock347, a PIN confirmation may be received. An integrated mobile application server may receive the text message and/or IVR confirmation response from the requesting device.
• Inblock348, a determination may be made as to whether the PIN has been confirmed. For example, if the user replies to a text message with the correct PIN or inputs the correct PIN into the IVR, the PIN may be confirmed. If, for example, the user replies to a text message with an incorrect PIN or inputs an incorrect PIN into an IVR, the PIN may not be confirmed. Upon a confirmation of the PIN,flow chart300 may proceed to block345. Upon a failed confirmation of the PIN,flow chart300 the transaction may be cancelled inblock349 or the PIN may be re-requested andflow chart300 may proceed to block347 to receive the PIN and subsequently confirm the PIN.
• FIGS. 4A,4B, and4C depict aflow chart400 illustrating an exemplary method for consumer registration according to an embodiment of the disclosure. In various exemplary embodiments, a user (e.g., a consumer) may register via a mobile device to engage in a promotion or purchase consumer products.
• Inblock401, a request may be received in a similar manner as described above forblock301.
• Inblock402, a determination may be made as to whether the received request is related to a promotion or a purchase in a similar manner as described above forblock302. Upon a determination that the request is for a promotion,flow chart400 may proceed to block403. Upon making a determination that the request is for a purchase,flow chart300 may proceed to block429.
• Inblock403, a user may be identified in a similar manner as described above for block303.
• Inblock404, a determination may be made as to whether the user has an associated user account associated in a similar manner as described above forblock304. Upon a determination that the user has an associated user account,flow chart400 may proceed to block425. Upon making a determination that a user does not have an associated user account,flow chart400 may proceed to block405.
• Inblock405, a user account may be created in a similar manner as described above forblock305.
• Inblock406, permission to access a user's carrier account may be requested. As noted above, in various embodiments, a land line number may be used to obtain a physical address associated with the user. Carrier account information may also be used to obtain a physical address of the user. In these embodiments, an integrated mobile application server may need permission from the user to access the user's carrier account information. As noted above, a carrier may refer to a mobile phone carrier service. Carrier account information may be associated with a carrier system. With permission from the user, an integrated mobile application server may access carrier account information via a network. To request permission, an integrated mobile application server may determine the user's carrier service (see block303) and communicate with the requesting device to request permission to access the user's carrier account information and prompt the user to transmit a permission response to the integrated mobile application server. In an exemplary embodiment, the integrated mobile application server may transmit a message (e.g., a text message) to the requesting device and/or a device associated with the identification number requesting access to the user's “T-Mobile” account, for example, and prompting the user to reply “1” if permission is granted or “2” if permission is not granted. Also, an integrated mobile application server may interact with an IVR system to communicate with the requesting device and/or a device associated with the identification number to prompt the user to input a permission response into the IVR.
• Inblock407, a permission response may be received. An integrated mobile application server may receive the permission response from a requesting device and/or device associated with the identification number. In an exemplary embodiment, the permission response may be received in a text message transmitted to a CSC associated with the integrated mobile application server. For example, a mobile phone associated with the identification number may transmit a text message including “1” in the body of the message as a permission response. Also, by interacting with an IVR, a user may input (e.g., speak and/or enter via a keypad associated with the requesting device) the permission response “Yes” or “1” into the IVR. The permission response may be transmitted to the integrated mobile application server.
• Inblock408, a determination may be made as to whether permission to access the user's carrier account information has been granted. For example, if the user replies to a text message with “1” to confirm or inputs “Yes” or “1” into an IVR, permission may be granted. If, for example, the user replies to a text message with a “2” to confirm or inputs “No” or “2” into an IVR, permission may not be granted. Upon a granting of permission,flow chart400 may proceed to block418. Upon permission not being granted,flow chart400 may proceed to block409.
• Inblock409, a land line number may be requested in a similar manner as described above forblock306.
• Inblock410, a land line number may be received in a similar manner as described above forblock307.
• Inblock411, a physical address associated with the received land line number may be obtained in a similar manner as described above forblock308.
• Inblock412, a determination may be made as to whether a physical address was obtained in a similar manner as described above forblock309. Upon a determination that a physical address was obtained,flow chart400 may proceed to block420. Upon a determination that a physical address was not obtained,flow chart400 may proceed to block413.
• Inblock413, a zip code may be requested in a similar manner as described above forblock319.
• Inblock414, a zip code may be received in a similar manner as described above forblock320.
• Inblock415, a city and state associated with the zip code may be determined in a similar manner as described above forblock321.
• Inblock416, a street address associated with the city and state may be requested in a similar manner as described above forblock322.
• Inblock417, a street address may be received in a similar manner as described above forblock323.
• As noted above, upon a granting of permission to access carrier account information, inblock418, carrier account information may be requested. To request carrier information, an integrated mobile application server may communicate with a carrier system via a network to query the carrier system and/or a database associated with the carrier system using the identification number. For example, an integrated mobile application server system may query carrier a database associated with carrier server system to return a physical address associated with mobile number “(123) 456-7890).
• Inblock419, the physical address associated with the identification number may be received by an integrated mobile application system.
• Inblock420, an address confirmation may be transmitted in a similar manner as described above forblock310.
• Inblock421, an address confirmation may be received in a similar manner as described above forblock311.
• In block422 a determination may be made as to whether the physical address has been confirmed in a similar manner as described above forblock312. Upon a determination that a physical address has not been confirmed,flow chart400 may proceed to block413. Upon a determination that a physical address has been confirmed,flow chart400 may proceed to block423.
• Inblock423, a user account may be updated in a similar manner as described above forblock313.
• Inblock424, a physical address may be transmitted to a fulfillment system in a similar manner as described above forblock314.
• As noted above, upon a determination that a user account is associated with an identification number,flow chart400 may proceed to block425. Inblock425 an address confirmation may be transmitted in a similar manner as described above forblock310.
• Inblock426, an address confirmation may be received in a similar manner as described above forblock311.
• In block427 a determination may be made as to whether the physical address has been confirmed in a similar manner as described above forblock312. Upon a determination that a physical address has not been confirmed,flow chart400 may proceed to block406. Upon a determination that a physical address has been confirmed,flow chart400 may proceed to block428.
• Inblock428, a physical address may be transmitted to a fulfillment system in a similar manner as described above forblock314.
• As noted above, upon a determination that a request is associated with a purchase of a consumer product,flow chart400 may proceed to block429. As illustrated inFIG. 4C, inblock429, a user may be identified in a similar manner as described above for block303.
• Inblock430, a determination may be made as to whether the user has an associated user account associated in a similar manner as described above forblock304. Upon a determination that the user has an associated user account,flow chart400 may proceed to block431. Upon making a determination that a user does not have an associated user account,flow chart400 may proceed to block433.
• Inblock433, a user account may be created in a similar manner as described above forblock305.
• Inblock434, permission to access a user's carrier account may be requested in a similar manner as described above forblock406.
• Inblock435, a permission response may be received in a similar manner as described above forblock407.
• Inblock436, a determination may be made as to whether permission to access carrier account information has been granted in a similar manner as described above forblock408. Upon a determination that permission is granted,flow chart400 may proceed to block437. Upon a determination that permission is not granted,flow chart400 may proceed to block442.
• Inblock442, a land line number may be requested in a similar manner as described above forblock306.
• Inblock443, a land line number may be received in a similar manner as described above forblock307.
• Inblock444, a physical address associated with the received land line number may be obtained in a similar manner as described above forblock308.
• Inblock445, a determination may be made as to whether a physical address was obtained in a similar manner as described above forblock309. Upon making a determination that a physical address was obtained,flow chart400 may proceed to block439. Upon making a determination that a physical address was not obtained,flow chart400 may proceed to block446.
• Inblock446, a zip code may be requested in a similar manner as described above forblock319.
• Inblock447, a zip code may be received in a similar manner as described above forblock320.
• Inblock448, a city and state associated with the zip code may be determined in a similar manner as described above forblock321.
• Inblock449, a street address associated with the city and state may be requested in a similar manner as described above forblock322.
• Inblock450, a street address may be received in a similar manner as described above forblock323.
• As noted above, upon a granting of permission to access carrier account information, inblock437, carrier account information may be requested in a similar manner as described above forblock418.
• Inblock438, the carrier account information may be received in a similar manner as described above forblock419.
• Inblock439, an address confirmation may be transmitted in a similar manner as described above forblock310.
• Inblock440, an address confirmation may be received in a similar manner as described above forblock311.
• In block441 a determination may be made as to whether the physical address has been confirmed in a similar manner as described above forblock312. Upon a determination that a physical address has not been confirmed,flow chart400 may proceed to block446. Upon a determination that a physical address has been confirmed,flow chart400 may proceed to block455.
• Inblock455, payment information may be requested in a similar manner as described above forblock341.
• Inblock456, payment information may be received in a similar manner as described above forblock342.
• Inblock457, a PIN may be determined in a similar manner as described above forblock343.
• Inblock458, an account may be updated in a similar manner as described above forblock313.
• Inblock459, a transaction may be processed in a similar manner as described above forblock345.
• As noted above, upon making a determination that a user has an account associated with an identification number, inblock431, a determination may be made as to whether an address is associated with the account in a similar manner as described above forblock339. Upon a determination that a user account is not associated with an address,flow chart400 may proceed to block433. Upon a determination that an address is associated with the user account,flow chart400 may proceed to block432.
• Inblock432, a determination may be made as to whether payment information is associated with the user account in a similar manner as described above forblock340. Upon a determination that payment information is not associated with the user account,flow chart400 may proceed to block455. Upon a determination that payment information is associated with the user account,flow chart400 may proceed to block451. Inblock451, a PIN confirmation may be transmitted in a similar manner as described above forblock346.
• Inblock452, a PIN response may be received in a similar manner as described above forblock347.
• Inblock453, a determination may be made as to whether the PIN is confirmed in a similar manner as described above forblock348. Upon a determination that the PIN has been confirmed,flow chart400 may proceed to block459. Upon a determination that the PIN has not been confirmed,flow chart400 may proceed to block454 to cancel the transaction or re-request the PIN. If the PIN is re-requested,flow chart400 may proceed to block452 to receive a PIN confirmation.
• FIG. 5 depicts aflow chart500 which illustrates an exemplary method for registering consumer shipping addresses via a mobile device, for example. In various exemplary embodiments, a user may have a user account and associated account information. A user may wish to purchase a consumer product using methods described above, and may intend that the recipient of the consumer product be a gift recipient and/or that the consumer product be shipped to an address other than the address associated with the user's account. For example, a user may wish to purchase a Blue Bic® ballpoint pen to be given to the user's mother. Also, the user may wish to purchase the Blue Bic® ballpoint pen to be shipped to the user's office address instead of the home address associated with the user account.
• Inblock501, a request may be received in a similar manner as described above forblock301.
• Inblock502, the user may be identified in a similar manner as described above forblock302.
• Inblock503, a determination may be made as to whether a user account is associated with an identification number in a similar manner as described above forblock304. Upon a determination that a user account is associated with an identification number,flow chart500 may proceed to block504. Upon a determination that a user account is not associated with an identification number, inblock523, the user may be registered in a similar manner as described above.
• Inblock504, a PIN confirmation may be transmitted in a similar manner as described above forblock346.
• Inblock505, a PIN response may be received in a similar manner as described above forblock347.
• Inblock506, a determination may be made as to whether the PIN is confirmed in a similar manner as described above forblock348. Upon a determination that the PIN has been confirmed,flow chart500 may proceed to block508. Upon a determination that the PIN has not been confirmed,flow chart500 may proceed to block507 to cancel the transaction or re-request the PIN. If the PIN is re-requested,flow chart500 may proceed to block505 to receive a PIN confirmation.
• Inblock508, a determination may be made as to whether the ship the consumer product to the physical address on file. In various exemplary embodiments, an integrated mobile application server may communicate with a requesting device and/or a device associated with the identification number to prompt the user regarding where to ship the consumer product. For example, to prompt the user, an integrated mobile application server may communicate with the requesting device to prompt the user to transmit an affirmative indicator if the user desires to ship the consumer product to the address on file (and may also communicate the address to the user) to the integrated mobile application server. In an exemplary embodiment, the integrated mobile application server may transmit a message (e.g., a text message) to the requesting device and/or a device associated with the identification number prompting the user to reply with “1” if the user desired to ship the consumer product to the address on file or a “2” if the user desires to ship the consumer product elsewhere. Also, an integrated mobile application server may interact with an IVR system to communicate with the requesting device and/or a device associated with the identification number to prompt the user to input a response regarding where to ship the consumer product into the IVR.
• Inblock509, a land line number may be requested in a similar manner as described above forblock306. In various exemplary embodiments, this land line number may be requested to prompt the user input a land line associated with a physical address where the user desires the consumer product to be shipped. This address, once determined, may be associated with the user account and, for example, an identifier of the address so that the user may ship future shipments to this address. For example, a user may desire to ship the consumer product to the user's mother, whose land line number is (222) 333-4444 and the associated address is 456 Other Street, Othertown, OtherState, 11111.
• Inblock510, a land line number may be received in a similar manner as described above forblock307. For example, an integrated mobile application server may receive a land line number (222) 333-4444.
• Inblock511, an address associated with the received land line number may be obtained in a similar manner as described forblock308. For example, using (222) 333-4444 as a key, a land line public database may be queried to return an address associated with the land line number.
• Inblock512, a determination may be made as to whether a physical address was obtained in a similar manner as described above forblock309. Upon making a determination that a physical address was obtained,flow chart500 may proceed to block513. Upon making a determination that a physical address was not obtained,flow chart500 may proceed to block518.
• Inblock518, a zip code associated with the address of the intended recipient may be requested in a similar manner as described above forblock319.
• Inblock519, a zip code may be received in a similar manner as described above forblock320.
• Inblock520, a city and state associated with the zip code of the address of the intended recipient may be determined in a similar manner as described above forblock321.
• Inblock521, a street address associated with the city and state of the intended recipient may be requested in a similar manner as described above forblock322.
• Inblock522, a street address may be received in a similar manner as described above forblock323.
• As noted above, upon making a determination that a physical address was obtained,flow chart500 may proceed to block513. Inblock513, an address confirmation may be transmitted in a similar manner as described above forblock310. The address confirmation may seek confirmation of the address of the intended recipient.
• Inblock514, an address confirmation may be received in a similar manner as described above forblock311.
• Inblock515, a determination may be made as to whether the physical address of the intended recipient has been confirmed in a similar manner as described above forblock312. Upon a determination that a physical address has not been confirmed,flow chart500 may proceed to block516. Upon a determination that a physical address has been confirmed,flow chart500 may proceed to block518.
• Inblock516, a user account may be updated. For example, the physical address of the intended recipient (e.g., the gift recipient or an alternative shipping address) may be associated with the user account. A identifier may also be associated with the physical address of the intended recipient as will be described in greater detail below with respect toFIG. 6.
• Inblock517, a physical address of the intended recipient may be transmitted to a fulfillment system in a similar manner as described above forblock314.
• FIG. 6 depicts anexemplary screen display600 ofuser account information601. As shown inFIG. 6, a user account may be identified by anaccount number602. In various exemplary embodiments, the account number may be associated with a requesting device and/or an identification number associated with a requesting device. For example, an account may be identified by a mobile phone number of a user.
• Account information601 may also include a user'spersonal information603,payment information604, shippinginformation605,gift recipient information606, and/or alternativeshipping location information607.Screen display600 may also include additional account features608 that may enable a user to access and/or edit account information, for example.
• Personal information603 may include a user's name and address. For example personal information may include a name, street address, city, state, and zip code.
• Payment information604 may include a billing address of the user, associated payment account information (e.g., credit card account information, debit account information, demand deposit account information, prepaid account information, Internet-based account information and/or other like account information). Although only on account is illustrated, payment account information may be associated with a user account and, during the purchase of a consumer product, for example, a user may select a payment method in a similar manner as described above for identifying a gift recipient or alternative shipping location for the consumer product. For example, an integrated mobile application server prompt a user via a text message or IVR to provide input as to which payment method the user selects.
• Shipping information605 may identify the physical address where consumer products are to be shipped.
• Gift recipient information606 may include thepersonal information606aof a gift recipient and anidentifier606bassociated with the recipient (e.g., “MOM”). The gift recipient's address may be obtained using the gift recipients land line number and/or zip code as described above.
• Alternative shipping information607 may include thepersonal information607aassociated with an alternative shipping address of a user, for example, and an identifier associated with the alternative shipping address (e.g., “WORK”). The alternative shipping address information may be obtained using a land line number and/or zip code as described above.
• Additional account features608 may enable the user to view the user's order history, edit user account information, add a gift recipient, and/or alternative shipping location.
• The present disclosure is not to be limited in scope by the specific embodiments described herein. Indeed, other various embodiments of and modifications to the present disclosure, in addition to those described herein, will be apparent to those of ordinary skill in the art from the foregoing description and accompanying drawings. Thus, such other embodiments and modifications are intended to fall within the scope of the present disclosure. Further, although the present disclosure has been described herein in the context of a particular implementation in a particular environment for a particular purpose, those of ordinary skill in the art will recognize that its usefulness is not limited thereto and that the present disclosure may be beneficially implemented in any number of environments for any number of purposes. Accordingly, the claims set forth below should be construed in view of the full breadth and spirit of the present disclosure as described herein.

Claims (39)

1. A system, comprising:

a communication module to receive a transmission, the transmission being associated with an identification number and including a number associated with a land line;

an address determination module to determine a physical address based on the number associated with the land line;

a confirmation module to confirm the physical address that was determined; and

a user account module to associate the physical address with a user account, the user account being identified by the identification number.

2. The system according toclaim 1, wherein the communication module transmits a request to the user to initiate the transmission including the number associated with the land line.

3. The system according toclaim 2, wherein the communication module transmits a message to a device associated with the identification number.

4. The system according toclaim 3, wherein the message comprises a text message.

5. The system according toclaim 2, further comprising:

an interactive voice recognition system to prompt the user to input the number associated with a land line.

6. The system according toclaim 1, wherein the address determination module queries a land line public database and receives a response from the land line public database, wherein the response includes the physical address.

7. The system according toclaim 1, wherein the confirmation module transmits a message including the physical address to a device associated with the identification number to confirm the physical address.

8. The system according toclaim 7, wherein the message comprises a text message.

9. The system according toclaim 1, further comprising:

an interactive voice recognition system to communicate the physical address to the user, prompt the user to confirm the physical address, and receive a response regarding the user's confirmation.

10. The system according toclaim 1, wherein the address determination module is unable to determine a physical address and then requests a zip code associated with the physical address based on the indication that the physical address could not be determined, determines a city and state associated with the zip code, requests a street address to be associated with the city and state, and compiles the street address, city and state, and the zip code into the physical address.

11. The system according toclaim 10, wherein to request the zip code and the street address, the address determination module transmits one or more messages to a device associated with the identification number.

12. The system according toclaim 11, wherein the message comprises a text message.

13. The system according toclaim 10, wherein the address determination module interacts with an interactive voice recognition system to request the zip code and street address.

14. The system according toclaim 1, further comprising:

a request module to receive a request from a device associated with the identification number, the request including a unique identifier corresponding to a consumer product.

15. The system according toclaim 14, the user account module to determine that the user is not associated with a user account based on the identification number.

16. The system according toclaim 1, a payment module to receive payment information associated with the user.

17. The system according toclaim 16, wherein the payment information comprises information associated with a credit card account, a debit card account, a prepaid card, a demand deposit account, an internet-based payment plan or a savings account.

18. The system according toclaim 16, wherein to receive payment information the payment module receives a text message.

19. The system according toclaim 16, wherein to receive payment information, the payment module interacts with an interactive voice recognition system to receive payment information as input into the interactive voice recognition system.

20. A method, comprising:

receiving a transmission, the transmission being associated with an identification number and including a number associated with a land line;

determining a physical address based on the number associated with the land line;

confirming the physical address that was determined; and

associating the physical address with a user account, the user account being identified by the identification number.

21. The method according toclaim 20, further comprising:

transmitting a request to the user to initiate the transmission including the number associated with the land line.

22. The method according toclaim 21, wherein the transmission is sent to a device associated with the identification number.

23. The method according toclaim 22, wherein the transmission comprises a text message.

24. The method according toclaim 22, wherein the transmission requests that the user input the number associated with a land line into an interactive voice recognition system.

25. The method according toclaim 20, wherein the determining comprises:

querying a land line public database; and

receiving a response from the land line public database, the response including the physical address.

26. The method according toclaim 20, wherein the confirming comprises transmitting a message including the physical address to a device associated with the identification number.

27. The method according toclaim 26, wherein the message comprises a text message.

28. The method according toclaim 20, wherein the confirming comprises:

communicating the physical address to the user via an interactive voice recognition system;

requesting that the user confirm the physical address; and

receiving a response regarding the user's confirmation via the interactive voice recognition system.

29. The method according toclaim 20, further comprising:

receiving an indication that the physical address could not be determined;

requesting a zip code associated with the physical address based on the indication that the physical address could not be determined;

determining a city and state associated with the zip code;

requesting a street address to be associated with the city and state; and

compiling the street address, city and state, and the zip code into the physical address.

30. The method according toclaim 29, wherein the requesting the zip code and the requesting the street address comprises transmitting a message to a device associated with the identification number.

31. The method according toclaim 30, wherein the message comprises a text message.

32. The method according toclaim 29, wherein the requesting the zip code and the requesting the street address comprises requesting the user to input the zip code and street address, respectively, into an interactive voice recognition system.

33. The method according toclaim 20, further comprising:

receiving a request from a device associated with the identification number, the request including a unique identifier corresponding to a consumer product.

34. The method according toclaim 33, further comprising:

determining that the user is not associated with a user account based on the identification number.

35. The method according toclaim 20, further comprising:

receiving payment information associated with the user.

36. The method according toclaim 35, wherein the payment information comprises information associated with a credit card account, a debit card account, a prepaid card, a demand deposit account, an internet-based payment plan or a savings account.

37. The method according toclaim 35, wherein the receiving payment information comprises receiving a text message.

38. The method according toclaim 35, wherein the receiving payment information comprises receiving payment information as input into an interactive voice recognition system.

39. A computer-accessible medium encoded with computer program code effective to perform the following:

receive a transmission, the transmission being associated with an identification number and including a number associated with a land line;

determine a physical address based on the number associated with the land line;

confirm the physical address that was determined; and

associate the physical address with a user account, the user account being identified by the identification number.

Images