To provide reporting consistency and clarity, Users are required to adhere to these naming conventions.
Account Naming Conventions
Users should provide as much clarity as possible when creating Account names. An organization's full name should always be used. Avoid acronyms and abbreviations.
For example, Johnson Controls, Inc. should be named as such in this Salesforce instance. This company is often referred to as JCI. This acronym should be avoided. Only use the acronym/abbreviation when the organization operates exclusively with this shortened name, such as 3M for Minnesota, Manufacturing, and Mining Company.
Engagement Name (* See rule for Multiple Accounts)
Account (Organization) Name: Title of Engagement
Example: Under Armour: On-Campus meeting with Wisconsin School of Business and College of Engineering
Outcome Name (* See rule for Multiple Accounts)
Account (Organization) Name: Title of Outcome
Example: Under Armour: Funding for graduate student fellowship
Referral Name (* See rule for Multiple Accounts)
Account (Organization) Name: Short description of Referral
Example: Under Armour: Inquiry for Marketing and Finance student recruitment
Multiple organizations / Accounts are involved in an Engagement, Outcome, and Referral
Multiple Accounts: Short description of Engagement (do not list all of the organizations' names - just include the text "Multiple Accounts")
Example: Multiple Accounts: Fall 2020 Research Day at the Capital
University of Wisconsin - Madison Accounts
Users CANNOT make new Accounts for UW-Madison units. Please make an Account creation request to email@example.com. This ensures proper naming conventions and applications of UW unit identification codes.
Example: User wants to make an Account for University Housing. The User should NOT do this. They should request the creation by sending an email to firstname.lastname@example.org. The administrator will make the Account with proper naming and identification code.