Customer relationship management system and method

• US 20080091774A1
• Filed: 12/15/2006
• Published: 04/17/2008
• Est. Priority Date: 12/15/2005
• Status: Abandoned Application

• Current Assignee: Sugarcrm Incorporated
• Original Assignee: Sugarcrm Incorporated
• Inventors: Roberts, John, Oram, Clinton, Taylor, Jacob
• Application Number:
  US11/640,053
• Publication Number:
  US 20080091774A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising

Abstract

A software-based customer relationship management system and method.

Claims

1. A customer relationship management system, comprising:

a client;

a database containing a plurality of pieces of information;

one or more modules that access the database to pull pieces of information from the database based on a request from the client and display a user interface to the user containing the requested information;

one or more controllers that control access by the client to the one or more modules and the database; and

a sugarbean class wherein each module further comprises a subclass of the sugarbean class.

2. The system of claim 1 wherein each module further comprises a type ahead component that allows the module to anticipate the typing of the user.

4. The system of claim 1 further comprising a heartbeat module that communicates periodically with a central server.

5. The system of claim 4, wherein the heartbeat module further comprises a license management component wherein the heartbeat module communicates license information between the heartbeat module and the central server.

7. The system of claim 1 further comprising a language module wherein the language of the user interface for each module is changed based on user input in real time without logout.

8. The system of claim 1, wherein each module further comprises a report module wherein the report contains the requested information and a graph that is generated based on the requested information.

9. The system of claim 1, wherein the modules further comprises a dashboard module that is customizable by the user.

10. The system of claim 1 further comprising an email module wherein the email module permits a user to assign group email to one or more users of the system.

11. The system of claim 1 further comprising an email module wherein the email module further comprises a quick action component wherein a quick action button is displayed on the user interface of the email user interface.

12. The system of claim 1, wherein the modules further comprises an administrator module wherein the administrator module further comprises an access control list to control access of the plurality of pieces of information contained in the database.

13. The system of claim 1 further comprising a workflow module.

14. The system of claim 1 further comprising a scheduler module.

15. A computer-based system, comprising:

a client; and

an application system having a database containing a plurality of pieces of information, one or more modules that access the database to pull pieces of information from the database based on a request from the client and display a user interface to the user containing the requested information, one or more controllers that control access by the client to the one or more modules and the database, and a heartbeat module that gathers a set of information about the system including a status of the system so that the set of information about the system can be periodically communicated over a link to a central server.

16. The system of claim 15, wherein the set of information further comprises a set of usage information for the application system.

17. The system of claim 15, wherein the heartbeat module further comprises a license management module that gathers a set of license information about the application system that can be periodically communicated to the central server, and receives a validation key for the license information and validates the combined license information using the validation key.

18. The system of claim 17, wherein the license management module shuts down the application system immediately without a validation key.

19. The system of claim 17, wherein the license management module communicates messages back to the central server and the users of the application system.

20. The system of claim 18, wherein the license management module provides a thirty day warning period before shutting down the application system.

21. The system of claim 17, wherein the application system further comprises a customer relationship management system.

22. The system of claim 15, wherein the heartbeat module communicates the set of information about the application system using a Simple Object Access Protocol over a hypertext transfer protocol or a secure hypertext transfer protocol.

23. The system of claim 15, wherein the heartbeat module communicates the set of information about the application system using hypertext transfer protocol proxies or secure hypertext transfer protocol proxies.

24. A computer-based system, comprising:

a client; and

an application system having a database containing a plurality of pieces of information, one or more modules that access the database to pull pieces of information from the database based on a request from the client and display a user interface to the user containing the requested information, one or more controllers that control access by the client to the one or more modules and the database, wherein the one or more modules further comprises an email module having a quick action component wherein a quick action button is displayed on a user interface of a user interface of the email module.

25. The system of claim 24, wherein the quick action component further comprises a list of actions available to a particular user for an email message.

26. The system of claim 24, wherein the quick action component further comprises a quick action list customized based on an email account or a message contents.

27. The system of claim 24, wherein the quick action component further comprises a default quick action based on a most likely action to be taken.

28. The system of claim 25, wherein the action further comprises a reply action or a create bug action.

29. The system of claim 24, wherein the application system further comprises a customer relationship management system.

30. A computer-based system, comprising:

a client; and

an application system having a database containing a plurality of pieces of information, one or more modules that access the database to pull pieces of information from the database based on a request from the client and display a user interface to the user containing the requested information, one or more controllers that control access by the client to the one or more modules and the database, and wherein the one or more modules have one or more actions associated with the one or more modules that further comprise an administrator module wherein the administrator module further comprises an access control list to control access to each piece of information contained in the database and each action associated with each of the one or more modules.

31. The system of claim 30, wherein the application system further comprises a customer relationship management system.

32. The system of claim 30 further comprising a default for any access control list to allow a role to not restrict modules that the default does not modify.

33. A computer-based system, comprising:

a client; and

an application system having a database containing a plurality of pieces of information, one or more modules that access the database to pull pieces of information from the database based on a request from the client and display a user interface to the user containing the requested information, one or more controllers that control access by the client to the one or more modules and the database, wherein the one or more modules further comprises a customized content unit that further comprises a plurality of lines of computer code executed by the application system that stores a template for a customized piece of content in the database wherein the customized piece of content includes the template and zero or more pieces of customized data, that stores each piece of customized data for each recipient of the customized piece of content in the database and that generates the customized piece of content for each recipient based on the template and the zero or more pieces of customized data so that the actual customized piece of content for each recipient does not need to be stored in the database.

34. The system of claim 33, wherein the customized piece of content further comprises an email message.

35. The system of claim 33, wherein the application system further comprises a customer relationship management system.

36. A method for the storage of mass customized content in a computer-based system having a client and an application system having a database containing a plurality of pieces of information, one or more modules that access the database to pull pieces of information from the database based on a request from the client and display a user interface to the user containing the requested information, one or more controllers that control access by the client to the one or more modules and the database, the method comprising:

storing a template for a customized piece of content in the database wherein the customized piece of content includes the template and zero or more pieces of customized data;

storing each piece of customized data for each recipient of the customized piece of content in the database; and

generating the customized piece of content for each recipient based on the template and the zero or more pieces of customized data so that the actual customized piece of content for each recipient does not need to be stored in the database.

37. The method of claim 36, wherein the customized piece of content further comprises an email message.

38. An apparatus for updating a deployment of a software application having a plurality of modules, comprising:

a plurality of computing devices each having a deployment of a software application wherein each deployment of the software application has a set of modules associated with the deployment, each computing device also having a data gathering unit that gathers a set of deployment information about the deployment on the particular computing device; and

an aggregation computer coupled to the plurality of computing devices over a link, the central computing having an aggregating unit that receives the set of deployment information from each computing device, a module storage unit that stores one or more updates for the deployments.

39. The apparatus of claim 38, wherein the aggregation computer further comprises a core module loader that, based on a set of deployment information from each computing device, automatically provides an update to the deployment on the computing device.

40. The apparatus of claim 38, wherein the set of deployment information for each deployment further comprises at least one of a status of the deployment, a set of licensing information about the modules that are part of the deployment, a set of anonymous usage statistics, a set of non-anonymous usage statistics and a list of a set of elements of the deployment.

42. The apparatus of claim 38, wherein the link further comprises a computer network that uses a secure hypertext transport protocol (HTTPS), hypertext transport protocol (HTTP) or a proxy for the HTTPS or HTTP protocols.

43. The apparatus of claim 38, wherein each deployment further comprises a deployment of a customer relationship management (CRM) application.

44. The apparatus of claim 42, wherein the aggregation computer further comprises a server computer.

45. The apparatus of claim 38, wherein each computing device further comprises a license management unit that receives a validation key for each module that is part of the deployment on the computing device and that validates each module that is part of the deployment on the computing device using the validation key.

46. The apparatus of claim 45, wherein the license management unit shuts down a portion of the deployment that is not validated.

41. The apparatus of 38, wherein the set of elements of the deployment further comprises a version of the deployment, a flavor of the deployment, a set of modules, themes, language packs and extensions of the deployment.

47. A method for updating a deployment of a software application having a plurality of modules, comprising:

gathering at each computing device that hosts a deployment of a software application a set of deployment information about the deployment on the particular computing device; and

receiving, at an aggregation computer coupled to each computing device, the set of deployment information from each computing device.

48. The method of claim 47 further comprising automatically providing an update to the deployment on a particular computing device based on the set of deployment information for the particular computing device.

49. The method of claim 47, wherein the set of deployment information for each deployment further comprises at least one of a status of the deployment, a set of licensing information about the modules that are part of the deployment, a set of anonymous usage statistics and a list of a set of elements of the deployment.

51. The method of claim 47, wherein the link further comprises a computer network that uses a secure hypertext transport protocol (HTTPS), hypertext transport protocol (HTTP) or a proxy for the HTTPS or HTTP protocols.

52. The method of claim 47, wherein each deployment further comprises a deployment of a customer relationship management (CRM) application.

53. The method of claim 47 further comprising receiving, at each computer device, a validation key for each module that is part of the deployment on the computing device and validating each module that is part of the deployment on the computing device using the validation key.

50. The method of 49, wherein the set of elements of the deployment further comprises a version of the deployment, a flavor of the deployment, a set of modules, themes, language packs and extensions of the deployment.