Empower customer self-service with Visual Workflows

I recently discovered a new, and potentially very powerful use for a hidden gem in the Salesforce Sales Cloud platform.  Many organizations who have Enterprise edition of Sales Cloud are not utilizing the Visual Workflow tool.   This “hidden gem” lets business process designers build visual flows which can, for example, serve as scripts for insides sales or support.

Within these flows the designer can incorporate queries of multiple Salesforce objects, create new records and update existing records.  This is a powerful “click not code” approach to walk users through business processes from within a controlled user interface.  This in itself is very powerful.  (If you would like to learn more about Visual Workflows, I have included a link to the implementation guide below.)  What many do not know however is that you can also expose these visual workflows (VWF) to external users on the Web. 

Is WFR for Self-Service the right option?

Allowing customers the ability to create, verify or update data in Salesforce opens up a number of intriguing possibilities such as:

• Allowing leads to provide qualifying responses to questions before a sales call.
• Give customers a way to submit requests or check the status of an order.

The Manufacturer’s Guide to Marketing Through Partner Enablement in 2021

Learn how partnerships allow manufacturers to scale revenue growth beyond what’s possible with direct sales alone.

Get the Guide

I am not suggesting that VWF replaces any need for communities or custom Visualforce, or that it is always the best way to engage external users in business processes, but it certainly is a great tool if the business case fits.  If the following criteria fit, consider using a VWF.

1.  The process may include getting and updating data on several different records during the flow.
2. This is a business process that tends to be fluid or potentially short lived.  A business or admin user can support it as opposed to using a developer for coding.
3. It’s a “one-off” customer support task that is not part of a bigger customer support portal requirement.
4. You are okay with more Spartan graphic design options.  VWF can be styled with Visualforce but then we would be back to writing code.

If this sounds like your process then using a Flow might be the way to go.  There are a few security constraints that Salesforce enforces when accessing a flow through a public URL.  This approach also requires a good knowledge of Force.com sites and the Salesforce security model for sites.  I won’t go into all of these gotchas on this blog post but feel free to reach out with questions and comments.

How it’s done – 10K foot

To build your first publicly accessible VWF you will need to complete the following three steps:

1. Create a Force.com site from within your Salesforce organization.
2. Build your Flow and activate it.
3. Create a simple Visualforce page that references your flow and make that your site landing page. (Code snippet below)

Note: the API name for your Flow replaces the highlighted code above. 

I do recommend you consider having someone from Perficient help mentor you through your first time.  There are a couple “Gotchas” that can cost time and impact your design.  Happy flow building!

Resources:

https://na10.salesforce.com/help/pdfs/en/salesforce_vpm_implementation_guide.pdf