This article answers the common questions asked about Targets.
This article contains the following sections:
- How can I send button pushes to a target that requires using their IVR to connect to an agent?
- How does the Priority Bump slider work?
- Why isn't my target receiving calls even after I reset caps?
- What should I do if I still need help with targets?
How can I send button pushes to a target that requires using their IVR to connect to an agent?
You can use the Dial IVR field that appears near the top of the screen when you create a target. Here you indicate the IVR input you need to send to the target to get connected to an agent.
In this field, you can enter:
- Numbers: If you type a 3 in this field, Ringba send the tone for the 3 key to the target.
- w: A lowercase w tells Ringba to wait 0.5 seconds. You can use this before entering numbers or in between numbers. You can place multiple lowercase w's together to create a longer waiting time.
- a reference to a tag with a numerical value: If you refer to a tag with a numerical value, Ringba gets the tag value and sends the tones that correspond to the digits in the value. For example, if you enter [tag:gather:zipcode], Ringba gets the value of the zipcode gather tag. If the value is 12345, Ringba sends the tones for each digit in order.
How does the Priority Bump slider work?
When you configure the Predictive Routing Settings on a target, you can set a value between -10 and 10 on the Priority Bump slider. This tool lets you manually affect the target's ranking in the predictive routing engine when you want a target to receive more or fewer calls.
The predictive routing engine considers many components, and its exact calculations are proprietary, so the exact mathematical effect of choosing a value on this slider is not available. However, this table contains a rough estimate of the effect on the target's conversion rate of choosing each value on the slider:
| Value | Amount Subtracted from Target's Conversion Rate | Slider Value | Amount Added to Target's Conversion Rate |
|---|---|---|---|
| -10 | -99.9% | 10 | +100% |
| -9 | -72.9% | 9 | +72.9% |
| -8 | -51.2% | 8 | +51.2% |
| -7 | -34.3% | 7 | +34.3% |
| -6 | -21.6% | 6 | +21.6% |
| -5 | -12.5% | 5 | +12.5% |
| -4 | -6.4% | 4 | +6.4% |
| -3 | -2.7% | 3 | +2.7% |
| -2 | -0.8% | 2 | +0.8% |
| -1 | -0.1% | 1 | +0.1% |
Why isn't my target receiving calls even after I reset caps?
If your target has a buyer, the buyer's call caps also apply to the target. If your target still isn't receiving calls after you reset the target's cap, check the related buyer to see if it is capped.
Resetting the caps on the buyer does not affect the buyer's targets' caps. Likewise, resetting the target's caps does not affect the related buyer's caps. So you have to check both levels of caps individually.
What should I do if I still need help with targets?
If you have any questions or need additional help, please reach out to our support team via chat or email at support@ringba.com.