Method and system for wealth management

• US 20100070323A1
• Filed: 09/05/2008
• Published: 03/18/2010
• Est. Priority Date: 09/05/2008
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Choi, Ryan, Polcari, Michael Peter, Hess, Ronald Vance, Yerkes, Rowland W.
• Granted Patent: US 8,296,161 B2
• Time in Patent Office: Days
• US Class Current: 705/8
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 10/1095 Meeting or appointment

Abstract

In accordance with embodiments, there are provided mechanisms and methods for wealth management. These mechanisms and methods for wealth management can enable embodiments to provide a multi-tenant database that stores information about clients of the tenants. In a multi-tenant database, a system for managing financial accounts is established, which may be useful for a tenant that is a financial analyst or that employs financial analysts. The multi-tenant database may include a calendar application that automatically includes the team members associated with the event being scheduled in a list of invitees, and the multi-tenant database may also includes relationship groups, such that information about related individuals (whom may have separate accounts) are automatically associated with one another. The ability of embodiments that provide relationship groups and teams can enable efficiently gathering information about related parties and efficiently inviting that interested parties to an event.

Claims

1. A method of obtaining information from a multi-tenant database comprising:

receiving a request from a user of a tenant of the multi-tenant database for monetary information about a customer of the tenant; and

in response,

associating the customer with a group, the group including at least one other customer of the tenant,

retrieving from the multi-tenant database the monetary information about the customer;

retrieving from the multi-tenant database monetary information about the group that is not included in the monetary information about the customer;

sending the monetary information about the customer to the user of the tenant; and

sending the monetary information about the group that is not included in the information about the customer to the user of the tenant.

2. The method of claim 1, the retrieving from the multi-tenant database of the monetary information about the group includes at least retrieving information about the other customer.

3. The method of claim 1, further comprising

receiving a request to mark a calendar with an event related to a group,

in response,

automatically sending an invitation to each member of a pre-established team that services the group, the invitation inviting the member to the event.

4. The method of claim 1, further comprising

receiving a request to mark a calendar with an event related to a group,

in response,

automatically sending an invitation to each member of the group, the invitation inviting a member of the group to the event.

5. The method of claim 1, further comprising:

establishing a group by at least associating a member with the group by at least establishing a relationship in the database between the member and the group;

assigning roles to the members of the group, each role describing a pre-established relationship that the member has with the group.

6. The method of claim 5, further comprising assigning a name to the group.

7. The method of claim 1, further comprising establishing a group by at least

assigning a name to the group;

associating a description of the group with the group; and

adding members to the group.

8. The method of claim 1, further comprising:

automatically invoking a query searching for team members;

receiving a selection of users from among the users returned by the query;

receiving a selection of an invite element of a graphical user interface; and

in response to receiving the selection of the invite button, automatically sending invitations to the users selected, the invitations inviting the users to an event.

9. The method of claim 1, further comprising:

receiving a request for a view of relationship groups;

in response,

sending information for displaying a webpage including at least

a list of relationship groups;

for a selected relationship group displaying

an entry for a customer identifier that is associated with the customer;

a list of other members of a relationship group to which the customer belongs;

a list account of the client, which include at least an account identifier,

a value of the account, and

a descriptive word describing a type of the account;

financial information of other members of the relationship group including at least

an identifier identifying information of another member of the group, and

a value of a financial account of the other member.

10. The method of claim 9, the webpage further including a list of open activities, each open activity in the list including at least

a description of the open activity,

one or more identifiers of members of the group participating in the activity,

one or more identifiers of user of the tenant participating in the activity, and

a scheduled date for the activity.

11. The method of claim 9, the webpage further including personal information about the customer.

12. The method of claim 1, further comprising:

receiving a request for information about personal interests of the customer; and

in response, sending a webpage having the personal interests of the customer.

13. The method of claim 12, further comprising:

receiving a request for information about financial interests of the customer; and

in response, sending a webpage having the personal interests of the customer.

14. The method of claim 1, further comprising:

sending a webpage having

a first menu including a list of major information categories;

a second menu including a list of subcategories, each major information category being associated with different list of subcategories, the subcategories presented by the second menu being different for each major category;

receiving a selection from the first menu;

receiving a selection from the second menu;

receiving a selection of a particular item of the subcategory; and

in response, presenting list of items of the subcategory and a multiplicity of windows, each window presenting information about a different aspect of the item of the subcategory.

15. The method of claim 14, the first menu selection being set to cause the display of relationship groups and the second menu being set to display a particular type of relationship group, the list of items include at least a list of relationship groups belonging to the particular type;

the multiplicity of windows including at least

a list of members of the relationship group;

a list of open activities;

a history of activities;

a list of financial accounts of the relationship group;

a list of financial accounts jointly owned by more than one member of the relationship group;

a summary of personal interests of members of the relationship group;

a summary of financial interests of members of the relationship group; and

a summary of opportunities of the relationship groups.

16. The method of claim 1, further comprising presenting a series of charts summarizing aspects of customers of the user.

17. The method of claim 1, the group having a multiplicity of members, one or more members of the group being assigned one or more roles.

18. the method of claim 1, the group having a multiplicity of members one or more members being assigned a priority.

19. The method of claim 1, the group having one or more members, each member being associated with an indication as to whether the member is included in a roll-up.

20. The method of claim 1, the user being presented with an option for creating an action plan as a template for performing a task.

21. the method of claim 1, the user being presented with a pre-established user-created template for performing a task.

22. A method of obtaining information from a multi-tenant database comprising:

establishing a group by at least associating a member of the group with the group by at least

establishing a relationship in the database between the member and the group;

assigning roles to the members of the group, each role describing a pre-established relationship that the member has with the group;

assigning a name to the group;

associating a description of the group with the group; and

adding one or more other members to the group;

setting an indication as to whether the member is included in a roll-up;

receiving a request from a user of a tenant of the multi-tenant database for monetary information about a customer of the tenant; and

in response,

determining that customer is associated with a group,

retrieving from the multi-tenant database the monetary information about the customer, the retrieving from the multi-tenant database of the monetary information about the group includes at least retrieving information about the other customer,

retrieving from the multi-tenant database monetary information about the group that is not included in the monetary information about the customer;

sending the monetary information about the customer to the user of the tenant; and

sending the monetary information about the group that is not included in the information about the customer to the user of the tenant, the monetary information about the group being determined based on monetary information of members of the group having an the indication of being included in the roll-up and not including monetary information of members having the indication of not being included in the roll-up;

receiving a request to mark a calendar with an event related to a group;

in response,

automatically sending an invitation to each member of a pre-established team that services the group, the invitation inviting the member of the pre-established team to the event;

automatically invoking a query searching for team members;

automatically selecting the team members to be invitees;

receiving a selection of an invite element of a graphical user interface;

in response to receiving the selection of the invite button, automatically sending invitations to the team members, the invitations inviting the users to the event;

receiving a request for a view of relationship groups;

in response,

sending information for displaying a webpage including at least

a list of relationship groups;

for a selected relationship group displaying

an entry for a customer identifier that is associated with the customer;

a list of other members of a relationship group to which the customer belongs;

a list of accounts of the customer, which for each account includes at least

an account identifier,

a value of the account, and

a descriptive word describing a type of the account;

financial information of other members of the relationship group including at least

an identifier identifying information of another member of the group, and

a value of a financial account of the other member;

the webpage further including a list of open activities, each open activity in the list including at least

a description of the open activity,

one or more identifiers of members of the group participating in the activity,

one or more identifiers of users of the tenant participating in the activity, and

a scheduled date for the activity;

the webpage further including personal information about the customer;

receiving a request for information about personal interests of the customer; and

in response, sending a webpage having the personal interests of the customer;

receiving a request for information about financial interests of the customer; and

in response, sending a webpage having the personal interests of the customer;

receiving a request to view a console webpage

sending a console webpage having

a first menu including a list of major information categories;

a second menu including a list of subcategories, each major information category being associated with different list of subcategories, the subcategories presented by the second menu being different for each major category;

receiving a selection from the first menu;

receiving a selection from the second menu;

receiving a selection of a particular item of the subcategory; and

in response, presenting a list of items of the subcategory and a multiplicity of windows, each window presenting information about a different aspect of the item of the subcategory;

the first menu selection being set to cause the display of relationship groups and the second menu being set to display a particular type of relationship group, the list of items include at least a list of relationship groups belonging to the particular type;

the multiplicity of windows including

a list of members of the relationship group;

a list of open activities;

a history of activities;

a list of financial accounts of the relationship group;

a list of financial accounts jointly owned by more than one member of the relationship group;

a summary of personal interests of members of the relationship group;

a summary of financial interests of members of the relationship group; and

a summary of opportunities of the relationship groups;

presenting a series of charts summarizing aspects of customers of the user.

23. A method of obtaining information from a multi-tenant database comprising:

sending a request from a user of a tenant of the multi-tenant database for monetary information about a customer of the tenant; and

in response,

receiving the monetary information about the customer to the user of the tenant; and

receiving the monetary information about the group that is not included in the information about the customer to the user of the tenant.

24. A machine readable medium storing thereon a one or more machine instructions, which when implemented cause the machine to perform a method of obtaining information from a multi-tenant database comprising:

receiving a request from a user of a tenant of the multi-tenant database for monetary information about a customer of the tenant; and

in response,

associating the customer with a group, the group including at least one other customer of the tenant,

retrieving from the multi-tenant database the monetary information about the customer;

retrieving from the multi-tenant database monetary information about the group that is not included in the monetary information about the customer;

sending the monetary information about the customer to the user of the tenant; and

sending the monetary information about the group that is not included in the information about the customer to the user of the tenant.

25. The machine readable medium of claim 24, the retrieving from the multi-tenant database the monetary information about the group includes retrieving information about the other customer.

26. The machine readable medium of claim 24, the method further comprising:

establishing a group by at least associating a member with the group by at least establishing a relationship in the database between the member and the group;

assigning roles to the members of the group, each role describing a pre-established relationship that the member has with the group.

27. The machine readable medium of claim 24, the method further comprising establishing a group by at least

assigning a name to the group;

associating a description of the group; and

adding members to the group.