WO2007002489A2

WO2007002489A2 - Capturing contact history billing information

Info

Publication number: WO2007002489A2
Application number: PCT/US2006/024625
Authority: WO
Inventors: Ian Siegel; Mark C. Eastwood; Eric Hammond
Original assignee: Ebay Inc.
Priority date: 2005-06-22
Filing date: 2006-06-22
Publication date: 2007-01-04
Also published as: US20070003038A1; US8908846B2; WO2007002489A3

Abstract

Apparatuses and methods to mask identification information to create billing mechanisms in an online listing system are disclosed. In one embodiment, a computer-implemented method of operating an online listing system includes determining an identity of a user based on an identifier entered by the user that uniquely identifies the user; and capturing call history information when routing a proxy telephone number from the user (e.g., a renter, a buyer, a prospective buyer, a mortgagor, etc.) to a lister (e.g., a landlord, a seller, a rental manager, a mortgagee, etc.). The identifier may be the proxy telephone number and/or a code entered after dialing the proxy telephone number. The proxy telephone number may be converted to an actual telephone number prior to routing the proxy telephone number to the lister.

Description

CAPTURING CONTACT HISTORY INFORMATION

RELATED APPLICATIONS

This application claims the priority benefit of U.S. Application Serial No.

11/158,916 filed June 22, 2005, which application is incorporated herein by reference.

FIELD OF TECHNOLOGY

This disclosure relates generally to the technical fields of software programming, networking, social and/or computer networks, and in one example embodiment, to an apparatus and a method to mask identification information to create billing mechanisms in an online listing system.

BACKGROUND

The emergence of an online listing system (e.g., such as eBAY®, Amazon®, and Rent.com® in which goods/services are offered to interested parties) has created new opportunities for a service provider to monetize transactions made between a user (e.g., a renter, a buyer, a prospective buyer, a mortgagor, etc.) and a lister (e.g., a landlord, a seller, a rental manager, a mortgagee, etc.) connected through the online listing system. It is important for the service provider to first identify when a transaction has been made between the user and the lister. Numerous techniques exist for the service provider (e.g., an operator of the online listing system) to discover the transaction between the user and the lister when the user and the lister communicate via the Internet (e.g., through email, instant messenger, etc.). For example, the service provider can discover the transaction by monitoring and/or reading emails between the user and the lister when they communicate with each other through emails sent to each other through the online listing system. Once the transaction is discovered, the service provider can charge the user and/or the lister with a transaction fee (e.g., such as a fee when a particular property has been rented through a website such as Rent.com®).

In many scenarios, the user and the lister transact over the telephone (e.g., through telephone calls between the user to/from the lister). In these scenarios, the service provider must rely on manual methods to discover the transaction, as numerous technical challenges exist in the circuit switched telephone network to verify when and from whom a call has been made (e.g., the user and/or the lister may have caller ID blocking, the user may use multiple phones to call the lister, reconciling and integrating to an online database from data collected through a circuit switched network is inefficient/delayed, etc.). In one approach, the service provider may manually discover the transaction by calling the user and/or the seller and soliciting information about the nature of their relationship and/or whether they entered into the transaction (e.g., by offering monetary and/or non-monetary incentives to the user/lister to report transactions). The service provider may have to hire expensive and trained staff to call the user and/or the lister and manually and ask them about whether a successful transaction was made (e.g., did the sale go through, how long was the response time, etc.). In addition, sometimes the user and/or the lister may resist paying the transaction fee without accurate justification from the service provider that the transaction was made possible through the online listing system (e.g., the user and/or the lister may want proof that they were first introduced to each other through the online listing system). The trained staff of the service provider may not be able to contact the user and/or the lister (e.g., via telephone/email) because their phone numbers and/or email addresses may have changed and/or the parties may be uncooperative (e.g., agreements between the user and the lister to sidestep a rebate payment to the service provider). As such, these manual methods are labor- intensive, expensive, difficult to justify, inaccurate, and incomplete.

SUMMARY Apparatuses and methods to capture communication information are disclosed. In one aspect, a computer-implemented method of operating an online listing system includes determining an identity of a user based on an identifier entered by the user that uniquely identifies the user; and capturing call history information when routing a proxy telephone number from the user (e.g., a renter, a buyer, a prospective buyer, a mortgagor, etc.) to a lister (e.g., a landlord, a seller, a rental manager, a mortgagee, etc.).

The identifier may be the proxy telephone number and/or a code entered after dialing the proxy telephone number. The proxy telephone number may be converted to an actual telephone number prior to routing the proxy telephone number to the lister. The call history information may include at least one of the identity of the user, a duration of a routed call, a time-and-day of the routed call, and a particular listing requested by the user. The computer-implemented method may include transmitting additional information to the user about the particular listing based on the duration of the routed call. The proxy telephone number may be unique to a particular listing requested by the user, and the code may be unique to the user.

The particular listing may be associated with an item detail page in the online listing system, and the user may contact the lister through the proxy telephone number, a proxy fax number, and/or a website lead form on the item detail page. The method may include validating a transaction between the user and the lister based on the call history information, the proxy fax number, and/or the website lead form. In addition, a charge may be justified to the user and the lister based on the call history information, the proxy fax number, and/or the website lead form.

Similarly, a call may be routed from the proxy fax number to an actual fax number through the online listing system. An actual email address of the user entered in the website lead form may be converted to a proxy email address; and may be transmitted to the lister. In addition, a call of the user may be received from multiple geographic sites prior to determining the identity of the user based on the identifier entered by the user that uniquely identifies the user. The identifier may be generated based on a logic algorithm having a checksum; and a bill may be generated to the lister for each different user routed call to the lister based on the identifier.

In another aspect, a computer-implemented method includes generating a telephone number to uniquely identify a listing of an online listing system; generating a telephone extension to uniquely identify a user of the online listing system; and associating the telephone extension with the telephone number based on a registration of the user on the online listing system. A periodic log of telephone numbers dialed between users (e.g., the user 100 and other users) of the online listing system and a lister may be optionally provided. In a further aspect, a computer-implemented method includes identifying a lister response to a user based on an identifier entered by a lister that uniquely identifies the user; and capturing response history information when routing a proxy telephone number from the lister to the user. The identifier may be the proxy telephone number. The identifier may also be a code entered after dialing the proxy telephone number. The proxy telephone number may be unique to a particular listing requested by the user, and the code may be unique to the user.

In yet a further aspect, an apparatus includes a transaction center server to identify a lister response to a user based on a code entered by the lister after dialing a proxy telephone number; and a billing module to capture a response history information when routing the proxy telephone number to the user. The code may be an extension entered after dialing the masked user telephone number. A timing module may determine how long the lister of the online listing system took to respond to the user. In addition, a mask module may determine an identity of the user dialing a proxy telephone number based on an extension number entered by the user, and wherein the transaction center server to capture call history information when routing the proxy telephone number to the lister. A mask removal module may convert the proxy telephone number to an actual telephone number prior to routing the proxy telephone number to the lister.

Other features of the present embodiments will be apparent from the accompanying drawings and from the detailed description that follows. BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which: Figure 1 is a block diagram illustrating an online listing system associated with a mask table and is connected to a user and a lister through a network according to an example embodiment.

Figure 2 is a flow chart illustrating of a user requesting additional details about a listing from a lister, according to an example embodiment. Figure 3 is a process view of the lister of Figure 1 responding to the user through masked contact data, according to an example embodiment.

Figure 4 is a table view of the mask table of Figure 1, according to an example embodiment.

Figure 5 is a process view of determining an identity of a user and capturing call history information when routing a proxy telephone number from the user to a lister, according to an example embodiment.

Figure 6 is a process view of generating a telephone number to uniquely identify a listing of an online listing system, and generating a telephone extension to uniquely identify a user of the online listing system, according to an example embodiment.

Figure 7 is a process view of identifying a lister response and capturing response history information when routing a proxy telephone number from a lister to a user, according to an example embodiment

DETAILED DESCRIPTION

Apparatuses and methods to capture communication information are disclosed. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the various embodiments. It will be evident, however, to one skilled in the art that the various embodiments may be practiced without these specific details. An example embodiment provides methods and systems to mask identification information to create billing mechanisms in an online listing system (e.g., such as eBAY®, Amazon®, and Rent.com® in which goods/services are offered to interested parties). A method and a system are described below, as example embodiments, to determine, to capture, to process, to identify, to generate, to associate, and to bill various parties involved in the online listing system. It will be appreciated that the various embodiments discussed herein may/may not be the same embodiment, and may be grouped into various other embodiments not explicitly disclosed herein.

Figure 1 is a system view of an online listing system 109 associated with a mask table 114 and connected to a user 100 and a lister 104 through a network (e.g., an Internet 102) according to an embodiment. The user 100 communicates with the lister 104 through the Internet 102 (e.g., by accessing and searching on an online listing system such as Rent.com®), in an example use scenario. In addition, the user 100 may directly communicate with the lister 104 offline through a telephone conversation (e.g., through a mask removal module 106). The mask removal module 106 may reside anywhere in the telephone network (e.g., a circuit switched and/or IP network), and serve as a gateway for offline communications between the user 100 and the lister 104. For example, the mask removal module 106 may reverse the encoding of a phone number that is 'masked' or encoded by a mask module 110 of the online listing system 109 (e.g., as later will be described in detail in Figure 5).

A transaction center server 112 (e.g., a transaction center server associated with the online listing system 109) may communicate with a billing module 108 and a mask module 110 connected to the transaction center server 112. The transaction center server 112 may also be connected to a display device 118, an input device 122, and a mouse 120, according to an embodiment illustrated in Figure 1. The transaction center server 112 (e.g., a computer system) includes a network interface 124, a disk controller 126, a disk drive 136, a display controller 128, an I/O controller 130, a processor 132 (e.g., a microprocessor), and a storage 134 (e.g., a hard drive, a dynamic random access memory, and/or a flash memory, etc.) connected to each other through a bus 138 according to an embodiment illustrated in Figure 1. The I/O controller 130 connects the transaction center server 112 to the input device 122 and the mouse 120 according to the embodiment of Figure 1.

The mask module 110 of the online listing system 109 may generate unique telephone extensions to identify different users (e.g., such as the user 100) of the online listing system using an extension generator module 140. A particular extension generated by the extension generator module 140 may be visible in each listing visited by the user 100 in the online listing system (e.g., each property visited by the user 100 in an online listing system for property rentals). Similarly, the mask module 110 may determine a proxy telephone number (e.g., a substitute phone number to mask an actual telephone number) for each listing posted in the online listing system 109 (e.g., every property posted by a rental manager on the online listing system).

When the user 100 calls in connection with a particular listing, the mask module 110 may determine an identity of the user 100 dialing the proxy telephone number (e.g., by consulting a mask table 114) based on an extension number entered by the user 100 (e.g., an extension number previously generated by an extension generator module 140 connected to the mask module 110). Based on this identity determination, the mask module 110 may update data in the storage 134 associated with the billing module 108 (e.g., to track a particular call and later bill the lister 104 and/or the user 100).

The mask module 110 may consult a mask table 114 of the mask database 116 (e.g., the mask database 116 may be stored in the storage 134 and/or external to the transaction center server 112 in various embodiments). In addition, the mask module 110 may communicate with the mask removal module 106 and permit the mask removal module 106 to convert the proxy telephone number to an actual telephone number of the lister 104 and route a call from the user 100 to the lister 104. The mask removal module 106 may then route the proxy telephone number to the lister 104 from the user 100 after the conversion is made according to an embodiment. A detailed view of the mask table 114 is illustrated in Figure 4. The mask table 114 as illustrated in Figure 4 includes a user side data 400 (e.g., the user illustrated having a unique extension 1511) and a lister side data 402 (e.g., the lister illustrated as having a unique phone number 800-555-2100). The user side data 400 includes actual user data 404 (e.g., actual phone numbers, fax, email, and other information about a user such as the user 100 as shown in Figure 1), and masked user data 406 (e.g., masked/proxy phone numbers, fax, email, and other information about a user such as the user 100 as shown in Figure 1). The masked user data 406 may be generated by the mask module 110 according to one embodiment.

Similarly, in Figure 4, the lister side data 402 includes an actual lister data 408 (e.g., actual phone numbers, fax, email, and other information about a lister such as the lister 104), and a masked lister data 410 (e.g., masked/proxy phone numbers, fax, email, and other information about a lister such as the lister 104 as shown in Figure 1). The masked lister data 410 may also be generated by the mask module 110 according to one embodiment. Referring now to Figure 1, the mask table 114 may be used by the mask module 110 to convert actual contact information associated with the user 100 to masked information and/or vise versa. In addition, mask table 114 may be used by the mask removal module 106 to convert a proxy telephone number associated with the lister 104 to an actual telephone number of the lister 104 and/or vise versa.

For example, the mask removal module 106 (e.g., may be in a circuit switched telephone network and/or in an IP network such as the Internet 102) may reference the mask table 114 of Figure 4 to convert the proxy telephone number (e.g., as previously generated by the mask module 110) of the lister 104 to an actual telephone number of the lister 104 based on a phone number entered. In addition, the mask removal module 106 may reference the mask table 114 to identify a particular user based on a code (e.g., an extension) entered by the lister 104 wishing to contact the user 100 via telephone according to an embodiment.

Referring back to Figure 1, the online listing system 109 may identify a lister response (e.g., a rental manager following up on a lead received through the online listing system) to the user 100 (e.g., a user of the online listing system such as a potential renter of an apartment) based on a code (e.g., the code may be an extension entered after dialing a masked user telephone number such as a proxy telephone number) entered by the lister 104 after dialing a proxy telephone number (e.g., a 'masked' telephone number generated by the mask module 110 and substituting for the actual telephone number of the user 100), according to an embodiment. In addition, the billing module 108 of Figure 1 may capture response history information when routing the proxy telephone number to the user 100.

In one embodiment, a timer module 113 (e.g., code executed by the processor 132 of the transaction center server 112) may determine how long the lister 104 of the online listing system took to respond to an inquiry from the user 100. The online listing system 109 may also record one or more telephone calls between the user 100 and the lister 104 based on a contract (e.g., a binding agreement) between the user 100 and the lister 104 with a proprietor of the online listing system (e.g., an online listing system 109). The lister may be rental manager, a landlord, a mortgage broker, and a merchant, according to various embodiments. In addition, the transaction center server 112 may provide to the billing module 108 a periodic log of telephone numbers dialed between users of the online listing system such as the user 100 and, other users of the online listing system 109 and the lister 104.

In one embodiment, a proxy telephone number generated by the mask module 110 is unique to a particular listing (e.g., a particular item or service offered for sale and/or lease) requested by the user 100, and the extension number (e.g., a telephone extension number) is unique to the user 100. The transaction center server 112 may send to the user 100 additional information about the particular listing based on the duration (e.g., amount of time) of the routed call. Every listing in the online listing system 109 may be associated with an item detail page (e.g., detailed information about a property for lease and/or sale) in the online listing system 109. The user 100 may contact the lister 104 through the proxy telephone number, a proxy fax number visible on the online listing system 109, and/or a website lead form on the item detail page.

The billing module 108 may validate a transaction (e.g., a successful lease and/or sale) between the user 100 and the lister 104 based on the call history information, the proxy fax number, and/or the website lead form. The billing module 108 may validate the transaction by automatically scanning (e.g., through an optical character recognition method) the call history information, the proxy fax number, and/or the website lead form to determine whether a binding contract was formed between the parties (e.g., offer, acceptance, consideration), hi one embodiment, the billing module 108 may determine that there is more likely than not a binding contract formed between the parties, and on that basis an automatic signal is transmitted from the billing module 108 to an administrator of the online listing system 109 to follow up with the parties via telephone.

The billing module 108 may also generate a justification to a bill (e.g., a transaction based charge) to at least one of the user and the lister based on any one or more of the call history information, the proxy fax number, and/or the website lead form. The transaction center server 112 may route the proxy fax number to an actual fax number through the online listing system. In addition, the transaction center server 112 may convert an actual email address of the user 100 entered in the website lead form to a proxy email address, and transmit the proxy email address to the lister 104.

Furthermore, the mask module 110 of the transaction center server 112 may receive a call of the user 100 from multiple geographic sites (e.g., from the user's office and/or home location) prior to determining the identity of the user 100 dialing the proxy telephone number based on the extension number entered by the user 100. In addition, the transaction center server 112 may generate the extension based on a logic algorithm having a checksum; and bill the lister (e.g., through the billing module 108) for each different user 100 routed call to the lister 104 based on the extension. It will be appreciated that the mask module 110 differs from the mask removal module 106 in that the mask module 110 is used to create proxy data (e.g., a proxy telephone number, a proxy email, a proxy fax number, etc. of the user 100 and/or the lister 104) from actual data while the mask removal module 106 is used to reconstruct the actual data (e.g., an actual telephone number, an actual email address, an actual fax number, etc. of the user 100 and/or the lister 104) from the proxy data. In alternative embodiments, the mask module 110 and the mask removal module 106 may be incorporated into a single module.

Figure 2 is a process view of a user requesting additional details about a listing from the lister 104 of Figure 1, according to an embodiment. In Figure 2, in operation 202, the user 100 registers and performs a search on the online listing system 109 of Figure 1, according to an embodiment. Next, in operation 204, the user 100 may view search results (e.g., results matching a criteria requested by the user 100) and selects a listing (e.g., a target product/service offered by the lister 104 of Figure lin the online listing system 109 of Figure lthat the user 100 wants to find out more about).

Then, in operation 206, an extension is generated (e.g., by the mask module 110 of Figure 1) that uniquely identifies the user 100. In operation 208, a proxy phone number (e.g., by the mask module 110 of Figure 1) is generated that uniquely identifies the listing (e.g., a good and/or a service posted for sale/rent/lease, etc. in the online listing system 109 of Figure 1). In alternative embodiments, the operation 206 and the operation 208 are performed immediately after the user 100 registers and performs a search in operation 202, and the unique extension and the unique proxy telephone identifying a particular listing is visible on each and every listing visited by the user 100 in the online listing system 109 of Figure 1.

Next, in operation 210, the user 100 requests additional information about the listing (e.g., by completing a website lead form at 212 and/or by calling the proxy phone number and the extension at 214). If the user calls the proxy phone number and the extension at 214, then the proxy phone number is routed to a listing phone number (e.g., an actual phone number of the lister 104 using the mask removal module 106 of Figure 1) and the extension is analyzed in operation 216. Then the data is sent to the billing module 108 of Figure 1 in operation 218 (e.g., for charging the user 100 and/or the lister 104 of Figure 1 depending on the revenue model of the online listing system 109 of Figure 1). Figure 3 is a process view of the lister 104 of Figure 1 responding to the user 100 through masked contact data (e.g., a proxy telephone number), according to an embodiment. In operation 300, a contact information of the user 100 is converted to a masked content data (e.g., before transmitting an email to the lister 104 of Figure 1 with contact information details of the user 100, the mask module 110 of Figure 1 may convert actual contact phone numbers, emails, fax machines etc. of the user 100 to masked/proxy contact phone numbers, emails, fax machines etc. using the mask table 114 of Figure 1 in the mask database 116 of Figure 1).

Then, in operation 302, the lister 104 of Figure 1 contacts the user 100 through the masked contact data (e.g., the masked contact data be may be an identifier, a code, a proxy telephone number, and/or an extension entered after dialing the proxy telephone number, etc.) In operation 304, the lister 104 of Figure 1 is routed back to the contact information of the user 100 (e.g., the actual contact information such as the actual phone number of the user 100) based on the masked content data. Then, the billing module 108 of Figure 1 is notified of response history information (e.g., how long the lister 104 of Figure 1 took to contact the user 100 so that the online listing system 109 of Figure 1 can determine lead success rates, etc.) in operation 306.

Figure 5 is a process view of determining an identity of the user 100 of Figure 1 and capturing call history information when routing a proxy telephone number from the user 100 to the lister 104 (e.g., see Figure 1), according to an embodiment. In operation 502, an identifier (e.g., the identifier may be a proxy telephone lnumber or a code entered after dialing the proxy telephone number, and may be a user identifier and/or a communication identifier) may be generated based on a logic algorithm (e.g., an intelligent algorithm that considers a geographic location of the user 100 and/or the lister 104, an income of the user 100, a budget of the user 100, etc.) the having a checksum. In operation 504, a call is received from the user 100 from multiple geographic sites. In operation 506, an identity of the user 100 may be determined based on the identifier (e.g., an extension to a proxy telephone number) entered by the user 100 that uniquely identifies the user 100. In operation 508, call history information may be captured when routing a proxy telephone number from the user 100 to the lister 104. In one embodiment, the proxy telephone number is unique to a particular listing requested by the user 100, and the code (e.g., a telephone extension) is unique to the user 100. The proxy telephone number is converted (e.g., using the mask removal module 106) to an actual telephone number prior to routing the proxy telephone number to the lister 104. In operation 510, the lister 104 may be billed using the billing module 108 of

Figure 1 (e.g., in other embodiments the lister 104 may not be billed, and in some embodiments the lister 104 and/or the user 100 may be billed). In one embodiment, additional information may be transmitted to the user 100 about the particular listing based on the duration of the routed call. The particular listing may be associated with an item detail page in the online listing system 109, and the user 100 may contact the lister 104 through the proxy telephone number, a proxy fax number, and/or a website lead form on the item detail page (e.g., a web page having details about a listing).

In operation 512, a transaction between the user 100 and the lister 104 may be validated based on at least one of a call history information (e.g., the call history information may include at least one of the identity of the user 100, a duration of a routed call, a time-and-day of the routed call, and a particular listing requested by the user 100), the proxy fax number and/or the website lead form, etc. In operation 514, a charge may be justified to the user 100 and/or the lister 104 based on the call history information, the proxy fax number, and/or the website lead form, etc.

In one embodiment the proxy fax number may be routed to an actual fax number through the online listing system 109 when the user 100 sends a fax to the lister 104 and/or vice versa (e.g., by the mask removal module 106 of Figure 1). In addition, an actual email address of the user 100 entered in the website lead form may be converted to a proxy email address (e.g., by the mask module 110 of Figure 1); and transmitted to the lister 104 of Figure 1.

Figure 6 is a process view of generating a telephone number (e.g., a proxy telephone number) to uniquely identify a listing of an online listing system 109, and generating a telephone extension to uniquely identify a user 100 of the online listing system, according to an embodiment. In operation 602, a telephone number (e.g., a proxy telephone number) may be generated to uniquely identify a listing of the online listing system 109. In operation 604, a telephone extension may be generated to uniquely identify the user 100 of the online listing system 109. In operation 606, the telephone extension may be associated with the telephone number based on a registration of the user on the online listing system (e.g., as described in operation 202 of Figure 2). In operation 608, a periodic log may be provided of telephone numbers dialed between users (e.g., the user 100 and other users) of the online listing system 109 of Figure 1 and the lister 104 of Figure 1. In operation 610, a call may be routed from the user 100 to the lister 104 when the user 100 dials the telephone number. In operation 612, call history information (e.g., length and duration of the call, time of call, etc.) may be captured when routing the call from the user 100 to the lister 104 when the user 100 dials the telephone number.

Figure 7 is a process view of identifying a lister response and capturing response history information when routing a proxy telephone number from the lister 104 to the user 100 (e.g., dialed by the lister 104 to the user 100), according to an embodiment. In operation 702, a lister response (e.g., the lister response may be a landlord following up to a lead from a prospective tenant, a mortgage broker following up to a prospective mortgagor etc.) to the user 100 (e.g., as described in the process view of Figure 5) may be identified based on an identifier (e.g., a code, a proxy telephone number, and/or the code entered after the proxy telephone number) entered by the lister 104 that uniquely identifies the user 100 (e.g., in alternate embodiments may uniquely identify the user, lister, and/or a combination of the user and/or lister). In one embodiment, the proxy telephone number is unique to a particular listing requested by the user, and the code is unique to the user. In operation 704, a response history (e.g., duration of the call, which salesperson called back the user 100, when the salesperson called back in light of the original call from the user 100, etc.) may be captured when routing a proxy telephone number (e.g., a mask of the actual phone number) from the lister 104 of Figure 1 to the user 100 of Figure 1. Additionally, in one embodiment, the identifier may uniquely identify the user 100 and a particular call made by the user 100 to the lister 104. Referring now to Figure 1, in one embodiment, a periodic log of telephone numbers dialed between the user 100 and other users of the online listing system 109 and the lister 104 is provided to the billing module 108 of Figure 1. The billing module 108 may calculate how long the lister of the online listing system 109 took to respond to the user (e.g., for sales tracking, response rate, incentive tracking, etc). The billing module 108 may also charge either the user 100 and/or the lister 104 and/or a third party (e.g., a referral service) based on a verified and justified transaction in one embodiment (e.g., verified based on the call logs, email responses, etc. between the parties). In addition, a call may be routed (e.g., through a circuit switched network and/or IP network associated with the mask removal module 106 of Figure 1) when the user 100 and/or the lister 104 communicate with each other through a proxy telephone number. One or more telephone calls between the user and the lister may be recorded based on a contract (e.g., a binding and/or non-binding online/offline contract) between the user 100 and the lister 104 with a proprietor of the online listing system 109.

It should be noted that the embodiments disclosed herein may be embodied in a machine-readable-medium. The term "machine-readable medium" should be taken to include a single medium and/or multiple media (e.g., a centralized and/or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term "machine-readable medium" shall also be taken to include any medium that is capable of storing, encoding and/or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the various embodiments. The term "machine- readable medium" shall accordingly be taken to include, but not be limited to, solid- state memories, optical and magnetic media, and carrier wave signals.

Although the present embodiments have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the embodiments. It will be appreciated that the various operations and processes disclosed herein may be performed in any order, and are not to be limited to a particular order of events unless explicitly specified that the order is important. In addition, the various modules, analyzers, generators, etc. described herein may be preformed and created using hardware circuitry (e.g., CMOS based logic circuitry) as well as in software. For example, the online listing system 109, the mask module 110, the extension generator module 140, the billing module 108, and/or the mask removal module 106, etc of Figure 1 may be embodied using transistors, logic gates, and electrical circuits (e.g., application specific integrated ASIC circuitry) using a transaction center circuit, a mask circuit, an extension generator circuit, a billing circuit, and/or a mask removal circuit, etc. In addition, it will be appreciated that the various operations, processes, and methods disclosed herein may be embodied in a machine-readable medium and/or a machine accessible medium compatible with a data processing system (e.g., a computer system). Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.

Claims

CLAIMSWhat is claimed is:

1. A system including: a transaction center server to identify a lister response to a user based on a code entered by the lister dialing a proxy telephone number; and a billing module to capture response history information when routing the proxy telephone number to the user.

2. The system of claim 1, wherein the code is an extension number entered after dialing the proxy telephone number.

3. The system of claim 1, including a mask module to determine an identity of the user dialing a listing proxy telephone number based on a user extension number entered by the user, and the transaction center server being to capture request history information when routing the a listing proxy telephone number to the lister.

4. The system of claim 3, wherein the listing proxy telephone number is unique to a listing, and the user extension number is unique to the user.

5. The system of claim 4, wherein the billing module is to generate a justification to a bill to at least one of the user and the lister based on any one or more of a group including the request history information, a proxy fax number, and a website lead form.

6. A computer-implemented method including: identifying a lister response to a user based on an identifier entered by a lister that uniquely identifies the user; and capturing response history information when routing a proxy telephone number from the lister to the user.

7. The method of claim 6, wherein the identifier is an extension entered after dialing the proxy telephone number.

8. The method of claim 6, including determining an identity of the user dialing a listing proxy telephone number based on a user extension number entered by the user, and capturing request history information when routing the listing proxy telephone number to the lister.

9. The method of claim 8, wherein the listing proxy telephone number is unique to a listing, and the user extension number is unique to the user.

10. The method of claim 9, including generating a justification to a bill to at least one of the user and the lister based on any one or more of a group including the request history information, a proxy fax number, and a website lead form.

11. A machine-readable medium embodying instructions that, when executed by a machine, cause the machine to perform the method of claim 6.