In order to create an Agentless send, you’ll first need to create a Logic+ flow. Within Logic+, you’ll be able to design a flow that sends an SMS, Email, or Calls-to-IVR without agent intervention. Don’t worry, it’s as easy as making the panel for your communication type.
Once created, you’ll assign your Logic+ flow to a campaign stage. Select one of the options below to jump to the appropriate section.
...
To get started on your agentless send, you’ll need to navigate to Admin > Configuration > Logic+. Then, click “Add New Logic.”
...
Once you are in your new Logic+ flow, you have the ability to create a new flow through the UI Panels or via JSON editing. For the purposes of this guide, we’ll be using the panels, but you can toggle your view at any time by using the Panels or JSON icons at the top of your editor.
...
...
Available Variables
OmniOut will pass the following variables to Logic+
Before we start adding in our panels, let’s call out the variables you have at your disposal. Many of these will not be necessary to use as part of your flow—they’re just listed here for full transparency. The green highlights are for commonly used variables.
Field Name | Sample Value |
|---|---|
$.(type) |
|
$.(status) |
|
$.(date) |
|
$.(campaignMemberId) |
|
$.(id) |
|
$.(accountID) |
|
$.(city) |
|
$.(state) |
|
$.(zip) |
|
$.(country) |
|
$.(firstName) |
|
$.(lastName) |
|
$.(fullName) |
|
$.(title) |
|
$.(email) |
|
$.(companyName) |
|
$.(recordOwnerId) |
|
$.(phone) |
|
$.(website) |
|
$.(callbackDatetime) |
|
$.(importedQTime) |
|
You can use as many (or as littlefew) of these variables as necessary for within the panels of your campaign, you just need to set them at the beginning of the flow.
Click the “Set Variable” Panel
...
This will give you a blank “Set Variable” panel.
Give your panel a quick name (for your reference later) by using the “Panel Name” field at the top of the panel. Then, use the “Variable Name” field to set the variable you’d like to use later. .
Creating an SMS Panel
In this example, we
...
Again, use the Variable Table above to determine which variables you’d like to set for your particular flow.
...
the variable to “Expression”
the Function as JSON Path
Field One as $(member).
The only field that changes for variables passed to Logic+ from OmniOut, is Field Two. Here, you enter the appropriate variable from the table above.
| Tip |
|---|
Variable 1: So, if we want to set a phone number as a variable, we’ll select “Expression,” JSON Path as the Function, Field One as “$(member),” and “$.phone” as Field Two. (See example below). |
| Tip |
|---|
Variable 2: One more example we will use is the First Name of our contact. Again, we’ll select the “Set Variable” Panel, then set the Panel Name to something recognizable for us later. Then, we’ll set the Variable Name to firstname, we’ll select “Expression” as the Variable type, JSON Path as the Function, Field One as “$(member),” and “$.firstName” as Field Two. (See example below) |
Use this method to create additional variable panels (you can always come back and set more later).
Connecting Logic+ Panels
Now, you’ll need to connect your panels to each other to make a basic flow. Choose one of your panels as the “Flow Initiator.” This can be seen in the upper-right corner of any panel and designates this panel as the “beginning” of your flow. In this case, we’ll use the “Phone Number” Panel as the initiator.
...
You can connect your panels by using the Exits Section of the Panel. From the “Phone Number” Panel, we’ll select the “First Name” Panel — letting Logic+ know that the flow should progress from “Phone Number” to “First Name.” Once selected, you’ll see a pathway form between the two panels.
...
Creating an SMS Panel
are going to use the $(email) and $(firstName) variables from the list above.
Click the Create Panel button, then select Send SMS. Just like before, you’ll
...
You’ll need to provide a Panel Name. In the example below, we’ll designate this panel as an Appointment Reminder.
...
Field Name | Description | ||
|---|---|---|---|
Recipient | For the Recipient you’ll use the variable you set above. Call to a variable using the $(variablename) format. It’s important to type the variable name exactly as you typed it in the Set Variable panel. If you followed this guide, you’ll use the number variable of “$You’ll use the number variable of “$(number)” - This means that the recipient is whatever phone number is passed from OmniOut. 👍 | ||
Sender | For the Sender field, you must use an inbound route that is listed under Admin > Configuration > Inbound Routes.
| ||
Content | This is the body of your message. You can also call to set variables use the variables listed above in this message body. For Example: This is a courtesy reminder that you have an appointment coming up tomorrow. If you need to reschedule, please respond to this message or call our offices at 317.123.4567. Have a great day and see you soon.” |
...
Once you’ve set your SMS Panel, be sure to connect it to the rest of your flow by choosing your new SMS panel as an Exit from one of your previous panels. In this example, we’ll select the Appointment Reminder MSG panel as an exit for First Name. Just like before, we’ll see a connector line appear between the two panels.
...
| Info |
|---|
At this point, you have a functioning agentless flow! (Easy, right?) You’ve set variables and used them to create an SMS panel. You If this is the only action you want to take for the flow, you can skip to the OmniOut Action section if you’d like. Continue on if you want to see examples for email and Logic ClassicVoice Panels Logic. We this will also show you how to connect multiple panels. |
Creating an Email Panel
In this case, we are going to use the $(email) variable.
Just like before, we’ll navigate back to the New Panel button and select Send Email. This will feel like fairly familiar territory at this point. But, based on what we saw from SMS, we’ll likely need a new variable, the email address for the recipient. Create a new Set Variable panel for the “$.email” variable.
...
...
Email-Specific Fields
Field Name | Description | ||
|---|---|---|---|
Recipient Email | For the Recipient you’ll use the “$(email)” variable set above. This means that the recipient is whatever phone number is passed from OmniOut. | ||
Sender Name | Enter the friendly name you want to use for your email. (e.g. Sharpen Customer Support) | ||
Sender Email | This is the email you’ll use to send the email. (e.g. support@sharpencx.com)
| ||
Subject | The subject line of your email | ||
Body | This is the body of your email message. This field supports HTML markup if you want to add some flair to your message. You can use an HTML markup tool like https://html-online.com/editor/ if you need to create a message and output the HTML. For Example: |
Here is what our example looks like when filled out:
...
...
Connecting Logic+ Panels
Now, you’ll need to connect your panels to each other to make a basic flow. Choose one of your panels as the “Flow Initiator.” This can be seen in the upper-right corner of any panel and designates this panel as the “beginning” of your flow. In this case, we’ll use the SMS Panel as the initiator.
...
You can connect your panels by using the Exits Section of the Panel. From Exits in the SMS Panel, we’ll select the Email Panel — letting Logic+ know that the flow should progress from the SMS Panel to the Email Panel. Once selected, you’ll see a pathway form between the two panels.
...
Creating an Outbound Voice Panel
Our final agentless option is to place an outbound call that goes to an Auto Attendant (Logic Classic). This option allows you to place bulk outbound calls to an auto attendant for Self-Service, to play a voice prompt to a user, etc.
...
Field Name | Description | ||
|---|---|---|---|
Recipient Number | For the Recipient Number you’ll use the variable you set same $(phone) variable from above. If you followed this guide, you’ll use the number variable of “$(number)” - This Again, this means that the recipient is whatever phone number is passed from OmniOut. 👍 | ||
CallerID Number | For the CallerID field, you must use an inbound route that is listed under Admin > Configuration > Inbound Routes.
| ||
Transfer Number | This refers to the inbound route pointed to a Logic Classic flow. Think of this as the number you are using to transfer the caller to your logic classic. Please search this knowledgebase if you would like to learn more about configuring an inbound logic flow. | ||
Connection Timeout | The duration in seconds this flow will wait for a connection before timing out (and ultimately not transferring to the Logic Classic). |
Here is an example utilizing the Transfer to Logic Classic panel with the information above. Note: the Exit section of the Email Panel is now pointing to the Agentless Call Panel.
...
In the example above, we have three different agentless actions taking place. The contact would receive an SMS reminder, an email reminder, and receive a call that would point towards a Logic Classic prompt. This was more for illustrative purposes than anythinganything—just to show you the flexibility of the different panels.
We’d recommend you don’t have so many communication layers in a single flow as they’ll happen simultaneously. Generally, try to take a “less is more” approach and create different Logic+ flows as they meet your needs.
...
This will load a second drop down labeled “Logic ID.” Select your agentless Logic+ flow from this drop down menu. If you do not see Agentless within the drop down or are unable to save your agentless step, make sure the LogicID field has been added to the FathomSASFCampaignsStatus table.
Since an agentless interaction can’t have dynamic dispositions, the outcome of your agentless step for SMS and Email will be the default disposition for your campaign. Ensure that the default disposition routes to the appropriate OmniOut stage (likely the next stage).
...