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.
...
To get started on your agentless send, you’ll need to navigate to Admin > Configuration > Logic+. Then, click “Add New Logic.”
...
Field Name | Description | ||
|---|---|---|---|
Recipient | 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 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.” |
...
Field Name | Description | ||
|---|---|---|---|
Recipient Number | For the Recipient Number you’ll use the same $(phone) variable from above. 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). |
...
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.
| Expand | ||
|---|---|---|
| ||
The FathomSASFCampaignsStatus table can be found in SharpenTables  |
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).
...