What Buyers Want to See Before They Take Your Calls

A serious buyer is not only asking whether you can send calls.

The buyer is asking whether the traffic can be understood, controlled, evaluated, and investigated.

A publisher may have real volume and years of industry knowledge. None of those facts automatically tells a new buyer what the caller experienced, which source produced the call, whether the traffic fits the buyer’s geography and product, how the call will route, or whether a problem can be traced back to a specific source.

The buyer is not merely purchasing an opportunity. The buyer is allowing an outside consumer journey to enter its phone system, agents, compliance process, CRM, quality program, dispute workflow, and financial records.

Clear evidence gives organized sources a way to stand apart from vague or blended supply.

But buyer review also needs limits. A buyer is not automatically entitled to every publisher identity, proprietary acquisition tactic, upstream commercial relationship, margin, ad account, or unrelated business record. The right standard is scoped transparency: enough information to make and defend a source-level decision without turning due diligence into unrestricted exposure.

This guide explains what serious buyers usually want to see, why broad promises are not enough, what information a publisher can reasonably protect, and how to prepare a buyer-review package that supports a controlled test.

This article is operational and educational. It is not legal advice. Advertising, telemarketing, privacy, recording, licensing, consent, and disclosure obligations vary by channel, vertical, jurisdiction, call type, and consumer journey. Publishers and buyers should review their specific practices with qualified counsel and other appropriate professionals.

What buyers are actually deciding

A new source commits more than buyer-price spend. It uses agent time, queue and telephony capacity, compliance and QA resources, reporting work, dispute-review time, follow-up labor, and brand reputation.

The buyer therefore needs to decide whether a defined source fits a specific campaign, target, destination, schedule, geography, call type, and operating team. Approval of one publisher relationship should not automatically approve every website, media channel, transfer team, sub-publisher, language, or product the publisher may operate.

The practical question is:

Can we define what we are turning on, observe what happens, and turn it down or off without losing the operating record?

That is why serious due diligence focuses on source identity, consumer journey, routing, reporting, controls, and accountability.

Promises are not evidence

Publishers often use short descriptions because the market rewards speed.

“Exclusive traffic.”

“High intent.”

“Fully compliant.”

“Great quality.”

“Direct inbound.”

Those phrases may describe a real strength. They are still incomplete until both sides agree on what the words mean and what records support them.

The distinction between a claim and substantiation is not unique to pay-per-call. The Federal Trade Commission’s business guidance states that advertising claims should be truthful, non-deceptive, and supported by evidence where appropriate. Specialized products and marketing methods may carry additional requirements. FTC advertising and marketing guidance

For publishers, the practical lesson is simple:

Replace adjectives with definitions, examples, and records.

A buyer can test a defined source. It cannot meaningfully test “great quality.”

What buyers may reasonably request

Not every buyer will request the same packet. The appropriate scope depends on the vertical, traffic type, risk, size of test, and buyer’s own obligations.

The following categories are common because they help the buyer understand the source without requiring unrestricted access to the publisher’s business.

Traffic category and acquisition method

The publisher should be able to describe how demand is created in plain language.

Useful categories may include:

• Paid search.
• Organic search.
• Social advertising.
• Display advertising.
• Native advertising.
• Owned-and-operated content.
• Comparison or directory traffic.
• Offline advertising.
• Existing audience or customer traffic.
• Consumer-initiated inbound.
• Warm transfer.
• Blind transfer where permitted and specifically approved.
• Scheduled callback.
• Network or sub-publisher supply.
• Another clearly defined method.

The description should identify the control boundary.

If the publisher owns the landing page but buys the media through an agency, say so. If a network supplies calls from several upstream publishers, do not describe the source as owned-and-operated. If a transfer center controls the upstream conversation, explain that role.

The buyer does not necessarily need the publisher’s exact keyword list, bidding rules, audience model, or vendor contract. It does need an honest explanation of who controls the material parts of the consumer journey.

The consumer journey from advertisement to call

A buyer wants to understand why the consumer is calling and what the consumer expects next.

A practical journey description may answer:

1. Where did the consumer encounter the message?
2. What product, service, or problem did the message describe?
3. What claim or offer received the consumer’s attention?
4. What call to action did the consumer see?
5. Did the consumer visit a landing page or complete a form?
6. Did the consumer place the call directly?
7. Did an upstream agent speak with the consumer?
8. What screening or qualification occurred?
9. What was the consumer told about the party receiving the call?
10. What context reaches the buyer at connection?

This does not have to be a thirty-page process map.

The important point is that the path should be specific enough to reveal expectation gaps.

A consumer who expects a government office, insurer, law firm, local contractor, lender, or specific brand should not unexpectedly reach an unrelated buyer. Google Ads’ destination rules likewise emphasize that destinations and phone numbers should function, relate to the advertised business, and provide a usable experience. Google Ads destination requirements

Consumer-initiated inbound versus transfer

“Calls” is too broad a category for buyer approval.

A consumer-initiated inbound call generally begins when the consumer chooses to dial a number presented through an ad, site, listing, or other source.

A transfer includes an upstream interaction before the buyer receives the caller. The upstream party may have screened the consumer, explained the next step, introduced the buyer, or simply transferred the call without an agent-to-agent handoff.

Both models can produce useful calls. They should not be represented as interchangeable.

Publishers should be ready to explain:

• Whether the caller dialed voluntarily.
• Whether an upstream agent participated.
• Whether the transfer was warm or blind.
• What screening questions were asked.
• What the caller was told about the handoff.
• Whether the buyer receives any context.
• How the call type appears in reporting.
• Whether different qualification rules apply.

A buyer that expects consumer-initiated inbound calls but receives transfers is not dealing with a minor labeling issue. The buyer approved a different consumer journey.

Advertising channels, creatives, claims, disclosures, and calls to action

Buyers may ask for representative examples of the materials that generate the calls.

That can include:

• Search-ad copy.
• Social or display creative.
• Video or audio scripts.
• Landing-page screenshots.
• Call-only ad examples.
• Directory listings.
• Advertorial content.
• Transfer scripts.
• Required disclosures.
• Calls to action.
• Brand references.
• Phone-number presentation.

A buyer usually needs to assess whether the message aligns with the product, service, geography, and receiving experience. It may also need to determine whether prohibited, misleading, unsupported, or buyer-incompatible claims are present.

A publisher does not have to disclose every test variation or media strategy by default. It should provide enough representative material to support the source description and explain how material changes are reviewed.

“Creative available upon request” is weaker than an organized packet that identifies:

• Which creative belongs to which source.
• When it was active.
• Which geography or channel used it.
• What landing page or number it led to.
• Whether it is current, retired, or illustrative.
• Who approves material changes.

Landing pages, forms, brands, and domains

A buyer may reasonably request the live or representative landing page and the domain associated with the source.

Review may include:

• Page ownership or control.
• Brand presented to the consumer.
• Product or service described.
• Calls to action.
• Disclosures.
• Forms and fields.
• Phone number displayed.
• Links to privacy or other relevant notices.
• Mobile functionality.
• Geographic statements.
• Whether the page redirects.
• Whether the domain or brand changes across the journey.

The buyer is not necessarily entitled to the publisher’s entire domain portfolio. It is entitled to know which page or experience supports the source being proposed.

A common red flag is a page that looks acceptable during review while traffic actually comes from other, undisclosed pages. Another is a domain, brand, or phone number that cannot be connected to the described business or source.

Google’s misrepresentation policy is a useful reminder that concealed identity, misleading business information, and dishonest presentation can create platform and consumer-trust problems. Google Ads misrepresentation policy

Geography, hours, volume, and operating limits

A buyer needs to know where and when the calls are likely to arrive.

Publishers should provide realistic estimates for:

• States, regions, counties, or ZIPs.
• Languages.
• Days and hours.
• Time zone used.
• Expected daily and weekly volume.
• Peak intervals.
• Burstiness.
• Seasonality.
• Ramp potential.
• Minimum or maximum useful test size.
• Known exclusions.
• Conditions that could change volume.

Do not treat an optimistic ceiling as expected production.

A source that reliably produces fifteen calls during the buyer’s staffed window may be easier to approve than a source promising one hundred calls with no interval pattern.

Volume should also be tied to source continuity. If scaling requires new landing pages, partners, channels, transfer teams, or geographies, say so. More volume from a materially different source should not inherit the original approval automatically.

Source and sub-source identifiers

A buyer needs a stable way to recognize the traffic.

Useful identifiers may include:

• Publisher account.
• Registered source ID.
• Buyer-facing source name or pseudonym.
• Sub-source.
• Campaign.
• Creative or landing-page ID.
• Tracking number.
• Call type.
• Routing request ID.
• Call ID.
• Buyer target or destination.
• Timestamp.

The exact fields vary by system. The principle does not:

Materially different traffic should not be blended into a label that prevents source-level decisions.

Stable identifiers support source-level reporting for publishers, buyer analysis, dispute review, and financial reconciliation.

They also protect strong publishers. When good and weak sources are blended, the buyer may pause everything because it cannot isolate the problem.

Caller-ID handling

Caller-ID handling matters because routing, duplicates, consumer callbacks, fraud review, and call reconciliation may depend on the number received.

A publisher should explain:

• Whether the original caller number is passed.
• Whether the number can be missing, masked, or altered.
• Whether transfers preserve the original caller identity.
• Which number appears on different call legs.
• How tracking numbers are used.
• How callback calls are handled.
• Whether the routing system matches the pre-call request to the live call.
• What happens when caller data does not match.

Telephony records can distinguish call direction, originating and receiving endpoints, status, duration, parent call legs, and other connection properties. Twilio’s Call resource is one example of how call platforms preserve separate operational fields rather than treating a call as a single undifferentiated event. Twilio Call resource

A publisher should not promise that caller ID proves identity or intent. It is one operating signal. It still needs consistent handling and documented exceptions.

For a deeper explanation, see why caller-ID matching matters in call routing.

Duplicate and repeat-caller controls

“Exclusive” traffic does not answer the duplicate question.

Buyers may ask:

• What identifies a duplicate?
• What lookback period is used?
• Is the rule buyer-specific, campaign-specific, source-specific, or global?
• Are repeat callers always excluded?
• How are callers with legitimate new needs handled?
• Is the check performed before routing, after connection, or both?
• How do masked or changed numbers affect detection?
• Can the publisher detect repeats across its own sub-sources?
• How does duplicate status appear in reporting?

There is no universal duplicate policy for every vertical and relationship.

The policy should be written before traffic starts, not invented during invoice review. Publishers should understand why duplicate policies matter in call campaigns and disclose the controls they actually use.

Call tracking and routing method

A buyer wants to know whether the publisher can respect operating controls.

The publisher should be able to explain:

• Which platform or integration routes the calls.
• Whether a pre-call ping or live-call workflow is used.
• How source labels travel through the route.
• How geography is determined.
• How schedules and time zones are applied.
• How caps and concurrency are enforced.
• What happens when no buyer is eligible.
• How a disabled target is removed from consideration.
• How reservations or buyer acceptance are handled.
• What happens when the destination fails.
• Whether the publisher can pause one source without stopping all traffic.
• Who can make emergency changes.

Buyers are trying to avoid a situation where “paused” means “we sent fewer calls” or “disabled” means “the publisher did not see the message yet.”

The routing process should have a clear source of truth and an accountable operator.

Sample reporting fields

A buyer does not need every possible field during initial review. It should be able to see whether the proposed record is sufficient to evaluate the source.

A useful sample may include:

• Call ID.
• Source and sub-source.
• Campaign.
• Call type.
• Timestamp and time zone.
• Caller geography.
• Buyer target.
• Routing result.
• Connection status.
• Duration.
• Billable duration where different.
• Qualification status.
• Billable status.
• Conversion status where applicable.
• Duplicate status.
• Rejection or exclusion reason.
• Dispute status.
• Recording or QA availability indicator.
• Buyer price where appropriate to the buyer report.

Avoid collapsing routed, connected, qualified, billable, converted, invoiced, and paid into one “successful call” field.

The buyer should be able to compare its call detail with invoices and internal outcomes. The publisher should be able to compare the same operating events with its payout report.

Historical performance and provenance

Historical performance can help a buyer size a test, but only when the buyer understands where the numbers came from.

Useful context includes:

• Date range.
• Sample size.
• Source and sub-source included.
• Buyer or vertical context.
• Call type.
• Qualification definition.
• Duration definition.
• Conversion definition.
• Duplicate and dispute treatment.
• Whether data is publisher-reported, operator-computed, or buyer-specific.
• Whether results were blended across materially different traffic.

A publisher estimate is not the same as a live system metric. A result from another buyer is not a forecast for the next buyer. A ten-call sample should not be presented with the confidence of a thousand-call history.

This does not mean a new source cannot be approved without history.

It means the source should be labeled honestly as new, and the buyer should use a controlled test. Benchmarks can help a new source earn confidence when their provenance and limitations are clear.

Call recordings and QA samples

Recordings or redacted transcripts can help a buyer understand caller intent, transfer quality, upstream statements, handoff quality, and agent handling.

They also create legal, privacy, security, and access-control questions.

Publishers should provide recordings or QA samples only when they have a lawful basis to record, retain, process, and share them for the proposed purpose. Review the applicable jurisdictions, disclosures, contracts, access controls, retention limits, and handling of sensitive information.

A buyer may reasonably ask whether recording occurs, which call leg is captured, what disclosure or consent process is used, whether samples are representative, how sensitive information is redacted, who can access the material, and how access and retention are controlled.

A telephony platform’s ability to create or retrieve a recording does not decide whether the recording is lawful or appropriate to share. Twilio’s Recording resource documents technical recording objects and access, but publishers still need a separate legal and operational review. Twilio Recording resource

Read call recordings, consent, and QA before treating recordings as routine sales collateral.

Licensing and vertical-specific restrictions

Some campaigns involve products, services, or intake activities with licenses, registrations, appointments, certifications, authorizations, or geographic restrictions.

A buyer may ask:

• Which verticals the source promotes.
• Which states or territories are included.
• Which entity is represented in the advertising.
• Whether the publisher or an upstream party performs screening or intake.
• Whether certain statements or activities are restricted.
• Whether the buyer must provide approved creative or disclosures.
• Whether calls can route only to specific licensed or authorized teams.
• What changes when a new state or product is added.

The publisher should not assume that the buyer’s license solves every upstream advertising or intake question. The buyer should not assume that a publisher can provide a legal guarantee through a checkbox.

The correct approach is to identify the actual activity and obtain current, qualified advice for the relevant vertical and jurisdiction.

Consent and disclosure practices

Consent is not a magic word.

The applicable question depends on what the publisher is doing. A consumer placing a call after viewing an advertisement presents different operational facts from a consumer submitting a form for future calls or texts, receiving a prerecorded message, or being transferred after an upstream conversation.

A buyer may reasonably request the consumer journey, relevant disclosure language, where it appears, the action the consumer takes, timestamp and source records where relevant, how the record connects to the call, and how revocation, complaints, or suppression requests are handled.

Publishers should avoid saying “TCPA compliant,” “DNC compliant,” or “fully consented” as a substitute for showing the actual process and obtaining legal review.

The FTC’s Telemarketing Sales Rule page provides the current rule text and official materials for covered telemarketing practices. It is one of several authorities that may matter depending on the facts. FTC Telemarketing Sales Rule

Complaint and escalation procedures

A buyer wants to know what happens when something goes wrong.

A practical procedure should identify:

• Who receives the complaint.
• How the relevant call and source are identified.
• Which records are preserved.
• Whether the source is paused during review.
• Who contacts upstream partners when applicable.
• How the consumer concern is handled.
• How the buyer receives an update.
• What triggers broader QA review.
• What corrective actions are available.
• How repeated patterns affect source status.
• How final findings are documented.

“No complaints so far” is not a complaint process.

The publisher should be able to investigate without revealing unrelated consumer data or partner information. The buyer should provide enough detail to identify the event and should not expect the publisher to investigate vague statements such as “quality was bad last week.”

Publisher contact and accountability information

Every source needs an accountable owner.

The buyer may not need the name of every media buyer, affiliate, or vendor. It does need a contact who can act.

That contact should be able to:

• Confirm the approved source.
• Explain the consumer journey.
• Coordinate routing changes.
• Pause traffic.
• Provide or retrieve review materials.
• Investigate call-level issues.
• Communicate material changes.
• Respond to complaints and disputes.
• Reconcile reporting differences.
• Escalate urgent problems.

A publisher relationship becomes difficult when sales, integration, compliance, QA, and finance each assume someone else owns the source.

What buyers are really trying to determine

The long request list usually reduces to eight operating questions.

Does the caller understand why they are calling?

The buyer wants alignment among the ad, landing page, call to action, upstream conversation, and receiving agent.

Does the traffic fit the buyer’s product and geography?

A genuine call can still be unusable because of product, service area, state, language, eligibility, license coverage, hours, or agent skills.

Can the source be identified and controlled?

The buyer wants to enable, cap, limit, pause, or remove a defined source without stopping unrelated traffic.

Can the publisher investigate problems?

A complaint or dispute should be traceable to a journey, creative, sub-source, tracking number, and accountable owner.

Are routing and caller data trustworthy?

The buyer needs confidence that source labels belong to the calls, caller data is handled consistently, and disabled or ineligible targets are respected.

Can performance be measured at the source level?

Segmentation should separate strong traffic from weak traffic and source issues from buyer-handling issues.

Will the publisher respect caps, schedules, and disabled targets?

Buyer controls must work in the routing process, not only in a spreadsheet or chat thread.

Can disputes be evaluated fairly?

Both sides need call-level records, written rules, reason codes, evidence standards, and a defined review window. A non-converting call is not automatically unqualified, and a connection is not automatically payable.

An evidence hierarchy for source review

Not every piece of information deserves equal weight.

A practical hierarchy is:

1. The buyer’s own live, source-level results.
2. Live source history computed from traceable call records.
3. Reviewed decision materials tied to the registered source.
4. Publisher records with clear definitions and provenance.
5. Publisher estimates or self-reported benchmarks.
6. Broad promises without definitions or supporting records.

New sources often begin near the bottom because live history does not exist yet.

That is acceptable when the uncertainty is explicit.

The right response is not to manufacture confidence. It is to run a limited test, preserve the source identity, apply known rules, review the calls, and replace estimates with live evidence.

Publisher privacy and scoped transparency

Useful transparency is not the same as unrestricted disclosure.

A buyer may need to know:

• The source type.
• The traffic category.
• The consumer journey.
• The direct-versus-network relationship class.
• The reviewed creatives or scripts.
• The relevant domain or landing page.
• The expected geography, hours, and volume.
• The source identifier.
• The routing and reporting method.
• The accountable operator.
• The records available for investigation.

A buyer generally does not need every upstream identity, the publisher’s customer list, exact media-buying tactics, bid logic, internal margins, unrelated ad accounts or domains, confidential vendor contracts, other buyers’ private performance, or consumer PII beyond the legitimate operating need.

This balance is explained more fully in why source identity, publisher privacy, and buyer trust need balance.

Stable pseudonyms can support accountability

A buyer-facing source may use a stable pseudonym when the operator retains the complete internal identity and can connect it to the publisher relationship, reviewed traffic path, decision materials, call records, performance, complaints, disputes, and financial outcomes.

The pseudonym should protect confidentiality, not create anonymity. The buyer should still be able to recognize, measure, enable, pause, and discuss the same source over time.

IAB Tech Lab’s sellers.json specification is not a pay-per-call rule, but it illustrates a related trust principle: distinguish direct sellers from intermediaries and preserve enough supply-chain identity for buyers to evaluate the path. IAB Tech Lab sellers.json

Publishers can challenge unreasonable requests

A publisher can ask what decision the request supports, whether it is tied to the proposed source, who will have access, how it will be retained, whether a redacted sample or operator review would meet the need, and whether the request creates circumvention risk without improving quality or control.

Reasonable review should be proportional.

A five-call test may not justify the same disclosure scope as a large, regulated, long-term relationship. A high-risk vertical may require more evidence than a simple local-service campaign.

A buyer-review checklist for publishers

Before approaching a new buyer, confirm that you can answer the following.

Source identity

• We have a stable source name or ID.
• We can describe the traffic category and acquisition method.
• We can state whether the source is direct, network, or another relationship class.
• Materially different sources and sub-sources are separated.
• An accountable person owns the source.

Consumer journey

• We can map the path from advertisement or upstream interaction to the buyer call.
• We can distinguish consumer-initiated inbound from transfer traffic.
• We can explain what the caller saw, heard, submitted, and expected.
• We have representative current creatives, pages, or scripts.
• We have a process for reviewing material changes.

Operating fit

• We can state the vertical, product, language, and geography.
• We have realistic hours and volume estimates.
• We can describe peaks, seasonality, and ramp limits.
• We understand the buyer’s accepted call type and qualification rules.
• We can start with a controlled test.

Tracking and routing

• Source and sub-source IDs travel with the call or routing request.
• Caller-ID and tracking-number behavior are documented.
• Duplicate and repeat-caller controls are defined.
• Caps, schedules, time zones, and target status are enforced.
• We can pause one source or target promptly.
• Routing failures and rejection reasons can be identified.

Reporting and evidence

• We can provide a sample call-detail report.
• Statuses such as routed, connected, qualified, billable, and converted remain distinct.
• Historical performance includes a date range, sample size, and definitions.
• Self-reported estimates are labeled as estimates.
• Call or QA samples are shared only when lawful and appropriately controlled.
• We can reconcile buyer feedback to source-level records.

Compliance and accountability

• Relevant claims, disclosures, and calls to action have been reviewed.
• Consent or disclosure practices can be explained with actual records where applicable.
• Vertical and geographic restrictions are documented.
• Complaint and escalation procedures exist.
• We know who can preserve records and investigate.
• We do not use “fully compliant” as a substitute for legal review and evidence.

Publisher protection

• We know which information is necessary for the buyer’s decision.
• Confidential partner identities and tactics are protected unless disclosure is justified.
• Access, retention, and confidentiality expectations are defined.
• Qualification, dispute, and feedback rules are agreed before launch.
• The buyer’s destination, staffing, schedule, and reporting are ready for a fair test.

Red flags that delay or stop approval

Buyers often delay or reject a source for reasons that are visible before the first call.

Vague traffic descriptions

“Digital traffic,” “inbound,” or “network calls” does not explain the consumer journey or control boundary.

Undisclosed transfers

A source is presented as consumer-initiated inbound, but an upstream agent actually screens or transfers the caller.

Identity mismatches

The brand, domain, phone number, source label, contract party, and described publisher relationship do not line up.

Review samples that do not represent live traffic

The approved page or creative is polished, but traffic comes from other undisclosed experiences.

Blended source labels

Several partners, pages, channels, or call types share one label, preventing source-level evaluation.

No reliable stop mechanism

The publisher cannot explain how it will respect a cap, schedule, disabled target, or emergency pause.

Impossible or unsupported volume claims

Projected volume is inconsistent with history, hours, geography, or the stated acquisition method.

Unexplained caller-ID behavior

Caller numbers are routinely missing, altered, repeated, or inconsistent with the routing request, and no exception process exists.

No duplicate policy

The publisher promises exclusivity but cannot explain repeat-caller detection, lookback periods, or reporting.

Reports that cannot reconcile

The publisher’s totals do not tie to call IDs, routing outcomes, qualification statuses, or payout records.

Careless recording access

Raw recordings containing sensitive information are offered as sales samples without a clear lawful basis, access control, redaction, or retention policy.

Blanket compliance guarantees

The publisher says “fully compliant” but cannot show the consumer journey, disclosures, responsible reviewer, applicable scope, or current advice.

No accountable operator

The salesperson can make promises, but no one owns routing, QA, complaints, or reconciliation.

Resistance to a controlled test

The publisher demands immediate volume or refuses source-level measurement.

Unreviewed source changes

New pages, sub-publishers, scripts, geographies, or transfer teams are added under an existing approval without notice.

A red flag may not prove misconduct, but it signals that the buyer lacks enough evidence or control to proceed confidently.

What a fair buyer review should look like

Publisher readiness is only half of the relationship.

A fair buyer should explain the accepted call types, qualification and billability rules, geographies, schedules, caps, concurrency limits, duplicate policy, receiving destination, reporting fields, dispute evidence, feedback process, payout timing, confidentiality controls, and its own emergency-pause procedure.

Buyers should not demand perfect disclosure from publishers while providing vague qualification rules and weak call records.

They should not treat a non-converting call as automatically unqualified. They should not expose publisher materials beyond the people who need them. They should not use due diligence to solicit upstream relationships or copy proprietary acquisition methods.

Publishers should review the buyer too. Serious publishers should look for clear rules, predictable routing, fair disputes, useful reporting, and dependable payment.

The best review process creates mutual clarity before either side takes meaningful risk.

How Dependable Calls approaches source review

Dependable Calls is being built around controlled, operator-led source enablement.

The model has two gates:

1. Dependable Calls determines which reviewed sources are appropriate to offer to a buyer.
2. The buyer decides which offered sources to enable for a specific campaign or target.

Both gates must be satisfied before a curated source routes.

The current implementation supports buyer-safe source identities, consumer-initiated inbound and transfer classifications, direct-publisher versus network relationship classes, curated decision assets, separate campaign and destination controls, and source-level metrics with provenance labels. These capabilities remain subject to live validation, operating discipline, and continued hardening.

The goal is not to expose every publisher relationship.

The goal is to give serious buyers enough information and control to make a source-level decision while giving serious publishers a structured way to prove that their traffic can be understood, measured, managed, and investigated.

A publisher does not need to reveal everything.

It does need to show that the source is real, the caller journey is explainable, the routing is controllable, the reporting is usable, and problems will have an accountable owner.

Have buyer-ready traffic? Apply to become a Dependable Calls publisher.