Welcome back to part 2 of our series on Salesforce Lightning Flow. If you missed part one, not to worry! Click here to get caught up. As mentioned at the end of part one, in part two we will be looking at how to know if flow is the right fit for you and your business. So lets drive in!
Is Flow a Good Fit?
How do you determine if Flow is a fit? As with all tools available in Salesforce, we recommend trying to solve your business challenges with out of the box features first, then light customizations. However, we find that page layouts become busy and users can be overwhelmed by the sheer amount of information. This overload of information can usually be directly correlated to the ever-increasing set of business processes that you build into your instance. Without some organization and segmentation of data you can quickly overwhelm users. This can slow them down an impact adoption and data quality.
Flow is your process consolidation MVP. For example, if you require a Sales person to perform qualification activities once an opportunity enters a particular stage, you could create a section on the page layout with those fields. However, those fields are largely useless once used to qualify a prospect, but they will likely stay on your page layout. Instead of keeping them there, you could create a Lightning Flow that steps the Salesperson through a quick questionnaire to gather the datapoints needed, calculate the viability of the prospect, and then display an output to the Salesperson while automatically advancing the stage of the Opportunity.
This ability to segment information into various subprocesses cleans up the page layout and increases user adoption of the aforementioned qualification process. Big win! So how do you build that in flow? Well, for starters, you need to consider what questions you want to ask your users. You’ve got your qualification questions and process outlined. Using Flow, you can place those questions onto various Screen components. You can then create a step by step process using Decision components to qualify the opportunity. Once you’ve finished gathering everything, you can save the qualification questionnaire and allow automation to calculate if the opportunity is qualified. That qualification status can then be shown to the user in the Flow interface.
Building this Process in Lightning Flow
This can all be built with click and drag declarative tools in Lightning Flow Builder. It can be used in the Lightning interface and plugged into a separate sub-tab on an Opportunity record. It can be used in the mobile application. All of these features reduce clutter and increase the simplicity of your process. A guided experience can have much better results than throwing 30-40 fields at a page layout and having your sales reps try to memorize which fields to fill out in which qualifying scenario.
This is just one scenario that can be applicable to any number of Salesforce customers. Expanding your UX chops in Salesforce with Flow will definitely require some strategic thinking. In part three of this series, we will look at a few business processes we’ve solved in Flow for you to consider in the future so be sure to keep an eye out for the next installment in the series.
Josh Sangster is a certified Salesforce Administrator and Senior Consultant at Statera. With six years of CRM administration and consultation experience across multiple verticals and different sizes of businesses he understands the headaches that plague users and administrators. He is currently working on advanced Salesforce certifications in an effort to better serve his clients. He is a transplant from Atlanta, GA residing in Denver, CO and enjoys to golf, hike, camp, swim, bike, exercise, and explore his new home state. He is an avid New York Football Giants fan and can often be found wearing blue and white from head to toe on Sundays in the fall. Go Big Blue!