Turning on a new call source is not a clerical task.

It is an operating decision.

The moment a source is enabled, a defined stream of callers may begin entering a buyer’s campaigns, targets, agent queues, qualification rules, dispute process, invoices, and reporting. A toggle can change routing in seconds, but the consequences of a weak decision may take days or weeks to understand.

That is why a serious buyer should not ask only:

Does this source look good?

The better questions are:

What exactly is the source?
How were the calls generated?
What does the consumer expect?
Which campaign and target should receive the source?
Is the buyer prepared to answer and handle the calls?
What rules determine whether the calls become billable?
What evidence will be reviewed during the test?
Who can pause the source, and how quickly?
What would justify more volume?
What would require the source to be turned off?

A buyer does not need perfect certainty before testing a new source. Perfect certainty rarely exists. The buyer does need a controlled test with a clear source definition, a narrow routing scope, known commercial rules, useful decision material, buyer-side readiness, and an agreed review process.

This guide explains what a buyer should know before turning on a new call source and how to structure the first test so that both the buyer and publisher can learn from it.

First, define what “turning on a source” actually means

In an uncontrolled operation, “turning on a source” may mean little more than giving a publisher a tracking number or activating a campaign.

That is too broad.

A publisher may operate several traffic paths that differ materially:

An owned-and-operated website.
A paid-search campaign.
A social advertising funnel.
A consumer-initiated inbound source.
A warm-transfer team.
A network of sub-publishers.
Several landing pages with different claims or calls to action.
Separate campaigns for different states, products, languages, or call types.

The buyer may be willing to test one of those sources without accepting all of them.

A useful source-enablement decision should therefore identify:

The source being reviewed.
The buyer that may receive it.
The campaign or vertical where it may participate.
The target or destination allowed to receive it.
The limits that apply during the test.
The conditions that can pause or end the test.

In a controlled model, source activation is not a blanket approval of a publisher. It is permission for one defined source to participate in one defined routing path under one defined set of rules.

For a deeper explanation of that structure, read what source enablement means in pay-per-call.

1. What exactly is the source?

A buyer cannot evaluate a source that has not been defined clearly.

“Facebook traffic,” “inbound calls,” “warm transfers,” or “publisher traffic” may be useful starting descriptions, but they are not always specific enough to support routing, reporting, or accountability.

Before enabling the source, the buyer should know:

Who controls the traffic path.
Whether the traffic is direct or aggregated.
Whether outside sub-publishers are involved.
Which domain, landing page, phone number, campaign, transfer floor, or call center is associated with it.
Which vertical and offer the source promotes.
Which geographies the source targets.
Whether the calls are consumer-initiated inbounds, transfers, or another defined call type.
Which source label will appear in routing and reporting records.
What changes would cause the source to require another review.

The source definition should be narrow enough that performance can be attributed to it.

If several materially different traffic paths share one label, the buyer may not be able to tell which part of the supply created a quality problem, compliance question, dispute pattern, or performance improvement.

Suppose a publisher operates:

Direct paid-search inbounds.
Warm transfers from its own agents.
Aggregated transfers from outside partners.

Those sources may have different caller expectations, scripts, complaint risks, connection rates, conversion patterns, and settlement issues. Combining them under one generic source label may create a blended report that is not useful for deciding what to scale.

A well-defined source protects the buyer, but it can also protect the publisher. If one traffic path underperforms, the operator can isolate that source instead of treating every call from the publisher as the same.

2. What did the consumer experience before the call?

A call is easier to evaluate when the buyer understands the consumer journey that produced it.

The buyer should know what the consumer saw, heard, clicked, submitted, or agreed to before reaching the destination.

For consumer-initiated inbound traffic, useful review material may include:

The advertisement or creative.
The landing page.
The call-to-action language.
The business or service identified to the consumer.
The phone number displayed.
The form fields, if a form is involved.
The geographic and product language.
Any qualifying questions shown before the call.
The disclosures and consent language relevant to the traffic path.
The steps between the advertisement and the phone call.

For transferred calls, useful review material may include:

The transfer script.
A description of the upstream conversation.
The questions asked before transfer.
The consumer’s stated reason for calling.
Whether the transfer is blind, warm, or otherwise structured.
The business or party identified before handoff.
Sample calls when appropriate and lawfully available.
What happens when the buyer does not answer.
Whether the upstream agent remains on the line.
The states, products, and eligibility topics the transfer team discusses.

The buyer should not assume that “inbound” automatically means the consumer understood the destination. A consumer can initiate a call after seeing vague, misleading, outdated, or poorly matched advertising. A transfer can arrive with strong intent, or it can arrive after an upstream interaction that created confusion.

The important question is not merely who dialed.

It is:

What did the consumer reasonably expect to happen next?

The answer should match the buyer’s offer, agents, script, licensing or authorization requirements, and call-handling process.

For a fuller comparison, see consumer-initiated inbound calls versus transfers.

3. Has the source been reviewed for the actual campaign?

A source can be legitimate and still be wrong for a particular campaign.

Before activation, the buyer should compare the source against the campaign’s actual requirements:

Vertical.
Product.
Geography.
Language.
Caller age or eligibility requirements, where applicable.
Call type.
Business hours.
Accepted consumer intent.
Required questions or exclusions.
Minimum qualification event.
Duplicate policy.
Buyer price.
Dispute rights.
Recording requirements.
Conversion-reporting requirements.
Licensing, authorization, or appointment constraints.

A general publisher approval does not answer those questions.

A source may have performed well in one vertical but be inappropriate for another. A buyer may accept consumer-initiated inbounds but not transfers. A licensed sales team may cover a broader geography than a smaller target. A campaign may require a specific consumer action that the source does not reliably create.

The review should connect the source to the exact campaign rules that will govern the calls.

That comparison should also identify any unresolved issue. An unresolved issue does not always require rejecting the source. It may require a narrower test, a lower cap, selected states, an experienced-agent target, additional documentation, or a temporary hold until the question is answered.

The goal is not to approve traffic quickly.

The goal is to know what has been approved.

4. Which campaign and target should receive the source?

A buyer-wide “on” switch is often too broad.

The buyer may operate several destinations with different:

Agent experience.
State coverage.
Product knowledge.
Language capabilities.
Hours.
Concurrency.
Transfer-handling ability.
Close rates.
QA maturity.
Technology.
Scripts.
Capacity.

A new source should begin in the target most capable of handling it.

For example, a buyer may have:

Target A: Experienced agents who handle transferred callers and cover a broad set of states.
Target B: Newer agents who handle only consumer-initiated inbounds in a smaller licensed footprint.
Target C: An overflow center used only when the primary team is full.

A new transfer source may be appropriate for Target A and inappropriate for Targets B and C.

Turning the source on for the buyer as a whole can create a false test. Calls may reach the wrong team, fail for buyer-side reasons, and then be blamed on the source.

A better test defines:

The campaign.
The target.
The accepted states.
The schedule.
The call type.
The cap.
The concurrency limit.
The fallback or overflow behavior.
Whether another target may receive the source if the primary target is unavailable.

This is why buyers should not have to accept every source by default. Source-level and target-level control lets the buyer say:

Yes, but only here, under these conditions.

5. Is the buyer operationally ready?

A new source test evaluates both the source and the buyer.

Buyers sometimes treat performance as though it were created entirely upstream. It is not.

The buyer’s operation affects:

Answer rate.
Speed to answer.
Abandonment.
Conversation length.
Qualification.
Conversion.
Consumer experience.
Agent disposition accuracy.
Duplicate identification.
Recording availability.
Dispute volume.
Source-level reporting.

Before the source goes live, the buyer should confirm:

Staffing

Are enough agents scheduled?
Does the team understand the expected volume?
Are experienced agents available during the first test?
Can the buyer absorb a spike without excessive hold time?
Is there a plan for breaks, meetings, and shift changes?

Training

Do agents know the source’s call type?
Do they know what the consumer was told?
Are transfer handoffs explained?
Are expected objections known?
Does the script match the source and offer?
Do agents understand how to disposition the call?

Technology

Is the destination working?
Are IVR and queue rules correct?
Are recordings functioning where lawful and required?
Are call events and dispositions being captured?
Can the buyer identify the source in reports?
Can the source be paused quickly?

Capacity

What is the real answerable capacity?
What cap protects the team during the test?
What happens when concurrency is full?
Does overflow preserve the intended consumer experience?
Are hours and time zones configured correctly?

A buyer that is not ready can make a strong source look weak.

If the first test is important, do not route it into an understaffed queue and then treat low conversion as a source verdict.

For more detail on operational limits, see how caps, schedules, and concurrency shape call flow.

6. What evidence supports the decision to test?

New sources usually begin with incomplete evidence.

That is normal.

The buyer may have access to:

Publisher-reported history.
Operator-reviewed source information.
Sample recordings.
Creatives and landing pages.
Transfer scripts.
Expected volume.
Expected geographies.
Prior performance in another campaign.
A benchmark.
A small number of early calls.

Those materials can justify a test, but they should not be confused with buyer-specific proof.

The buyer should label the provenance of each number:

Self-reported estimate: supplied by the publisher.
Operator-published benchmark: reviewed and published by the exchange or operator.
Cross-campaign history: performance from another context.
Buyer-specific history: the buyer’s own results.
Live computed metric: calculated from current operating records.
Small-sample observation: early data that may not be stable.

A metric without provenance is easy to overvalue.

For example, “25% conversion” could mean:

A publisher’s estimate.
One buyer’s result.
A result from a different vertical.
A result based only on connected calls.
A result based on all routed calls.
A result from ten calls.
A result from ten thousand calls.
A result that excludes disputed calls.
A result that was never reconciled.

Those are not equivalent.

A useful pre-test benchmark should help the buyer decide what to watch and how to structure the test. It should not promise that the source will reproduce someone else’s outcome.

Read how benchmarks help new sources get buyer confidence for a more detailed framework.

7. What will count as a successful test?

A test should have decision criteria before the first call routes.

Without them, the review can become emotional:

A few good calls create premature scaling.
A few bad calls create premature rejection.
The buyer and publisher choose whichever metric supports their position.
Buyer-side failures are blended with source-side failures.
The test continues because no one knows when it is complete.

A controlled test should define:

The test window

Use a period or call count large enough to observe the source, but small enough to limit downside. The right size depends on the vertical, expected volume, buyer capacity, call type, and settlement model.

Do not invent an arbitrary universal number.

The routing scope

Specify:

Campaign.
Target.
States.
Schedule.
Cap.
Concurrency.
Call type.
Any exclusions.

The metrics

Relevant measures may include:

Offered calls.
Routed calls.
Connected calls.
Qualified calls.
Billable calls.
Converted calls.
Answer rate.
Connection rate.
Qualification rate.
Conversion rate.
Billable talk time.
Dispute rate.
Duplicate rate.
Agent disposition distribution.
Complaint or QA findings.

Do not collapse those statuses into one “good call” number.

The review questions

At the end of the test, ask:

Did the source reach the intended target?
Did the buyer answer consistently?
Did callers match the stated intent?
Did the consumer journey match the buyer’s expectations?
Were qualification rules applied consistently?
Were conversions reported on time?
Were disputes concentrated around one issue?
Did a buyer-side operational problem distort the results?
Did performance vary by state, time, agent team, or call type?
Is there enough evidence to continue, pause, change, or scale?

The possible outcomes

A test does not need to end with only “scale” or “reject.”

Possible decisions include:

Continue at the same cap.
Increase the cap slightly.
Restrict the source to selected states.
Change the schedule.
Route to a different target.
Improve agent training.
Clarify qualification rules.
Request updated creative or script material.
Pause for investigation.
Disable the source.
Re-test after a material change.

That range of decisions produces better learning than an all-or-nothing approach.

8. Are qualification, billing, payout, and dispute rules clear?

A source test should not begin with vague commercial rules.

The buyer should understand:

The buyer price.
What event makes a call billable.
Whether qualification is duration-based, CPA-based, or another defined model.
Which duration is measured.
Whether IVR, ringing, hold, or transferred time affects the rule.
How duplicates are identified.
Which exclusions apply.
How conversions are reported.
The deadline for reporting a conversion.
How disputes are submitted.
What evidence supports a dispute.
How adjustments affect invoices.
What happens when a call has incomplete data.
Whether the test has any special commercial terms.

The publisher payout is a separate amount and a separate operating concern. Buyers do not need private publisher economics, but the operation should not confuse buyer price with publisher payout.

The buyer also should not assume that routed, connected, qualified, billable, payable, converted, invoiced, and paid all mean the same thing.

Clear settlement rules improve source evaluation because they keep financial outcomes tied to defined events.

When those rules are unclear, every early call can become an argument:

The buyer says the call was not qualified.
The publisher says the caller connected.
The operator sees a long duration but cannot tell what happened.
The invoice includes a call the buyer expected to dispute.
The source appears unprofitable because conversion reporting is late.
The publisher sees rejections without usable reasons.

The source should not be turned on until the parties understand how the operating records will become financial records.

9. Has the legal and compliance review been completed?

Source review is not a compliance guarantee.

A platform toggle, application, recording, creative review, or publisher representation does not determine whether a call complies with every federal, state, vertical, contractual, licensing, privacy, recording, advertising, or consent requirement.

The buyer should identify who is responsible for reviewing:

Advertising claims.
Landing pages.
Transfer scripts.
Consumer disclosures.
Consent language.
Calling practices.
Do Not Call requirements.
Prerecorded or artificial-voice use.
Recording consent.
State-specific restrictions.
Vertical-specific requirements.
Licensing and authorization.
Record retention.
Material source changes.

The Federal Trade Commission’s Telemarketing Sales Rule compliance guide explains that the rule may apply to certain interstate telemarketing activity, including some calls received in response to advertising, and addresses disclosures, privacy, calling practices, assisting and facilitating, and recordkeeping. The FCC’s current telemarketing rules are codified in 47 C.F.R. § 64.1200.

Those are not the only rules that may matter. State law, industry-specific requirements, contracts, buyer policies, and the exact consumer journey can change the analysis.

This article is operational education, not legal advice. Buyers and publishers should have qualified counsel review the traffic model and current requirements that apply to their campaigns.

A practical control is to treat material changes as a new review event. A new landing page, traffic channel, script, call center, sub-publisher, product, geography, or consumer promise may change the source that was originally approved.

10. Can the buyer see what happened after activation?

A source should not be turned on if the operation cannot observe it.

At minimum, the buyer and operator should be able to determine:

Whether the source was offered and enabled.
Which campaign and target received it.
When activation occurred.
Who changed the setting.
Which calls were attributed to the source.
Why a call did or did not route.
Whether the destination answered.
Whether the call connected.
Whether it qualified.
Whether it became billable.
Whether it converted.
Whether it was disputed or adjusted.
Which date range and sample size support the metrics.
Whether the source was later paused, disabled, withdrawn, or changed.

A single blended campaign report is not enough for a source-level test.

The buyer needs to separate source performance from:

Publisher-wide performance.
Campaign-wide performance.
Target performance.
Agent performance.
Geography.
Schedule.
Call type.
Buyer-side outages.
Routing exclusions.

That does not mean every metric should become a verdict.

Long duration does not automatically prove strong intent. A conversion rate can be affected by agent skill, staffing, product fit, reporting delay, and sample size. A high dispute rate may reveal a source problem, a qualification-rule problem, or inconsistent buyer review.

Metrics should help the buyer ask better questions.

For a fuller discussion, read how source-level metrics help buyers scale more confidently.

11. Who can pause the source, and what triggers a pause?

Every new source needs a stop mechanism.

The buyer should know:

Who can disable the source.
Whether the operator can withdraw it.
Whether the publisher can stop sending it.
How quickly a routing change takes effect.
Whether the source can be disabled for one target without affecting others.
Who receives an alert.
What evidence is preserved for review.
What happens to calls already in progress or reserved.
How the source is re-enabled after a pause.

Pause triggers may include:

Material creative or script changes.
Consumer complaints.
Unexpected geography.
Misrepresented call type.
Sudden performance deterioration.
Duplicate concentration.
Routing to an unintended target.
Destination failure.
Missing recordings or reporting.
Dispute spikes.
Licensing or authorization concerns.
Unexplained volume changes.
Unresolved compliance questions.
A material change in the source’s upstream partners.

A pause is not always a final rejection.

It can be an operating control that protects the buyer, publisher, consumer, and investigation process while the parties determine what changed.

The important requirement is that the source can be isolated. If the only available action is to shut down an entire publisher, campaign, or buyer, the source definition and control model may be too broad.

A practical pre-activation checklist

Before turning on a new call source, the buyer should be able to answer the following.

Source definition

Is the source defined more narrowly than the publisher account?
Is the traffic direct or aggregated?
Are sub-publishers involved?
Is the source consumer-initiated inbound, transferred, or another defined type?
What label will identify it in routing and reporting?
Which material changes require another review?

Consumer journey

What did the consumer see or hear?
Who did the consumer expect to reach?
Are current creatives, landing pages, scripts, and sample calls available where appropriate?
Are the offer, geography, and product limitations clear?

Campaign fit

Which campaign accepts the source?
Which states or regions are allowed?
Which qualification and duplicate rules apply?
Are licensing, authorization, and vertical requirements understood?
Are buyer price and settlement terms clear?

Routing scope

Which target will receive the source?
What schedule applies?
What cap applies?
What concurrency limit applies?
What happens when the target is unavailable?
Can the source be disabled without affecting unrelated supply?

Buyer readiness

Are the right agents scheduled?
Are agents trained on the call type and consumer journey?
Is the destination working?
Are recordings, dispositions, and reporting functioning?
Can the buyer absorb the test volume?

Evidence and measurement

Which numbers are estimates, benchmarks, or buyer-specific history?
What sample size supports them?
Which events will be measured?
Are routed, connected, qualified, billable, and converted calls separated?
When will the test be reviewed?
What would justify scaling, continuing, restricting, pausing, or disabling?

Governance

Who approved the source?
Who can enable or disable it?
Are changes audited?
What triggers a pause?
Who investigates a complaint or performance anomaly?
How are source changes communicated?

If several of those questions cannot be answered, the buyer may not be ready to turn the source on.

A five-stage activation process

A disciplined source launch can be organized into five stages.

Stage 1: Review

Define the source, inspect decision materials, compare it with campaign requirements, document unresolved questions, and confirm commercial terms.

Stage 2: Configure

Select the campaign and target. Set geography, schedule, cap, concurrency, source controls, qualification rules, and reporting.

Stage 3: Validate

Confirm that the destination works, the source label resolves correctly, the route reaches the intended target, recordings and events are captured, and the source can be stopped.

Stage 4: Test

Run a controlled test with clear metrics, buyer-side staffing, a defined review window, and early monitoring.

Stage 5: Decide

Continue, adjust, restrict, pause, disable, or scale based on buyer-specific evidence.

The process does not need to be slow.

It needs to be explainable.

What Dependable Calls is building around this decision

Dependable Calls is being built around curated source enablement rather than unrestricted source discovery.

The operating model has two gates:

Dependable Calls decides which reviewed sources are appropriate to offer to a buyer.
The buyer decides which offered sources to enable for the applicable campaign and target.

The current implementation supports a source registry, operator-controlled offers, buyer-facing pseudonyms, campaign- and target-level enablement, source decision materials, buyer-scoped metrics, published benchmarks, audited changes, and live routing checks for curated targets.

That software support does not mean every source is automatically approved, profitable, compliant, or ready for scale. Dependable Calls remains a beta-stage operation. Source documentation, buyer readiness, live campaign testing, monitoring, QA, legal review, and continued hardening still matter.

The purpose of the control model is not to make the decision for the buyer.

It is to give the buyer a narrower, better-informed decision:

Turn on this reviewed source for this target under these limits, then evaluate what actually happens.

Want access to curated call sources? Apply to join the Dependable Calls buyer beta.