Overview

Custom Alerts are configurable emails that can be set-up in order to send unique messages for certain situations. Alerts are attached to events. Events in the system represent situations such as:

• An order has been imported
• Pricing and/or quantity is being updated
• Routing has completed

During events such as these, it's possible to create a custom alert to send at the time these events occur.

Before You Get Started

Optional email connections can be set-up to modify the email address that the alert comes from.

For example, if a Flxpoint user would like to send an "Order Received" alert to their B2B customers from their own email address, an email connection can be configured for an email such as example@example.com.

If this connection is chosen, then the custom alert will come from example@example.com. If no email connection is created, the email will be sent from no-reply@flxpoint.com.

The no-reply@flxpoint.com inbox cannot be monitored for sent or received emails.

If you would like to monitor or communicate with the alert recipients, we recommend creating a new email connection.

Instructions & Tutorial

Events

Events dictate the data available within each custom alert.

For example, if you choose an Order Import event, you will have access to order metadata (i.e. order #, shipping address info, etc.). If you choose a Fulfillment Request/fulfillment orders event, you will have access to FR/FO metadata.

To create a custom alert, you must choose an event to associate that custom alert with in order to properly build your alert with dynamic data.

Body Syntax

The most important part of a custom alert is the actual email body that is sent.

Each event will have a different set of data that can be leveraged within the alert. This different data is distinguished by placeholders. Placeholders represent values that you can add to a custom alert to inject a real-time value into the alert.

Take the following example:

The above list represents placeholder values that can be used within an Order Import custom alert.

The above body text represents an example where a custom alert is using the shipping address fields to put into an alert.

By using the above syntax, the custom alert would appear similar to what you see above.

Leveraging these placeholder values, you can create dynamic alerts and messages that provide detailed information around the alert you are configuring.

Applying a Custom Alert

To use a custom alert, you must incorporate it as an action within a workflow rule.

For example, if you'd like to receive a custom alert for international orders, you can configure an order import workflow rule that looks similar to the following:

Within each workflow, you will be able to select custom alerts that are relevant to that event.

Events and workflows are directly tied to one another. When you select a specific event, you will only be able to apply the custom alert in the matching workflow.

For example, if you create an order import custom alert, this alert can only be used within the order importing workflow.