An Application Data Sheet is filed concurrently with this specification as part of the present application. Each application that the present application claims benefit of or priority to as identified in the concurrently filed Application Data Sheet is incorporated by reference herein in its entirety and for all purposes.
Social networks, such as Twitter®, Facebook®, and Yammer® have grown in popularity not only for casual social purposes, but also for work-related purposes. Users of social networks post messages related to a company's products and/or services containing information that could be useful to understand customers, track market developments, manage public relations, and address issues related to the company's products and/or services, employees, or the company itself.
The implementations disclosed herein relate generally to database systems and more particularly to integration of information from social networks into multi-tenant database systems (“MTS”). Embodiments of the implementations are particularly useful for integrating information from social networks such as twitter.com, yammer.com, and other similar services. The implementations described herein provide methods and systems for integrating information harvested from social networks (e.g., posted messages) into a MTS. Various embodiments provide methods and systems for enabling customer support representatives to manage social networks like any other support channel. Various embodiments provide methods and systems for enabling multiple agents to pull, filter, process, search through, and take action based on such harvested information. Various embodiments provide methods and systems for using templates for such harvested information and storing harvested information in a knowledge base to increase productivity.
Some embodiments comprise integrating information from a social network into a multi-tenant database system. A plurality of information from the social network is retrieved, using a processor and a network interface of a server computer in the multi-tenant database system, wherein the plurality of information is associated with a message transmitted using the social network. Metadata related to the transmitted message is generated, using the processor. A conversation object is generated, using the processor, based on the plurality of information associated with the transmitted message and the metadata related to the transmitted message. The conversation object is then stored in an entity in the multi-tenant database system, using the processor of the server computer.
Some embodiments comprise a non-transitory computer-readable medium tangibly encoded with instructions for performing the above-described operations and variations thereof.
Some embodiments comprise a system comprising a processor, a network interface, and a non-transitory computer-readable medium tangibly encoded with instructions for performing the above-described operations and variations thereof.
Reference to the remaining portions of the specification, including the drawings and claims, will realize other features and advantages of the implementations. Further features and advantages of the implementations, as well as the structure and operation of various embodiments, are described in detail below with respect to the accompanying drawings. In the drawings, like reference numbers indicate identical or functionally similar elements.
The implementations described herein provide methods and systems for integrating information harvested from social networks (e.g., posted messages) into a MTS. Customer support representatives are able to manage social networks like any other support channel. Multiple agents can pull, filter, process, search through, and take action based on such harvested information. Templates can be used to characterize harvested information and store it into standard object types. Harvested information can be stored in a knowledge base to increase productivity.
Each database can generally be viewed as a collection of objects, such as a set of logical tables, containing data fitted into predefined categories. A table, one representation of a data object, is used herein to simplify the conceptual description of objects and custom objects in the present disclosure. It should be understood that the terms table, object and entity may be used interchangeably herein. Each table generally contains one or more data categories logically arranged as columns or fields in a viewable schema. Each row or record of a table contains an instance of data for each category defined by the fields. For example, a CRM database may include a table that describes a customer with fields for basic contact information such as name, address, phone number, fax number, etc. Another table might describe a purchase order, including fields for information such as customer, product, sale price, date, etc.
As used herein, the term multi-tenant database system (“MTS”) refers to those systems in which various elements of hardware and software of the database system may be shared between one or more customers. For example, a given application server may simultaneously process requests for a great number of customers, and a given database table may store rows for a potentially much greater number of customers. In some MTS embodiments, standard entity tables might be provided. For CRM database applications, such standard entities might include tables for relevant data, such as Account, Contact, Lead and Opportunity, each containing predefined fields.
As used herein, the term social network or social networking site refers to any multiuser online system that enables its users to create and preserve connections, communicate by posting broadcast or private messages, and share information with other users of the online system. Examples of social networks include twitter, Facebook, and Yammer.
As used herein, the term message includes any message posted on a social network, including but not limited to status updates, private messages sent to one or more users of the social network, or public messages for broadcast to everyone or to a subgroup of users.
Multi-Tenant Database System (MTS) Overview
User systems 12 might communicate with MTS 16 using TCP/IP and, at a higher network level, use other common Internet protocols to communicate, such as Hypertext Transfer Protocol (“HTTP”), file transfer protocol (“FTP”), Andrew File System (“AFS”), wireless application protocol (“WAP”), etc. As an example, where HTTP is used, user system 12 might include a HTTP client commonly referred to as a “browser” for sending and receiving HTTP messages from a HTTP server at MTS 16. Such a HTTP server might be implemented as the sole network interface between MTS 16 and network 14, but other techniques might be used as well or instead. In some embodiments, the interface between MTS 16 and network 14 includes load-balancing functionality, such as round-robin HTTP request distributors to balance loads and distribute incoming HTTP requests evenly over a plurality of HTTP servers. Preferably, each of the plurality of HTTP servers has access to the MTS's data, at least as for the users that are accessing that server.
In aspects, the system shown in
One arrangement for elements of MTS 16 is shown in
Some elements in the system shown in
According to one embodiment, each user system 12 and all of its components are operator configurable using applications, such as a browser, including program code run using a central processing unit such as an Intel Pentium® processor or the like. Similarly, MTS 16 (and additional instances of MTS's, where more than one is present) and all of their components might be operator configurable using application(s) including program code run using a central processing unit such as an Intel Pentium processor or the like, or multiple processor units. Program code for operating and configuring MTS 16 to intercommunicate and to process web pages and other data and media content as described herein is preferably downloaded and stored on a hard disk, but the entire program code, or portions thereof, may also be stored in any other volatile or non-volatile memory medium or device as is well known, such as a ROM or RAM, or provided on any media capable of storing program code, such as a compact disk (“CD”) medium, digital versatile disk (“DVD”) medium, a floppy disk, and the like. Additionally, the entire program code, or portions thereof, may be transmitted and downloaded from a software source, e.g., over the Internet, or from another server, as is well known, or transmitted over any other conventional network connection as is well known (e.g., extranet, VPN, LAN, etc.) using any communication medium and protocols (e.g., TCP/IP, HTTP, HTTPS, WAP, Ethernet, etc.) as are well known. It will also be appreciated that program code for implementing aspects of the system can be implemented in any programming language that can be executed on a server or server system such as, for example, in C, C++, HTML, Java, JavaScript, WML, any other scripting language, such as VB Script and many other programming languages as are well known.
It should also be understood that each user system 12 may include differing elements, for example, one user system 12 might include a user's personal workstation running Microsoft's Internet Explorer browser while connected to MTS 16 by VPN, another user system 12 might include a thin-client netbook (e.g., Asus Eee PC®) running the Opera browser while connected to MTS 16 through an extranet, and another user system 12 might include a PDA running a WAP-enabled browser while connected to MTS 16 over third-party cellular networks.
According to one embodiment, each MTS 16 is configured to provide web pages, forms, data and media content to user systems 12 to support the access by user systems 12 as tenants of MTS 16. As such, MTS 16 provides security mechanisms to keep each tenant's data separate unless the data is shared. If more than one MTS 16 is used, they may be located in close proximity to one another (e.g., in a server farm located in a single building or campus), or they may be distributed at locations remote from one another (e.g., one or more servers located in city A and one or more servers located in city B). Each MTS 16 may include one or more logically and/or physically connected servers distributed locally or across one or more geographic locations. Additionally, the term “server” is meant to include a computer system, including processing hardware and process space(s), and an associated storage system and database application (e.g., relational database management system (“RDBMS”)), as is well known in the art. It should also be understood that “server system” and “server” are often used interchangeably herein. Similarly, the databases described herein can be implemented as single databases, a distributed database, a collection of distributed databases, a database with redundant online or offline backups or other redundancies, etc., and might include a distributed database or storage network and associated processing intelligence.
It should also be understood that each application server 100 may be communicably coupled to database systems, e.g., system database 106 and tenant database(s) 108, via a different network connection. For example, one application server 1001 might be coupled via the Internet 14, another application server 100N-1 might be coupled via a direct network link, and another application server 100N might be coupled by yet a different network connection. TCP/IP is the currently preferred protocol for communicating between application servers 100 and the database system, however, it will be apparent to one skilled in the art that other transport protocols may be used to optimize the system depending on the network interconnect used.
In aspects, each application server 100 is configured to handle requests for any user/organization. Because it is desirable to be able to add and remove application servers from the server pool at any time for any reason, there is preferably no server affinity for a user and/or organization to a specific application server 100. In one embodiment, therefore, an interface system (not shown) implementing a load-balancing function (e.g., an F5 Big-IP load balancer) is communicably coupled between the application servers 100 and the user systems 30 to distribute requests to the application servers 100. In one aspect, the load balancer uses a least connections algorithm to route user requests to the application servers 100. Other examples of load balancing algorithms, such as round robin and observed response time, also can be used. For example, in certain aspects, three consecutive requests from the same user could hit three different servers, and three requests from different users could hit the same server. In this manner, MTS 16 is multi-tenant, wherein MTS 16 handles storage of different objects and data across disparate users and organizations.
As an example of storage, one tenant might be a company that employs a sales force where each user (e.g., a salesperson) uses MTS 16 to manage their sales process. Thus, a user might maintain contact data, leads data, customer follow-up data, performance data, goals and progress data, etc., all applicable to that user's personal sales process (e.g., in tenant database 108). In one MTS arrangement, since all of this data and the applications to access, view, modify, report, transmit, calculate, etc., can be maintained and accessed by a user system having nothing more than network access, the user can manage his or her sales efforts and cycles from any of many different user systems. For example, if a salesperson is visiting a customer and the customer has Internet access in their lobby, the salesperson can obtain critical updates as to that customer while waiting for the customer to arrive in the lobby.
While each user's sales data might be separate from other users' sales data regardless of the employers of each user, some data might be organization-wide data shared or accessible by a plurality of users or all of the sales force for a given organization that is a tenant. Thus, there might be some data structures managed by MTS 16 that are allocated at the tenant level while other data structures might be managed at the user level. Because an MTS might support multiple tenants including possible competitors, the MTS, in one implementation, has security protocols that keep data, applications, and application use separate. Also, because many tenants will opt for access to an MTS rather than maintain their own system, redundancy, up-time and backup are more critical functions and need to be implemented in the MTS.
In addition to user-specific data and tenant-specific data, MTS 16 might also maintain system-level data usable by multiple tenants or other data. Such system-level data might include industry reports, news, postings, and the like that are sharable among tenants.
In certain aspects, user systems 30 communicate with application servers 100 to request and update system-level and tenant-level data from MTS 16; this may require one or more queries to system database 106 and/or tenant database 108. MTS 16 (e.g., an application server 100 in MTS 16) automatically generates one or more SQL statements (a SQL query) designed to access the desired information.
The organization ID column 201 is provided to distinguish among organizations using the MTS. As shown, N different organizations have data stored in main table 200. In an exemplary embodiment, the organization IDs in column 201 are defined as Char(15), but may be defined as other data types. In one embodiment, the first 3 characters of the organization ID is set to a predefined prefix, such as “ood”, although another subset of characters in the organization ID may be used to hold such a prefix if desired.
In the particular example of
Integration Environment
In an example embodiment, social network 30 is the twitter social network. A member 40 of twitter can broadcast a message (i.e., tweet) to all members of the twitter social network who are following tweets by the member 40. A member 40 of twitter can also send a targeted message to a single, identified member of twitter, or to a group of members.
In an example embodiment, the MTS periodically polls the social network for new transmissions of messages and pulls information related to each newly transmitted message; this information is stored in the MTS in the form of a Conversation object. In an example embodiment wherein social network 30 is twitter, the MTS polls twitter's search API on a regular basis and stores all search results as twitter Conversation objects. Each twitter Conversation object is stored as a record in an entity of the MTS. An exemplary embodiment of a Conversation object for twitter is described in the table below.
Example Embodiment of a Conversation Object for Twitter
Integrating Information from a Social Network into a MTS
If the message is a response to an earlier outbound message related to an existing case (510), then the user may create a Conversation object in the MTS and associate it with the existing case (515). The user can then create a case comment using the message text (520), and the case can be closed if it is appropriate to do so (525).
If the message is not a response to an earlier outbound message related to an existing case (510), then the user may create a new Conversation object (530) in the MTS. The MTS may then search through existing contacts and/or leads to see if the message was sent by an existing contact (535). If so, the MTS may associate the Conversation object with the existing contact (540). In one embodiment, if more than one existing contact and/or lead appears in the search results, then one of the following actions may be taken: (1) no association will be created, or (2) associations are created with all existing contacts and/or leads appearing in the search results, or (3) an association will be created with the most recent contact or lead. If the message was not sent by an existing contact (535), the MTS may create a new Contact or Lead and associate it with the Conversation object (545). In one embodiment, the Contact or Lead object includes a custom field to store the twitter username for the new contact.
If the message is a search tweet (i.e., a publicly broadcast status update), the MTS may retrieve the prior conversation, if any (550). If the message is an @username tweet (i.e., a publicly accessible targeted message) or direct message tweet (i.e., a private message), the user may be able to determine that the content of the message warrants creation of a new case and create a new case (555) and search the knowledge base (560) to see if there is an existing solution or any further information. If there is, then the user may be able to respond to the message to communicate the solution or further information (565)—the MTS may post the response to the twitter API (570).
In one embodiment, the user may be able to view a plurality of messages in a list view, select particular messages, and take actions upon the selected messages in the list (575). The user may be able to escalate a selected message to a case and create a new case (555). The user may be able to use the selected message to create a new knowledge base article (580). The user may be able to use the selected message to create a new lead (585). Or, the user may be able to choose to ignore the selected message and mark it for deletion (590). In one embodiment, the user may be able to change the status of the selected message (e.g., “solved by community”) or change other metadata related to the selected message.
In one embodiment, when a new Conversation object is created based on a transmitted message, metadata related to the transmitted message is generated and stored along with the Conversation object in the MTS. In one embodiment, when a new Conversation object is created, it can be categorized in accordance with any of a number of aspects, including but not limited to the message content, the author of the message, the recipient of the message, the date and/or time of the message, the case or lead or knowledge base article with which the message is associated, etc.
In one embodiment, messages from certain users (e.g., usernames belonging to MTS system administrators) may be filtered out in the search results.
User Interface
In one embodiment, the search for newly transmitted messages may be triggered manually. In one embodiment, the search for newly transmitted messages may be run automatically, possibly on a periodic basis. In one embodiment, the user can enable auto-creation of cases, leads, and/or contact
In one embodiment, outbound messages destined for the social network can be generated from several locations in the user interface—when the user is viewing a case, a Conversation object, a contact, and/or a lead. In one embodiment, the user interface allows creation of an outbound message from within the MTS user interface. In one embodiment, the user interface allows creation of an outbound message directly from the social network's user interface.
In one embodiment, once an action has been taken on a message (e.g., create case, create lead, ignore), the user interface indicates that an action has been taken on the message; in one embodiment, the user interface indicates the exact disposition of the message.
In one embodiment, reports can be generated to determine various statistics, which may include: how many messages were pulled in by the search, how many messages were reviewed, how many messages were promoted to cases or leads or knowledge base articles, how many messages were ignored, and how many messages are left to be dealt with.
Setup and Administration
In one embodiment, a Search object is created in order to define various search terms for use when searching for messages in the social network. In one embodiment, multiple instances of Search objects may be created. Each search instance may have an associated owner (either username or queue). All conversations that are pulled in as a result of the Search object may be assigned to the owner associated with the search object. For example, conversations pulled in using the search terms “comcast issue”+“comcast problem” are assigned to the owner “twitter service.” In another example, conversations pulled in using the search terms “Verizon offer”+“which cable company” are assigned to the owner “twitter sales.”
Example Embodiment of a Search Object for Twitter Integration
In one embodiment, an Account object is created in order to enable system administrators to keep track of necessary user account information, wherein the user account is related to the social network.
Example Embodiment of an Account Object for Twitter Integration
While the invention has been described by way of example and in terms of the specific embodiments, it is to be understood that the invention is not limited to the disclosed embodiments. To the contrary, it is intended to cover various modifications and similar arrangements as would be apparent to those skilled in the art. Therefore, the scope of the appended claims should be accorded the broadest interpretation so as to encompass all such modifications and similar arrangements.
Number | Name | Date | Kind |
---|---|---|---|
5577188 | Zhu | Nov 1996 | A |
5608872 | Schwartz et al. | Mar 1997 | A |
5649104 | Carleton et al. | Jul 1997 | A |
5715450 | Ambrose et al. | Feb 1998 | A |
5761419 | Schwartz et al. | Jun 1998 | A |
5819038 | Carleton et al. | Oct 1998 | A |
5821937 | Tonelli et al. | Oct 1998 | A |
5831610 | Tonelli et al. | Nov 1998 | A |
5873096 | Lim et al. | Feb 1999 | A |
5918159 | Fomukong et al. | Jun 1999 | A |
5963953 | Cram et al. | Oct 1999 | A |
5983227 | Nazem et al. | Nov 1999 | A |
6092083 | Brodersen et al. | Jul 2000 | A |
6161149 | Achacoso et al. | Dec 2000 | A |
6169534 | Raffel et al. | Jan 2001 | B1 |
6178425 | Brodersen et al. | Jan 2001 | B1 |
6189011 | Lim et al. | Feb 2001 | B1 |
6216133 | Masthoff | Apr 2001 | B1 |
6216135 | Brodersen et al. | Apr 2001 | B1 |
6233617 | Rothwein et al. | May 2001 | B1 |
6236978 | Tuzhilin | May 2001 | B1 |
6266669 | Brodersen et al. | Jul 2001 | B1 |
6288717 | Dunkle | Sep 2001 | B1 |
6295530 | Ritchie et al. | Sep 2001 | B1 |
6324568 | Diec | Nov 2001 | B1 |
6324693 | Brodersen et al. | Nov 2001 | B1 |
6336137 | Lee et al. | Jan 2002 | B1 |
D454139 | Feldcamp | Mar 2002 | S |
6367077 | Brodersen et al. | Apr 2002 | B1 |
6393605 | Loomans | May 2002 | B1 |
6405220 | Brodersen et al. | Jun 2002 | B1 |
6411949 | Schaffer | Jun 2002 | B1 |
6434550 | Warner et al. | Aug 2002 | B1 |
6446089 | Brodersen et al. | Sep 2002 | B1 |
6535909 | Rust | Mar 2003 | B1 |
6549908 | Loomans | Apr 2003 | B1 |
6553563 | Ambrose et al. | Apr 2003 | B2 |
6560461 | Fomukong et al. | May 2003 | B1 |
6574635 | Stauber et al. | Jun 2003 | B2 |
6577726 | Huang et al. | Jun 2003 | B1 |
6601087 | Zhu et al. | Jul 2003 | B1 |
6604117 | Lim et al. | Aug 2003 | B2 |
6604128 | Diec | Aug 2003 | B2 |
6609150 | Lee et al. | Aug 2003 | B2 |
6621834 | Scherpbier et al. | Sep 2003 | B1 |
6654032 | Zhu et al. | Nov 2003 | B1 |
6665648 | Brodersen et al. | Dec 2003 | B2 |
6665655 | Warner et al. | Dec 2003 | B1 |
6684438 | Brodersen et al. | Feb 2004 | B2 |
6711565 | Subramaniam et al. | Mar 2004 | B1 |
6724399 | Katchour et al. | Apr 2004 | B1 |
6728702 | Subramaniam et al. | Apr 2004 | B1 |
6728960 | Loomans | Apr 2004 | B1 |
6732095 | Warshavsky et al. | May 2004 | B1 |
6732100 | Brodersen et al. | May 2004 | B1 |
6732111 | Brodersen et al. | May 2004 | B2 |
6754681 | Brodersen et al. | Jun 2004 | B2 |
6763351 | Subramaniam et al. | Jul 2004 | B1 |
6763501 | Zhu et al. | Jul 2004 | B1 |
6768904 | Kim | Jul 2004 | B2 |
6772229 | Achacoso et al. | Aug 2004 | B1 |
6782383 | Subramaniam et al. | Aug 2004 | B2 |
6804330 | Jones et al. | Oct 2004 | B1 |
6826565 | Ritchie et al. | Nov 2004 | B2 |
6826582 | Chatterjee et al. | Nov 2004 | B1 |
6826745 | Coker et al. | Nov 2004 | B2 |
6829655 | Huang et al. | Dec 2004 | B1 |
6842748 | Warner et al. | Jan 2005 | B1 |
6850895 | Brodersen et al. | Feb 2005 | B2 |
6850949 | Warner et al. | Feb 2005 | B2 |
6907566 | McElfresh et al. | Jun 2005 | B1 |
7062502 | Kesler | Jun 2006 | B1 |
7069231 | Cinarkaya et al. | Jun 2006 | B1 |
7069497 | Desai | Jun 2006 | B1 |
7100111 | McElfresh et al. | Aug 2006 | B2 |
7181758 | Chan | Feb 2007 | B1 |
7269590 | Hull et al. | Sep 2007 | B2 |
7289976 | Kihneman et al. | Oct 2007 | B2 |
7340411 | Cook | Mar 2008 | B2 |
7356482 | Frankland et al. | Apr 2008 | B2 |
7373599 | McElfresh et al. | May 2008 | B2 |
7401094 | Kesler | Jul 2008 | B1 |
7406501 | Szeto et al. | Jul 2008 | B2 |
7412455 | Dillon | Aug 2008 | B2 |
7454509 | Boulter et al. | Nov 2008 | B2 |
7508789 | Chan | Mar 2009 | B2 |
7599935 | La et al. | Oct 2009 | B2 |
7603331 | Tuzhilin et al. | Oct 2009 | B2 |
7603483 | Psounis et al. | Oct 2009 | B2 |
7620655 | Larsson et al. | Nov 2009 | B2 |
7644122 | Weyer et al. | Jan 2010 | B2 |
7668861 | Steven | Feb 2010 | B2 |
7698160 | Beaven et al. | Apr 2010 | B2 |
7730478 | Weissman | Jun 2010 | B2 |
7747648 | Kraft et al. | Jun 2010 | B1 |
7779039 | Weissman et al. | Aug 2010 | B2 |
7779475 | Jakobson et al. | Aug 2010 | B2 |
7827208 | Bosworth et al. | Nov 2010 | B2 |
7851004 | Hirao et al. | Dec 2010 | B2 |
7853881 | Aly et al. | Dec 2010 | B1 |
7945653 | Zuckerberg et al. | May 2011 | B2 |
8005896 | Cheah | Aug 2011 | B2 |
8014943 | Jakobson | Sep 2011 | B2 |
8015495 | Achacoso et al. | Sep 2011 | B2 |
8032297 | Jakobson | Oct 2011 | B2 |
8073850 | Hubbard et al. | Dec 2011 | B1 |
8082301 | Ahlgren et al. | Dec 2011 | B2 |
8095413 | Beaven | Jan 2012 | B1 |
8095531 | Weissman et al. | Jan 2012 | B2 |
8095594 | Beaven et al. | Jan 2012 | B2 |
8103611 | Tuzhilin et al. | Jan 2012 | B2 |
8150913 | Cheah | Apr 2012 | B2 |
8209308 | Rueben et al. | Jun 2012 | B2 |
8209333 | Hubbard et al. | Jun 2012 | B2 |
8275836 | Beaven et al. | Sep 2012 | B2 |
8457545 | Chan | Jun 2013 | B2 |
8484111 | Frankland et al. | Jul 2013 | B2 |
8490025 | Jakobson et al. | Jul 2013 | B2 |
8504945 | Jakobson et al. | Aug 2013 | B2 |
8510045 | Rueben et al. | Aug 2013 | B2 |
8510664 | Rueben et al. | Aug 2013 | B2 |
8566301 | Rueben et al. | Oct 2013 | B2 |
8621015 | Chauhan | Dec 2013 | B2 |
8646103 | Jakobson et al. | Feb 2014 | B2 |
8756275 | Jakobson | Jun 2014 | B2 |
8769004 | Jakobson | Jul 2014 | B2 |
8769017 | Jakobson | Jul 2014 | B2 |
9519711 | Chauhan | Dec 2016 | B2 |
10489790 | Chauhan | Nov 2019 | B2 |
10977661 | Chauhan | Apr 2021 | B2 |
11386434 | Chauhan | Jul 2022 | B2 |
11715110 | Chauhan | Aug 2023 | B2 |
20010044791 | Richter et al. | Nov 2001 | A1 |
20020072951 | Lee et al. | Jun 2002 | A1 |
20020082892 | Raffel et al. | Jun 2002 | A1 |
20020129352 | Brodersen et al. | Sep 2002 | A1 |
20020140731 | Subramaniam et al. | Oct 2002 | A1 |
20020143997 | Huang et al. | Oct 2002 | A1 |
20020162090 | Parnell et al. | Oct 2002 | A1 |
20020165742 | Robins | Nov 2002 | A1 |
20030004971 | Gong et al. | Jan 2003 | A1 |
20030018705 | Chen et al. | Jan 2003 | A1 |
20030018830 | Chen et al. | Jan 2003 | A1 |
20030066031 | Laane | Apr 2003 | A1 |
20030066032 | Ramachandran et al. | Apr 2003 | A1 |
20030069936 | Warner et al. | Apr 2003 | A1 |
20030070000 | Coker et al. | Apr 2003 | A1 |
20030070004 | Mukundan et al. | Apr 2003 | A1 |
20030070005 | Mukundan et al. | Apr 2003 | A1 |
20030074418 | Coker | Apr 2003 | A1 |
20030120675 | Stauber et al. | Jun 2003 | A1 |
20030151633 | George et al. | Aug 2003 | A1 |
20030159136 | Huang et al. | Aug 2003 | A1 |
20030187921 | Diec | Oct 2003 | A1 |
20030189600 | Gune et al. | Oct 2003 | A1 |
20030204427 | Gune et al. | Oct 2003 | A1 |
20030206192 | Chen et al. | Nov 2003 | A1 |
20030225730 | Warner et al. | Dec 2003 | A1 |
20040001092 | Rothwein et al. | Jan 2004 | A1 |
20040010489 | Rio | Jan 2004 | A1 |
20040015981 | Coker et al. | Jan 2004 | A1 |
20040027388 | Berg et al. | Feb 2004 | A1 |
20040128001 | Levin et al. | Jul 2004 | A1 |
20040186860 | Lee et al. | Sep 2004 | A1 |
20040193510 | Catahan, Jr. et al. | Sep 2004 | A1 |
20040199489 | Barnes-Leon et al. | Oct 2004 | A1 |
20040199536 | Barnes Leon et al. | Oct 2004 | A1 |
20040199543 | Braud et al. | Oct 2004 | A1 |
20040249854 | Barnes-Leon et al. | Dec 2004 | A1 |
20040260534 | Pak et al. | Dec 2004 | A1 |
20040260659 | Chan et al. | Dec 2004 | A1 |
20040268299 | Lei et al. | Dec 2004 | A1 |
20050050555 | Exley et al. | Mar 2005 | A1 |
20050091098 | Brodersen et al. | Apr 2005 | A1 |
20060021019 | Hinton et al. | Jan 2006 | A1 |
20070214097 | Parsons et al. | Sep 2007 | A1 |
20080249972 | Dillon | Oct 2008 | A1 |
20090012760 | Schunemann | Jan 2009 | A1 |
20090063415 | Chatfield et al. | Mar 2009 | A1 |
20090094340 | Gillai | Apr 2009 | A1 |
20090100342 | Jakobson | Apr 2009 | A1 |
20090164233 | Arnold | Jun 2009 | A1 |
20090177484 | Davis et al. | Jul 2009 | A1 |
20090177744 | Marlow et al. | Jul 2009 | A1 |
20090182832 | O'Sullivan | Jul 2009 | A1 |
20090210507 | Haverkos | Aug 2009 | A1 |
20090307320 | Golan | Dec 2009 | A1 |
20100144318 | Cable | Jun 2010 | A1 |
20100161734 | Wang | Jun 2010 | A1 |
20100223341 | Manolescu | Sep 2010 | A1 |
20100293055 | Nash | Nov 2010 | A1 |
20100325107 | Kenton et al. | Dec 2010 | A1 |
20110055264 | Sundelin | Mar 2011 | A1 |
20110218958 | Warshavsky et al. | Sep 2011 | A1 |
20110247051 | Bulumulla et al. | Oct 2011 | A1 |
20110276638 | Errico | Nov 2011 | A1 |
20120042218 | Cinarkaya et al. | Feb 2012 | A1 |
20120233137 | Jakobson et al. | Sep 2012 | A1 |
20120290407 | Hubbard et al. | Nov 2012 | A1 |
20130212497 | Zelenko et al. | Aug 2013 | A1 |
20130218948 | Jakobson | Aug 2013 | A1 |
20130218949 | Jakobson | Aug 2013 | A1 |
20130218966 | Jakobson | Aug 2013 | A1 |
20130247216 | Cinarkaya et al. | Sep 2013 | A1 |
20130326622 | Chasin | Dec 2013 | A9 |
20140359537 | Jackobson et al. | Dec 2014 | A1 |
20150006289 | Jakobson et al. | Jan 2015 | A1 |
20150007050 | Jakobson et al. | Jan 2015 | A1 |
20150095162 | Jakobson et al. | Apr 2015 | A1 |
20150142596 | Jakobson et al. | May 2015 | A1 |
20150172563 | Jakobson et al. | Jun 2015 | A1 |
20160379222 | Chauhan et al. | Dec 2016 | A1 |
20170091776 | Chauhan | Mar 2017 | A1 |
20190197558 | Chauhan et al. | Jun 2019 | A1 |
20200074474 | Chauhan | Mar 2020 | A1 |
20210279738 | Chauhan | Sep 2021 | A1 |
20220383328 | Chauhan | Dec 2022 | A1 |
Entry |
---|
“Google Plus Users”, Google+Ripples, Oct. 31, 2011 [retrieved on Feb. 21, 2012 from Internet at http://www.googleplusers.com/google-ripples.html], 3 pages. |
Microsoft, “E-mail to Case_Lead Using CRM 4 Workflow”, Feb. 19, 2008, 20 pages [retrieved on Dec. 9, 2016]. Retrieved from the Internet URL: https://blogs.msdn.microsoft.com/crm/2008/02/19/e-mail-to-caselead-using-crm-4-workflow (SALE 1032-4). |
Microsoft, “How do I convert an email into a Lead or a Case”, Sep. 27, 2006, 7 pages [retrieved on Dec. 9, 2016]. Retrieved from the Internet URL: https://blogs.msdn.microsoft.com/crm/2006/09/27/how-do-i-convert-an-email-into-a-lead-or-a-case (SALE 1032-4). |
U.S. Non-Final Office Action dated Feb. 15, 2023 in U.S. Appl. No. 17/806,997. |
U.S. Notice of Allowance dated Dec. 14, 2020 issued in U.S. Appl. No. 16/676,182. |
U.S. Notice of Allowance dated Jan. 26, 2022 issued U.S. Appl. No. 17/249,956. |
U.S. Notice of Allowance dated Jul. 29, 2019 issued in U.S. Appl. No. 15/374,807. |
U.S. Notice of Allowance dated Aug. 26, 2013 issued in U.S. Appl. No. 12/917,326. |
U.S. Notice of Allowance dated Aug. 9, 2016 issued in U.S. Appl. No. 14/145,870. |
U.S. Notice of Allowance dated Mar. 9, 2022 in U.S. Appl. No. 17/249,956. |
U.S. Notice of Allowance dated Mar. 9, 2023 in U.S. Appl. No. 17/806,997. |
U.S. Office Action dated Nov. 24, 2021 issued in U.S. Appl. No. 17/249,956. |
U.S. Office Action dated Nov. 4, 2020 issued in U.S. Appl. No. 16/676,182. |
U.S. Office Action dated Dec. 18, 2015 issued in U.S. Appl. No. 14/145,870. |
U.S. Office Action dated Apr. 5, 2019 issued in U.S. Appl. No. 15/374,807. |
U.S. Office Action dated May 10, 2013 issued in U.S. Appl. No. 12/917,326. |
U.S. Office Action dated Sep. 18, 2012 issued in U.S. Appl. No. 12/917,326. |
Number | Date | Country | |
---|---|---|---|
20230394490 A1 | Dec 2023 | US |
Number | Date | Country | |
---|---|---|---|
61256861 | Oct 2009 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 17806997 | Jun 2022 | US |
Child | 18331563 | US | |
Parent | 17249956 | Mar 2021 | US |
Child | 17806997 | US | |
Parent | 16676182 | Nov 2019 | US |
Child | 17249956 | US | |
Parent | 15374807 | Dec 2016 | US |
Child | 16676182 | US | |
Parent | 14145870 | Dec 2013 | US |
Child | 15374807 | US | |
Parent | 12917326 | Nov 2010 | US |
Child | 14145870 | US |