Set Up Salesforce Flow for Service

After completing this unit, you’ll be able to:

In addition, to show recommendations that result from Einstein Next Best Action, Maria must create flows that contain offers and actions. Then she can create recommendations and action strategies that filter them.

At the end of this unit, we provide instructions to install a package that contains Maria’s flows and action strategies.

Maria starts by creating flows for her steps. Salesforce Flow for Service supports screen flows, field service mobile flows, autolaunched flows, and quick actions. Maria wants flows that guide her agents interactively, so she creates screen flows.

From Setup, she types Flows into the Quick Find Box, and selects Flows to start Flow Builder. (To refresh your flow-building skills, visit the Flow Basics Trailhead module.)

To create each flow, Maria adds screen and other logic elements to the canvas. When she’s done, she saves the flow, activates it, and tests it. To confirm that the flows reflect best practices, Maria demos her flows to a few top agents.

Important: Remember to activate your flows.

To display quick actions in the Actions & Recommendations component, make them available on the record page layout. For example, Maria makes sure that the Log a Call quick action for cases, Case.LogACall, is available in the Case record page layout.

Several standard quick actions are available in Lightning Experience. In addition, you can create custom quick actions. To make actions available in the record page layout, follow these steps.

• From Setup, enter Object Manager into the Quick Find box, and select Object Manager.
• Select Case, open Case Page Layouts, and edit the Case Layout.
• In the Case Layout section at the top, select Mobile & Lightning Actions.
• Under Salesforce Mobile and Lightning Experience Actions, override the predefined actions. Then drag quick actions from the top section and add them to the page layout.
• Click Save.

Roberto wants to extend special offers to certain customers who experienced problems with broken solar panels. Maria configures Einstein Next Best Action so that recommendations can appear in the component with the steps for her call script.

Before she begins, Maria visits Get Started with Einstein Next Best Action. She starts by creating the flows that launch when the user accepts a recommendation. Then she’s ready to create these sample recommendations.

• A discount offer for the gold service plan. This recommendation references the flow Offer Gold Service Discount.
• A future purchase discount. This recommendation references the flow Offer 1-Time Discount.

At the end of this unit, we provide instructions to install a package with sample flows and action strategies. You can install the package now and follow along. Otherwise, when it’s time to complete the hands-on challenge, you can use the packaged flows to create recommendations.

1. From the App Launcher, find and select Recommendations.
2. Click New, and enter a name, a description, and acceptance and rejection labels.
3. Select the flow that launches when the recommendation is accepted.
4. Optionally, upload an image to show with the offer or action.
5. Click Save.

Next, Maria creates an action strategy so that recommendations can appear on the case page. From Setup, in the Quick Find box, she enters Next Best Action, and selects Next Best Action.

If you are following along, the provided package includes two action strategies. One strategy specifies the Case page as the object where recommendations appear, while the other strategy is global. You select which strategy to use later when we configure recommendation settings in the Actions & Recommendations deployment.

Using Strategy Builder, Maria creates a strategy that loads and filters her recommendations. She also tests the strategy in Strategy Builder. Later, she’ll work with Roberto to develop more recommendations and refine the filtering logic in her strategy.

Maria does a quick review of the prework she’s done. So far, she’s configured flows, quick actions, recommendations, and action strategies. Now she’s ready to create RecordActions for the steps in her call script.

In a deployment, you can configure different default actions for each channel.

• Chat—This channel works with Chat in Lightning Experience.
• Phone—This channel works with Open CTI and softphone screen-pop settings.
• Default—Use this channel to specify default actions for when records open from list views or related records.

When a record opens in a channel, the component shows the default steps for that channel. For example, suppose that you use Open CTI and configure default actions for the phone channel. The component then shows those actions when the phone number matches and the caller’s contact record is popped. If agents navigate to the contact record page manually, such as when they open the record from a list view, they see the actions configured for the Default channel.

If you want to follow along, use the instructions at the end of this unit and install the package that we provide. You use this package when it’s time to complete the hands-on challenge.

1. From Setup, in the Quick Find box, enter Actions & Recommendations, and select Actions & Recommendations.
2. Click New Deployment, and click Next.
3. Name your deployment, for example, Broken Solar Panel, and select which guidance to show. Maria selects Flows and quick actions and Recommendations.
4. Click Next.
5. Select up to 10 objects to use as context for object-specific quick actions and Next Best Action strategies. Maria selects the Account, Case, and Contact objects. When you associate a quick action or action strategy with an object, you give that action or strategy an object-specific context. When a user opens a page for that object, they see global and object-specific actions and recommendations. On other page types, they see only global items. For example, suppose that Maria defines an object-specific quick action for the Case object. To show that quick action in the component on Case pages, she selects Case as a context object.
6. Click Next.
7. Configure default actions for each channel. Maria clicks the tab for the Default channel (1).
8. Drag actions from All Actions (2) to regions in the preview area (3). Maria drags the Verify Caller and Customer Feedback flows to the top and bottom pinned regions, respectively. She places the Triage and Repair and Order Replacement flows in the unpinned region. She also adds the Log a Call (Case) quick action to the unpinned region.
9. Select actions that are important to complete, and click Mark Mandatory (4). Maria selects Verify Caller and marks it as mandatory. If an agent tries to close this flow without completing it, a reminder appears.
10. Select actions that you don’t want agents to remove, and click Unmark Removable (5). By default, all actions are removable. For example, Maria doesn’t want agents to remove Verify Caller. She selects that flow and unmarks it so agents don’t see the Remove option.
11. Specify whether to auto-launch the first flow in the list when the record page opens (6).
12. Click Next.
13. Select other actions that the user can start from the component at run time. Maria configures the actions that agents use most often, including the flows for Order Parts and Change Delivery Address. If agents need a step that isn’t in the list, they can find it quickly in this subset.
14. Click Next.
15. On the General Settings tab, set up how recommendations display, and select a default strategy.  
    
    Note: If you selected recommendations as a type of guidance to show in the component, then this screen appears.
    
    You can show a maximum of 4 recommendations. Maria sets the maximum to 2. She selects a default strategy, for example, Offer strategy (Global).
16. Click the Strategy Settings tab, and select object-specific strategies that override the default strategy on those record pages. For example, Maria selects the object-specific strategy for case pages, Offer strategy (Case).
17. Click Save.
18. Click Close.

Next, Maria adds the Actions & Recommendations component to record pages, and selects her deployment.

You can add the Actions & Recommendations component to Lightning console and standard navigation pages for supported objects. Most record pages are supported. For the exceptions, see the Salesforce Flow for Service Developer Guide (English only).

1. From the App Launcher, find and select a supported object, for example, Cases.
2. Open a Case record page.
3. Click and select Edit Page to launch the Lightning App Builder.
4. Drag the Actions & Recommendations component to a page location. In Service Console, we recommend the left sidebar.
5. Select a deployment in component properties.  
   
   Note: If you don’t select a deployment, agents see an empty list when they click Add.
   
   
6. To save the component configuration, click Save.
7. Click Activation…
8. Set your customized page as the app default for Service Console. Click Close.
9. Click Back to return to the Case record page.
10. Optionally, repeat these steps to display the component on another record page. You can reuse a deployment on multiple pages.
11. Choose Service Console from the App Launcher.

To test her call script, Maria creates a new case. Sure enough, the case opens and shows the list of steps. The Verify Caller action is at the top of the list, with a red asterisk indicating that it’s mandatory. Triage and Repair, Order Replacement, Log a Call, and Customer Feedback also appear. And when Maria clicks Recommendations, she sees the best offers from Einstein Next Best Action.

Agents can find and start a different step when they click Add.

Sometimes agents or customers pause a flow when information isn’t available to complete it. (A process automation setting controls whether users can pause flows.) The component shows if there are paused flows associated with the record. That way, agents can find and complete a paused flow quickly.

Maria thinks that Salesforce Flow for Service has the right stuff to transform the agent experience. She looks forward to sharing her call script with Roberto and her agents.

Before we begin, let’s install an unmanaged package in your Trailhead Playground.

If you see a tab in your org labeled Install a Package, great! Follow the steps below. If not, from the App Launcher () find and select Playground Starter and follow the steps. If you don’t see the Playground Starter app, copy this AppExchange link and check out Install a Package or App to Complete a Trailhead Challenge on Trailhead Help.

1. Click the Install a Package tab.
2. Paste 04t3i000002nHAuAAM into the field.
3. Click Install.
4. Select Install for Admins Only, then click Install.