Book Image

Salesforce Sales Cloud – An Implementation Handbook

By : Kerry Townsend
Book Image

Salesforce Sales Cloud – An Implementation Handbook

By: Kerry Townsend

Overview of this book

Salesforce Sales Cloud is a system rich in functionality, addressing many sales business challenges such as sales productivity, forecast visibility, and sales enablement. However, unlocking the full value of the system and getting maximum returns pose a challenge, especially if you’re new to the technology. This implementation handbook goes beyond mere configuration to ensure a successful implementation journey. From laying the groundwork for your project to engaging stakeholders with sales-specific business insights, this book equips you with the knowledge you need to plan and execute. As you progress, you’ll learn how to design a robust data model to support the sales and lead generation process, followed by crafting an intuitive user experience to drive productivity. You’ll then explore crucial post-building aspects such as testing, training, and releasing functionality. Finally, you’ll discover how the solutions’ capability can be expanded by adding and integrating other tools to address typical sales use cases. By the end of this book, you’ll have grasped how to leverage Sales Cloud to solve sales challenges and have gained the confidence to design and implement solutions successfully with the help of real-world use cases.
Table of Contents (20 chapters)
1
Part 1:Building the Fundamentals
7
Part 2: Preparing to Release
13
Part 3: Beyond the Fundamentals

Post-go-live support

It is tempting to think that once the deployment is complete and the system is live, that is the end of the work. However, the post-go-live period is critical. Users are forming their opinions about the system that will have a lasting impact. It is recommended that you plan how the system will be supported directly after go-live rather than working out a course of action once you get there.

Note

The aim is always that that there will be no issues post-go-live but, in reality, issues do occur for a number of reasons. Users use the system in a way that wasn’t tested, data anomalies occur that cause errors, and things get missed in the deployment and data migration.

There are a couple of elements that you will want to have in place. You will need a communicated method of capturing, triaging, and resolving system defects. This includes agreement about the environment defects will be resolved in and the frequency with which they will be deployed. These...