Create an Automated Abandoned Cart Email

Administrators can set up Salesforce automation tools to send an abandoned cart email to constituents who leave an item(s) in their cart for a given number of days, without checking out.

Recipe Prep

Keep these things in mind:

You are using Community Hub in your org.

You are not using cash billing in your org (see note at the bottom of the recipe).
No Community Hub carts exist that contain no products.

To make this recipe, you should understand:

Autolaunched Flows
How the Cart object is used in Community Hub.

This recipe will be even better if you understand:

Salesforce email templates
Salesforce email alerts
The Nimble Templating Framework

Ingredients

You will combine these ingredients to make this recipe:

Suggested Name	Type	Description
Abandoned Cart Check	Autolaunched Flow	The auto-launched flow receives the cart record ID from the Cart Inserted process builder and evaluates logic to determine sending a reminder email. For example: a decision would evaluate if the cart still exists and if the cart creator is a constituent of Community Hub. If so, the decision would send an email, if not, no email would be sent.
Abandoned Cart Alert	Email Alert	The alert is configured to send from an organization-wide email address to the constituent who created the Community Hub cart and abandoned it.

Directions

You can follow these directions to make this recipe in your org:

Create the email template.
Create the email alert:
1. Select Cart as the object for the Email Alert.
2. Select the template you created
3. Select User as the recipient type and select Record Creator as the selected recipients.
4. Select your preferred organization-wide email address as the email's "from address".
Create the auto-launching flow:
1. Create a variable resource called CartId with the following details:
  1. Data Type is Text
  2. Input and Output is Input Only.
  1. Lookup is NU__Cart__c
  2. Field is Id
  3. Operator is equals
  4. Value is CartId variable
  5. Assign the record's field to variables
    1. Field is Id
    2. Variable is CartId variable
    3. Assign null values to the variables if no records are found is TRUE
    4. Create a record lookup variable with the following details:
  1. Create an editable outcome called Yes with the following details:
    1. Resource is CartId variable.
    2. Operator is is null.
    3. Value is GlobalConstant.False (in GLOBAL CONSTANT value picklist dropdown).
    4. Create a decision variable called Cart Exists
2. Drag the email from the Palette menu onto the canvas.
  1. Mark the Lookup as the beginning step, and link to the decision element.
  2. Link the decision element to the Email Alert element, and select the Yes outcome.
  3. Connect all elements:
3. Save as an auto-launched flow, assign a name, and activate the flow.

This is one of many different ways to set up an email follow-up for abandoned carts. Given the innumerable decisions and evaluations you can configure in the Cloud Flow Designer, you can adjust the logic to execute reminders in whatever way makes sense for your association by including more decisions and more queries.

For example: you could send emails based on specific Account attributes, or based on which products are within a constituent's cart.

Feel free to tailor this recipe to fit your needs and business processes.

If you use cash billing in your org, consider reviewing the cart evaluation logic to exclude those Community Hub carts created by staff, as opposed to constituents.

For example: this could be accomplished using helper formula checkbox fields on the Cart object that return TRUE or FALSE based on the Created By user's profile name. Reference any custom field as needed in the flow to narrow the automation's focus.