Salesforce administration Tag

Salesforce User Adoption, Part II: Improving Salesforce User Adoption

team all hands together Creating a great Salesforce app for your team is only part of the solution; the other part is getting your team to use the app. The best tool in the world is useless if it's not used! You've seen plenty of tips about signs your team has bought into using Salesforce. Your next step is improving Salesforce user adoption, and communication, training, and continuous refinement are the keys.

sorting and organizing Many companies use Salesforce not only for sales-related CRM but also for managing disparate business processes. Salesforce record types can help administrators fine-tune their orgs and manage business processes for different users effectively. Sometimes, administrators go a little overboard with custom record types. Even after reading the documentation, it can help to see how other admins utilize Salesforce record types. Here are some tips to help get you started.

Now that your company has rolled out its shiny new CRM system, you’ll want to make sure your team is fully on board. How can you track Salesforce user adoption? What are the signs you don’t have full buy-in from your organization on using Salesforce?Silhouette of many thumbs up Of course, there are many useful reports available in the Salesforce Adoption Dashboards. To get the most benefit from those dashboards and reports, you'll need to quantify your expectations. How should your team use the system?

3D stick man jump over crack floor, business concept, avoid pitfalls.Working with Salesforce relationships is a little different from traditional relational database structures, but Salesforce has great tools for building custom data relationships and most people can adapt quickly to the SOQL model. As with any other system, though, there are a few "gotchas" to watch for when designing Salesforce relationships. I ran into one of these gotchas just recently. I needed a lookup relationship from our custom object to the standard Product table, Product2. No problem, right? Create the lookup field in the custom table, and there it is. Not so fast!