...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Note |
|---|
This article is part of a larger series in creating a campaign in OmniOut. If you haven’t created a campaign (or don’t have a campaign in which you want to add an agentless step), we recommend starting at the campaign-level first. Said differently, you will not be able to actually send an agentless interaction without linking it to a campaign. |
In order to create an Agentless send for your OmniOut campaign, 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 “$(numberphone)” - 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.” |
...
| Info |
|---|
At this point, you have a functioning agentless flow! (Easy, right?) You’ve set variables and used them to create an SMS panel. 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 Voice Panels Logic. We this will also show you how to connect multiple panels. |
...
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 email 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 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).
...