The Revenue Recovery feature gives you another chance at revenue when a call's connection to a target ends too soon to convert, such as when an agent drops the call. If you enable this feature, Ringba routes these calls to a different eligible target to take another try at converting.

This article contains the following sections:

• Revenue Recovery
• How to Enable Revenue Recovery on a Campaign
• How to Enable Revenue Recovery on a Buyer, Target, or Ring Tree Target
• Revenue Recovery FAQ

Revenue Recovery

Sometimes a call connects with a target for too little time for a conversion to occur. When this happens, you might like to connect the call with a different eligible target to try to complete the conversion. The Revenue Recovery feature lets you reroute calls that the target ended too early.

Note: Revenue recovery only works when the call is ended by the Target. If the caller ends the call, there is no opportunity to recover revenue because the caller has disconnected.

When you configure Revenue Recovery, you enter how long a call must stay connected.

If the target ends the call in less time than the threshold you set, the caller hears the call ringing again while Ringba routes the call to the next eligible target. If the next target also ends the call too early, Ringba can continue trying more targets. You specify how many attempts, up to a maximum of 5, Ringba should make when you configure the feature.

You can also set a number of Reroute Attempts at the Buyer, Target, or Ring Tree Target level. This number indicates how many previous connections the call can have and the Target will still accept it. For example, if you set a Buyer's Reroute Attempts field to 2, then that Buyer's Targets and RTTs will accept only calls that have been previously connected 2 times before, even if the Campaign is set to 5 Reroute Attempts.

Conversely, if any Buyers, Targets, or RTTs on a Campaign will accept rerouted calls, Ringba will reroute calls to them, even if Revenue Recovery is disabled on the Campaign.

Example 1

You enable Revenue Recovery for your Campaign and set a connection threshold of 10 seconds. A call comes in through that Campaign and connects to a target. However, the agent dropped the call after 8 seconds of silence. Since the connection lasted less time than the threshold you set, Ringba reroutes the call to another eligible target to try to convert it.

Example 2

You enable Revenue Recovery for your Campaign and set a connection threshold of 15 seconds. A call comes in through that Campaign and connects to a target. However, the target does not have agents available to take the call so plays a short automated message saying, "We have no agents available at the moment" and hangs up after 12 seconds. Since the connection lasted less time than the threshold you set, Ringba reroute the call. The caller hears another ring tone after the recording and stays on the line to talk to the next target.

How to Enable Revenue Recovery on a Campaign

Use the following steps to enable Revenue Recovery on your Campaign:

1. Click Campaigns in the left navigation menu to open the Campaigns screen.
2. Open the Campaign where you want to add Revenue Recovery. The campaign appears with the Campaign Settings tab open by default.
3. Scroll down to the Revenue Recovery switch near the bottom of the General Info section and toggle it on. Fields appear for you to configure the feature.
4. (Optional) Enter a number of seconds in the Connection Threshold To Reroute field. This value is 10 seconds by default.
5. (Optional) Enter the maximum number of attempts Ringba makes to reroute a call in the Reroute Attempts field. This value is 2 retries by default. The maximum number you can enter is 5.

How to Enable Revenue Recovery on a Buyer, Target, or Ring Tree Target

In addition to configuring Revenue Recovery on a Campaign, you can also configure the same fields at the Buyer, Target, or Ring Tree Target (RTT) level. If you configure at the Buyer level, the system honors the configurations you set for all Targets and RTTs associated with that Buyer. If you configure at the Target or RTT level, the system honors the configurations for that specific Target or RTT.

See the How does Ringba decide which values to use if I configure Revenue Recovery at the Campaign, Buyer, Target, and RTT levels? question in the standalone Revenue Recovery FAQ for more information on how these configurations interact with each other.

Revenue Recovery FAQ

Can I reroute if the call was disconnected by the caller?

No, the reroute only happens if it was disconnected by the buyer.

How do the rerouted calls appear in Reporting?

Calls rerouted as part of Revenue Recovery appear as events in Reporting. You can see that the rerouting occurred. Rerouting generates another call with another recording.

In addition to these questions, we also have a dedicated Revenue Recovery FAQ article.