Campaigns – Marketing Projects that need to be planned, managed, and tracked in Salesforce.com
Leads – Persons or Companies interested in products – Prospects or Suspects
Accounts – Orgs, individuals or companies doing business
Contacts – Individuals associated to Accounts
Opportunities – Potential Sales Deals
Cases – Detailed description of customer’s feedback, problem, question
Solutions – description of issue and resolutions – solution knowledge base
Forecasts – Best estimates of Revenue generation
Documents – store files in folders with access rules
Reports – Summary and analysis of data – displayed or printed
Dashboard – collection of charts and components – real time snap shot of metrics and KPIs
Activities – Task and Calendar Events
Products – Individual Items sold on Opportunity
Accounts are where the company contact info is stored. Understand the Person Account- this type of account combines the contact and account into one object type. This would be used for b2c applications where two records would be redundant. Person Accounts must be specifically requested and can only be enabled by Salesforce.com staff.
Activities are split into tasks and events. Tasks are typically phone call or emails that would be logged on the account/lead/opportunity/case. Note that the look-up field field on activity is not standard because it can reference many different objects (more on this later). Events are appointments; think calendar items in Outlook. Activities are enabled on a per-object basis. This meY that while you log calls on an account you cannot log a call on a report, for instance.
Assets can be used to track your company’s or your clients’ assets. They relate to the account and contact, and link to Products, by default. Products do not need to be added to a price book to be linked to an asset.
Campaigns are used for marketing purposes. Leads and contacts can be added to a marketing campaign. The campaign can then be used to track response rates to marketing campaign, establish ROI, and so forth. Web-to-lead can be configured to automatically add your lead to one campaign.
Documents are different than files attached to objects. Documents are shared online documents and are used where you would store graphics for email templates and other files that Salesforce uses.
Cases are used to track support issues. They can be configured to be accessible through the self-service portal (Salesforce.com support is set up this way). Email-to-case and web-to-case are also possible.
Contacts store contact information, and are linked to accounts. If a contact is not linked to an account then it is a “private” contact and only viewable by the contact owner or salesforce administrator.
Contracts used to track contractual agreements and provide an audit history of that agreement. Contracts are related to accounts, not opportunities.
Dashboards are comprised of components. Each component links to a report or external source. Each report can provide only one summary field (two for matrix reports). The component determines how the data of the report is presented. Dashboards are only as current as the last time they were refreshed. A dashboard refresh can be done manually, or can be scheduled on a daily/weekly/monthly and emailed upon automated refresh.
Forecasts can be used to project revenue, and track user quotas. Customizable forecasting can be used for users to override projections in opportunities.
Opportunity Products can be added to opportunities to represent line items in a sale. Opportunity "3 widgets" represents the sale of 3 widgets at $40/pop. You would add an opportunity product linked to the product "widget", qty 3, price $40. Opportunities products are linked to Opportunities through a master/detail relationship. Products must be added to a price book to be selectable as an opportunity product.
Products would typically be used to store the products that your company sells, or the assets that your company or clients maintain. Add products to price books to establish pricing for opportunity products.
Leads can be converted to a contact, account, and opportunity. Web-to-lead will allow you to convert website submissions directly into Salesforce leads.
Opportunities represent a)a sale or b)a lost sale or c)the potential for a sale. The stage field of the opportunity indicates at what point in the sales cycle the opportunity currently resides, and marks the probability (%) field with the corresponding percentage. This probability field is often used to create projections. Each stage can be marked as Closed/Won (sold) or Closed/Lost (lost) or neither (open); abc respectively.
Price Books are used to establish different pricing structures for products. Large client A gets the product for $50, while the public list price is $100. No problem- create the price book "Large client A" and add the product to that price book for $50; add the product to the "Standard Price Book" for $100.
Solutions are used to create Answers to commonly created cases. Solutions must be reviewed before publishing, and can be made accessible in the self-service portal creating a knowledge base type of application.
Users are the ones that log into Salesforce.com. When a user is no longer "active" you can no longer assign records to that user.
Leads – Persons or Companies interested in products – Prospects or Suspects
Accounts – Orgs, individuals or companies doing business
Contacts – Individuals associated to Accounts
Opportunities – Potential Sales Deals
Cases – Detailed description of customer’s feedback, problem, question
Solutions – description of issue and resolutions – solution knowledge base
Forecasts – Best estimates of Revenue generation
Documents – store files in folders with access rules
Reports – Summary and analysis of data – displayed or printed
Dashboard – collection of charts and components – real time snap shot of metrics and KPIs
Activities – Task and Calendar Events
Products – Individual Items sold on Opportunity
Accounts are where the company contact info is stored. Understand the Person Account- this type of account combines the contact and account into one object type. This would be used for b2c applications where two records would be redundant. Person Accounts must be specifically requested and can only be enabled by Salesforce.com staff.
Activities are split into tasks and events. Tasks are typically phone call or emails that would be logged on the account/lead/opportunity/case. Note that the look-up field field on activity is not standard because it can reference many different objects (more on this later). Events are appointments; think calendar items in Outlook. Activities are enabled on a per-object basis. This meY that while you log calls on an account you cannot log a call on a report, for instance.
Assets can be used to track your company’s or your clients’ assets. They relate to the account and contact, and link to Products, by default. Products do not need to be added to a price book to be linked to an asset.
Campaigns are used for marketing purposes. Leads and contacts can be added to a marketing campaign. The campaign can then be used to track response rates to marketing campaign, establish ROI, and so forth. Web-to-lead can be configured to automatically add your lead to one campaign.
Documents are different than files attached to objects. Documents are shared online documents and are used where you would store graphics for email templates and other files that Salesforce uses.
Cases are used to track support issues. They can be configured to be accessible through the self-service portal (Salesforce.com support is set up this way). Email-to-case and web-to-case are also possible.
Contacts store contact information, and are linked to accounts. If a contact is not linked to an account then it is a “private” contact and only viewable by the contact owner or salesforce administrator.
Contracts used to track contractual agreements and provide an audit history of that agreement. Contracts are related to accounts, not opportunities.
Dashboards are comprised of components. Each component links to a report or external source. Each report can provide only one summary field (two for matrix reports). The component determines how the data of the report is presented. Dashboards are only as current as the last time they were refreshed. A dashboard refresh can be done manually, or can be scheduled on a daily/weekly/monthly and emailed upon automated refresh.
Forecasts can be used to project revenue, and track user quotas. Customizable forecasting can be used for users to override projections in opportunities.
Opportunity Products can be added to opportunities to represent line items in a sale. Opportunity "3 widgets" represents the sale of 3 widgets at $40/pop. You would add an opportunity product linked to the product "widget", qty 3, price $40. Opportunities products are linked to Opportunities through a master/detail relationship. Products must be added to a price book to be selectable as an opportunity product.
Products would typically be used to store the products that your company sells, or the assets that your company or clients maintain. Add products to price books to establish pricing for opportunity products.
Leads can be converted to a contact, account, and opportunity. Web-to-lead will allow you to convert website submissions directly into Salesforce leads.
Opportunities represent a)a sale or b)a lost sale or c)the potential for a sale. The stage field of the opportunity indicates at what point in the sales cycle the opportunity currently resides, and marks the probability (%) field with the corresponding percentage. This probability field is often used to create projections. Each stage can be marked as Closed/Won (sold) or Closed/Lost (lost) or neither (open); abc respectively.
Price Books are used to establish different pricing structures for products. Large client A gets the product for $50, while the public list price is $100. No problem- create the price book "Large client A" and add the product to that price book for $50; add the product to the "Standard Price Book" for $100.
Solutions are used to create Answers to commonly created cases. Solutions must be reviewed before publishing, and can be made accessible in the self-service portal creating a knowledge base type of application.
Users are the ones that log into Salesforce.com. When a user is no longer "active" you can no longer assign records to that user.
No comments:
Post a Comment