on 07-19-2017 8:10 PM
Hi! I was curious if anyone uses a standard naming convention for opportunity "name" when creating a new opportunity in C4C. We have only been using C4C globally for a few months and the number of opportunities in the system is growing with 100s of users entering opportunities in different ways. We use different attributes/fields when entering the opportunity to note the type, category, etc but never established a naming convention. I'm curious what other companies do (best practices) and why? Thanks for your input!!!
It completely varies from Business to Business and is mostly dependent on the initial practice that was established by one or the other user,
Ideally best practice (in my perception after looking multiple such naming conventions / Sources from internet.) would be to follow Account Name + Product + Quantity.
The Opportunity Identifier would be something that would help identify what this specific deal is for (i.e., product name + quantity, order date, service name).
Multiple Opportunities: If you have more than one opportunity with an account (i.e., 2004 order/2005 order, product a/service a) you will literally have to click into each Opportunity to find the information about it to understand what it is for
Search and Navigation: if you look on your recent items tab, and you name your Opportunities by product/service only, you will see a bunch of Opportunities named the same, and will not be able to easily find the one you are looking for
Reporting: for Summary and Matrix reports, if you have a limited number of "Group By" options (3 on Summary Reports, 2 on Matrix reports). This would be more relevant for Matrix reports, if you wanted to see Pipeline by Rep, Account and Opportunity - or Rep, Account, Product ... you can't. With only two Group By filters, you won't be able to display all this information on one report
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
7 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.