Transferred = Qualified: When to Pay on Transfers
Some pay-per-call buyers do not need anyone to listen to a call to decide whether it was good. If their intake team takes the call once it is transferred, the transfer itself is the signal. Deciding when to pay on transfers, and setting the rule up so it matches what the buyer actually accepts, saves networks and buyers a lot of back-and-forth. This guide covers when a "transferred = qualified" rule fits, when it does not, and how to set it up step by step.
What "transferred = qualified" means
In a typical pay-per-call flow, a caller reaches a tracking number, may go through a short screen (an IVR menu or a live screener), and is then transferred to a buyer. Under a transferred = qualified rule, every call that reaches the buyer counts as a good call, usually with a minimum length so instant hang-ups after the transfer do not count.
The decision is made by your call platform's own data: a transferred, connected, converted or payout field, or the name of the buyer the call was sent to. No recording, transcript or review of what was said is needed.
When it makes sense to pay on transfers
Paying on transfers works best when the screening has already happened before the transfer. Common signs it fits:
- The buyer screens on their side. An intake team that asks its own questions and decides whether to sign a case often prefers to pay for the chance to talk to the caller, and judge quality later in its own pipeline. SSDI intake is a common example.
- There is a screen before the transfer. An IVR or live screener filters out wrong numbers and out-of-area callers, so a transfer already means the caller passed basic checks.
- Recordings are not available. If the platform does not send a recording link for a campaign, an AI check on the conversation is not possible, and the transfer is the most reliable signal you have.
This is general information about structuring call campaigns, not legal or compliance advice. SSDI, legal and insurance campaigns have their own rules; check them with your own counsel.
When paying on transfers is the wrong rule
A transfer only tells you the call reached the buyer. It says nothing about what was said next. A transfer-only rule is a poor fit when:
- The buyer pays only for callers who meet criteria. Home ownership, age, state, an active need: if the buyer will reject calls that fail these, the rule needs to check the conversation, not just the transfer.
- Transfers happen with no screen. If every inbound call is sent straight to the buyer, "transferred" means "called", and wrong numbers and job seekers get paid like real callers.
- Disputes are already common. If buyers regularly push back on paid calls, a transfer flag will not end the argument. Evidence from the call will.
Many networks run both kinds of rule. Our pay-per-call networks page explains how to run several campaigns with different rules side by side.
Set a minimum length after the transfer
A transfer followed by a five-second hang-up is rarely a call anyone wants to pay for. Most transfer agreements add a minimum length, often called a buffer. Keep these points in mind:
- Agree on which clock counts. Total call length includes time in the IVR or with a screener. Connected time with the buyer can be shorter. Write down which one your buffer uses.
- Do not treat length as quality. A minimum length filters out the worst calls, but a long call is not always a good one. We cover this in why call duration isn't call quality, and how to pick a number in setting a pay-per-call buffer.
Here is an illustration, not a benchmark: a buyer agrees to pay on any transfer that lasts at least 60 seconds. A call transferred after 40 seconds in the IVR, which then stays with the buyer for 30 seconds, passes on total length (70 seconds) but fails on connected time (30 seconds). That is why the clock has to be agreed in writing.
Pick the field that really means "transferred"
Call platforms label transfers in different ways. Depending on the platform and setup, the signal may be a yes/no field such as transferred, connected or converted, a buyer or target name, a connected duration, or a payout or revenue amount. Before you trust a field:
- Open a few recent calls you know were transferred and a few you know were not.
- Find a field that is filled on the first group and empty, zero or false on the second.
- Avoid fields that are always filled, such as a default target or a campaign name.
- Re-check after any change to routing, buyers or IVR, since a new setup can change which fields are sent.
How to set up a transferred = qualified rule, step by step
Step 1: Write the rule with the buyer
Put it in one sentence: "A call counts when it is transferred to the buyer and stays connected at least N seconds." Note the clock and any exclusions, such as repeat callers within a set window.
Step 2: Confirm the transfer field
Use the checks above to confirm which field your platform sends for a transfer.
Step 3: Test on past calls
Apply the rule to the last few weeks of calls and compare the result with what the buyer actually paid for.
Step 4: Share the same view with both sides
Buyers and publishers should see the same verdict and reason for each call.
Step 5: Track cost per qualified call by source
A transfer rule makes counting easy, but the question that matters is still which publishers and campaigns bring calls the buyer keeps. Review cost per qualified call by publisher every week.
How Tagloud handles transferred = qualified
In Tagloud, each campaign has a choice: an AI check against your own qualification rules, or "transferred = qualified". In transfer mode, Tagloud reads the call data that CallGrid, Ringba or Retreaver already sends (by webhook or API, with an hourly auto-import) and marks each call qualified or not, with the reason, such as the field that showed the transfer and the buyer it went to. You can set a minimum length after transfer and pick which field means "transferred", or let Tagloud detect it from buyer, connected, converted or payout fields. Saving the setting re-checks the calls already in the campaign. Each verdict then rolls up into publisher grades and cost per qualified call, and can be sent to your own systems with the result webhook. See all supported integrations.
FAQ
Is a transferred call the same as a qualified call?
Only if the buyer agrees it is. Under a transferred = qualified rule, reaching the buyer for at least the agreed minimum length is the definition of a good call. Buyers who pay only for callers meeting criteria need a check on the conversation instead.
Do I need call recordings to pay on transfers?
No. The decision uses the transfer, buyer, connected or payout data your call platform sends, so it works even when recordings are off.
What minimum length should a transfer have?
There is no standard number. Agree on one with the buyer, write down whether it counts total or connected time, and review it if disputes keep coming up.
Can I use transfer rules for some buyers and AI checks for others?
Yes. Set the rule per campaign, so buyers who screen on their side can pay on transfers while buyers with strict criteria get calls checked against their rules.
Try it on your own calls. 7 days and 100 analyzed calls free, no card needed. Connect CallGrid, Ringba or Retreaver in about 5 minutes.