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.
...
To get started on your agentless send, you’ll need to navigate to Admin > Configuration > Logic+. Then, click “Add New Logic.”
...
| Info |
|---|
Again, use the Variable Table above to determine which variables you’d like to set for your particular flow. For variable from OmniOut, you will always set:
|
...
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 “$(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 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.” |
...
| Info |
|---|
At this point, you have a functioning agentless flow! You’ve set variables and used them to create an SMS panel. You can skip to OmniOut Action section if you’d like. Continue on if you want to see examples for email and Logic Classic. |
Creating an Email Panel
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.
...
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: |
...
Field Name | Description | ||
|---|---|---|---|
Recipient Number | For the Recipient Number you’ll use the variable you set above. If you followed this guide, you’ll use the number variable of “$(number)” - 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). |
...
| Info |
|---|
Note: If you do not already have an agentless Logic+ flow created, save your campaign, open a new tab in your browser, and navigate to Admin > Configuration > Logic+. |
...
This page is also part of the larger setup document for OmniOut (Salesforce). If you’re following the guide here are some related links:
Creating an Agentless Flow as Part of an OmniOut Campaign (you are here)