| Note |
|---|
A prerequisite to this step is that all of the prior sections have been completed. |
...
Now that your campaign and contact data is prepared, it is time to begin building your cadence within the OmniOut Tool.
Navigate to Admin > Configuration > OmniOut. Then, select SharpenDB (or SharpenTables for legacy campaigns) from the Campaign Source drop down. Click on the Next button.
...
Select the campaign list you want to configure from the Campaign drop down. Click the Next button.
...
| Warning |
|---|
Your SharpenDB2 campaign table can only be linked with one campaign at a time. If you need to assign the table link to another campaign, please reach out to SharpenCare. |
Scheduling
Select the Days of the week, the time zone, and the hours in which the campaign should run. If you have contacts in different timezones and want to reach out based on the local time, check out this article.
...
Status | All campaign statuses created within your data source will show up here. If a campaign stage or disposition option is missing, head back to Salesforce or Tables (depending on your source), make the change, and refresh OmniOut. |
Points | Points allow you to weight interactions within the Outbound Queue. Generally, you want later stages of the cadence (e.g. Call 5) to take priority over a new, 1st touchpoint. Otherwise, new prospects to the cadence would make it impossible to work through your previous prospects. |
Action | The action designates the type of interaction presented to the rep. In this case, the first touchpoint is a call, so the action will present as a “phone call.” This doesn’t limit the agent from another interaction type—it just serves as a reminder as they navigate dozens of cadences on different durations. Options for Actions are:
|
Edit |
The script is similar to Q Scripts in that you can surface scripts to the agent specific to the cadence touch point. For example, if you always want a specific voicemail on the 3rd contact, or specific email templates, you can enter them here. For more information on scripts, click here. |
Delay | Delay/Delay Unit = The amount of time that will pass from the time the interaction enters this status before triggering the interaction in the queue. Typically the first stage of a campaign/cadence would not have a delay.
Note: It is important to select the correct delay unit. If the desire is for a stage to happen 2 hours from now then select 2 hours...do not select 120 minutes.
|
End Results / Dispositions | To the right of the Delay Method field in the campaign stage there are selection boxes for each end result/disposition. As mentioned in a previous step, if these End Results and Dispositions do not match what you’d want to use, they can be modified withinSharpen Tables > FathomSASFCampaignsStatus under “structure” (even if you aren’t using SFDC as your data source). If this seems daunting, we would recommend reaching out to your Client Success manager, we are happy to help. For each end result/disposition, it is necessary to select the next campaign stage for the interaction if that disposition is selected by the agent when completing the interaction associated with this stage.  |
...
Queue | All available queues will display within this dropdown. Ensure you select the appropriate outbound queue for this agent and this campaign. If you want to route all of “Adam’s” leads to “Adam” — choose a queue that only Adam will access, like a MyQ. If the leads do not need to be delivered to a specific person, you can route the interactions to a group queue (like “Sales”) so that leads are handled by any agent as they become available. |
Calling Method | This determines how you'd like the agents to proceed through the campaign.
|
...