Ringba makes it easy to integrate with Jornaya's TCPA Guardian. This tool lets you pull information about which callers provided TCPA consent, which helps you avoid non-compliant calls and mitigates the risk of TCPA litigation by having proof of consent.
There are two versions of the Jornaya integration. If you are using real-time bidding, instead of this article you should see the Jornaya Integration - RTB version article for step-by-step instructions on using Jornaya with real-time bidding.
If you are routing calls in a static way that doesn't involve dynamic bidding, you should use this article about the call flows version of the integration. A call flow is a decision tree you build to control how Ringba processes the calls that come in to your account.
To enable this integration, you should first review the Call Flows with Ringba article for step-by-step instructions on creating a call flow and adding it to your campaign. You add the Jornaya Node to your call flow to instruct Ringba to ping TCPA Guardian for information before dialing a target to connect the call.
In this example, Ringba pings TCPA Guardian as soon as the call comes in. The result of that ping determines the next step:
- If Jornaya says the call is allowed, then Ringba uses the Dial node to connect the call to a target.
- If the Jornaya says the call should be blocked, Ringba plays a short message telling the caller the call was blocked and then hangs up.
- If the Jornaya ping fails for any reason, Ringba simply hangs up.
You can use a call flow like this or customize it to match your own process. See the Jornaya Node article for step-by-step instructions on using and configuring this node.