Direct Publishers, Brokers, and Exchanges: Understanding the Tradeoffs in Call Supply

Call supply can reach a buyer through several relationship structures.

A publisher may contract directly with the buyer. A broker or network may package traffic from one or more publishers. An exchange or routing intermediary may coordinate multiple sources and buyers through a shared operating layer.

None of those structures is automatically good or bad.

A direct relationship can be deeply transparent, commercially efficient, and easy to manage. It can also hide sub-publishers, rely on one fragile integration, or leave both parties without a neutral operating record.

A broker can assemble useful supply, absorb business-development work, and resolve problems through experienced account management. It can also become a weak link when the broker cannot explain the traffic, control upstream changes, or reconcile downstream disputes.

An exchange can centralize routing, buyer access, reporting, and settlement. It can also add technical and financial dependency, create a larger failure domain, or provide little real control despite an impressive interface.

The right comparison is therefore not direct versus middleman.

It is:

Which party performs each material job, what records support that job, which controls are enforceable, and who remains accountable when the call does not behave as expected?

This article compares the three supply-chain models without declaring a universal winner. It focuses on relationship and operating structure: who owns the relationship, who sees the source, who maintains the integration, who makes routing decisions, who handles disputes, who invoices the buyer, who pays the publisher, and where risk concentrates.

For the narrower category distinction between a supplier and a two-sided operator, read The Difference Between a Call Vendor and a Call Exchange. The purpose here is different. A direct publisher, broker, or exchange can each act as a vendor in one relationship. This guide examines the chain behind that relationship.

This article is educational and operational, not legal advice. Advertising, telemarketing, privacy, consent, recording, licensing, data-sharing, and contract duties vary by jurisdiction, vertical, consumer journey, and party role. Qualified counsel should review the requirements that apply to a specific arrangement.

The short answer

A buyer should not choose a supply model based on the number of intermediaries alone.

A publisher should not choose a demand path based on the headline payout alone.

Both sides should evaluate:

1. Source definition: Can the traffic path be identified and kept stable?
2. Responsibility: Is every material operating job assigned to a real party?
3. Control: Can source access, routing, caps, schedules, concurrency, destinations, and changes be enforced?
4. Evidence: Do call, source, routing, quality, dispute, invoice, and payout records connect?
5. Incentives: Does each participant benefit from accurate classification, sustainable performance, and timely problem resolution?
6. Financial exposure: Who owes the buyer invoice, who owes the publisher payout, and what happens if another party does not pay?
7. Failure containment: Can one weak source, buyer, integration, or payment problem be isolated without stopping everything?
8. Operator judgment: Who notices when the written rules no longer match what is happening live?

A direct relationship often works well when the parties know exactly what they are buying and selling, the routing path is simple, and both sides can carry the operational workload.

A broker often works well when relationship access, traffic packaging, account management, and commercial coordination create more value than the added layer costs.

An exchange often works well when multiple sources and buyers need shared routing, source controls, technical normalization, call-level records, dispute handling, and financial administration.

A hybrid model is often the most practical: direct strategic relationships for core supply, plus an exchange or broker for incremental sources, specialized routing, testing, or administrative support.

Define the models before comparing them

The market uses overlapping labels. One company may generate calls, broker outside supply, operate routing software, manage buyer contracts, and settle publisher payouts. Another may call itself an exchange while selling one blended stream. A direct publisher may rely on approved sub-publishers.

Current call-platform documentation reflects that overlap: Ringba defines publishers broadly enough to include website owners, advertising networks, affiliate marketers, and call centers, while buyers can include businesses, networks, and call centers. Its RTB documentation separately describes bids, rate limits, payout triggers, and duplicate handling. Functions matter more than labels.

Direct publisher relationship

A direct publisher relationship exists when the buyer contracts with the publisher represented as controlling or supplying the defined source.

The publisher may own the consumer-facing property, buy media, operate transfers, manage affiliates, or aggregate disclosed sub-sources. “Direct” describes the contracting path. It does not prove that every traffic input is owned and operated by the contracting publisher.

Broker or network relationship

A broker or network connects supply and demand through relationship and commercial coordination.

It may recruit publishers, organize traffic packages, translate buyer requirements, support integrations, collect feedback, handle disputes, invoice the buyer, pay the publisher, and move traffic among buyers. Some brokers operate substantial technology; others use third-party platforms. Some expose each source; others sell a blended package.

Exchange or routing intermediary

An exchange or routing intermediary coordinates call opportunities across multiple supply and demand relationships through a common decision and record layer.

It may receive pings or live calls, evaluate eligibility, request bids, reserve and bridge routes, preserve lifecycle events, apply qualification rules, support disputes, bill buyers, calculate publisher payouts, and reconcile both sides.

An exchange does not have to be open or auction every call. It can use invitation-based source access, fixed bids, RTB, priority rules, or hybrids.

The source is a separate layer

The consumer-facing source may be one website, paid-search campaign, social funnel, inbound call path, transfer team, sub-publisher, domain and creative set, or other defined traffic path.

A buyer may contract directly with a publisher while receiving several materially different sources. A broker may provide one tightly controlled source. An exchange may route both direct and intermediated sources.

The relationship model explains who contracts and coordinates. The source model explains what traffic is actually being delivered.

Three hypothetical supply chains

The examples below are hypothetical.

Hypothetical chain A: direct publisher to buyer

Consumer → publisher-owned landing page → publisher tracking number → buyer target → buyer CRM

The buyer contracts with the publisher. The publisher sends calls to one or more buyer destinations. The parties exchange source documentation, qualification rules, reports, invoices, and payments directly.

This chain can be simple. It can also require both parties to build and maintain every operating connection themselves.

Hypothetical chain B: publisher through a broker

Consumer → publisher source → broker tracking or routing layer → buyer target → buyer CRM

The publisher contracts with the broker. The broker contracts with the buyer. The broker may combine traffic from several publishers or keep each source separate.

The broker receives the buyer price and owes the publisher payout under separate agreements. A buyer rejection does not automatically define whether the publisher remains payable. That depends on the applicable terms and evidence.

Hypothetical chain C: source through an exchange

Consumer → publisher source → exchange intake → eligibility and buyer selection → reserved route → buyer target → call outcome → exchange settlement records

The exchange manages the transaction layer. A publisher may submit a ping before the call, send the live call directly, or use another approved integration. Buyers may participate through fixed targets, RTB endpoints, or other controlled rules.

The exchange may have the most detailed shared record. It also becomes a critical dependency for routing and settlement.

A balanced comparison matrix

The table describes common tendencies, not guarantees.

No model wins every row. The useful question is whether the structure delivers enough control, access, evidence, and operating work to justify its cost and dependency.

Where direct publisher relationships work well

Direct relationships are strongest when both parties want depth more than breadth.

They can work especially well when:

• The buyer wants a strategic or distinctive source.
• The source and any approved sub-sources are clearly defined.
• The buyer can perform source and creative review.
• One source routes to a manageable number of targets.
• Qualification and duplicate rules are stable.
• The buyer can return timely source-level outcomes.
• Both parties can reconcile calls, disputes, invoices, and payments.
• The relationship justifies dedicated integration and account management.

Direct access can support detailed discussions about media, creatives, transfers, buyer handling, source changes, and campaign design. Commercial responsibility may also be easy to locate: the buyer owes the publisher, and the publisher answers directly for the supply it sells.

Direct relationships tend to break down when the hidden workload multiplies. Buyers may build different integrations and reports for every publisher. Publishers may rebuild for every buyer. Informal source changes, unreviewed sub-publishers, inconsistent feedback, incompatible identifiers, and broad disputes can make a supposedly simple path difficult to manage.

Direct is not the absence of operating cost. It moves more of that cost and responsibility into the buyer’s and publisher’s teams.

Where brokers and networks work well

A broker is valuable when relationship and coordination work creates measurable value.

A capable broker may know which buyers are actively accepting a vertical, which publishers can supply a specific call type, which integrations are realistic, and which partners resolve problems responsibly. It can turn fragmented supply into an evaluable package containing the source, consumer journey, acquisition method, geography, schedule, capacity, qualification rules, review material, reporting method, dispute process, and commercial terms.

It may also absorb contracts, tracking setup, buyer changes, test caps, reporting, disputes, invoices, payouts, collections, and partner communication. Removing the broker does not remove those jobs; it reallocates them.

Broker relationships tend to break down when the broker takes economic responsibility without operational visibility or authority. Warning signs include blended sources, unsupported buyer feedback, unreviewed creative changes, inability to pause the actual traffic path, unclear downstream-collection terms, reports that do not reconcile, conflicting resale paths, or no party clearly responsible for a complaint.

The FTC’s lead-generation workshop examined consumer information moving through multiple marketing entities and auction-style “ping tree” mechanics. Calls are different from form leads, but the operating lesson is useful: additional layers require clearer roles and records, not automatic condemnation of intermediaries.

Where exchanges and routing intermediaries work well

An exchange is valuable when a shared layer solves work that would otherwise repeat across many buyer-publisher pairs.

It can let publishers and buyers connect through common fields, source IDs, routing rules, reason codes, call events, dispute records, and settlement records. That reduces repeated plumbing without eliminating every custom difference in CRM, qualification, transfer type, or commercial terms.

The strongest use case is live coordination. A call may route only when the source is permitted, the target is eligible and open, geography and call type match, caps and concurrency remain, the destination is healthy, duplicate rules allow the call, and the bid or fixed rule is valid. A control shown in a portal matters only when the live route enforces it.

That distinction is central to what source enablement means in pay-per-call: the operator’s offer, the buyer’s enablement, and call-time eligibility are separate decisions.

A shared record layer can also connect the publisher ping, source, buyer opportunity, bid, reservation, route, telephony events, qualification, conversion, dispute, invoice, and payout. It can support the scoped transparency described in Why Source Identity, Publisher Privacy, and Buyer Trust Need Balance: the buyer gets enough stable source information to decide and investigate, while unrelated publisher details remain protected.

Exchanges tend to break down when centralized dependency is not matched by control and accountability. A routing defect or outage can affect many relationships. Stored settings may not be enforced. Source catalogs can become labels without review. Disputes can become procedural queues. Cash timing can create payment pressure. Partners may lack enough exportable data to verify settlement.

An exchange is useful only when its routing, records, permissions, and financial administration solve real operating problems.

What programmatic advertising teaches—and what it does not

Programmatic advertising has spent years trying to make complex supply paths easier to inspect.

IAB Tech Lab’s ads.txt standard lets publishers declare which companies are authorized to sell their inventory. Its sellers.json and SupplyChain specifications distinguish direct sellers from intermediaries and identify the entities selling or reselling a bid request.

Google’s OpenRTB implementation guide goes further into the transaction path. Its SupplyChain object can indicate whether the chain is complete, identify nodes in order, and show which entities participate in payment flow.

Those standards do not map directly onto pay-per-call. An ad impression and a live consumer phone call are different units with different operational and legal concerns.

The useful principle is narrower:

A multi-party market becomes easier to govern when authorization, identity, transaction path, and payment responsibility are represented explicitly.

Pay-per-call does not need to copy every programmatic standard to learn from that principle.

The controls matter more than the label

A buyer and publisher should evaluate the operating system beneath the relationship.

Source identity and change control

Ask:

• Is each source defined separately?
• Can sub-sources be distinguished?
• Does the source identity persist across routes and reports?
• Who approves a material change?
• What triggers re-review?
• Can one source be paused without disabling the entire publisher?

A “direct” publisher with opaque sub-sources may provide less usable visibility than an exchange with stable source records.

A broker with disciplined source packaging may be easier to investigate than a direct relationship based on informal trust.

Buyer permissions

Ask:

• Does the buyer choose which sources it accepts?
• Is that choice per buyer, campaign, target, or destination?
• Can the buyer set test limits?
• Can the buyer disable one source?
• Does the buyer receive enough information to make the decision?
• Is the permission enforced during routing?

For a practical activation checklist, see What a Buyer Should Know Before Turning On a New Call Source.

Routing and capacity controls

Ask who owns:

• Business-hour schedules.
• Holiday schedules.
• State and ZIP filters.
• Product eligibility.
• Call-type restrictions.
• Daily and hourly caps.
• Budget caps.
• Concurrency.
• Queue protection.
• Destination failover.
• RTB timeouts.
• Reservation windows.
• Duplicate lookbacks.
• Caller-ID requirements.

A model that cannot enforce buyer capacity may destroy value even when the source is good.

Source and creative review

Ask:

• Who reviews the publisher?
• Who reviews the source?
• Who reviews creatives, landing pages, forms, scripts, and disclosures?
• Does approval apply to one source or the whole publisher?
• Are approved versions preserved?
• What happens after a material change?
• Who can suspend traffic during an investigation?

Review should be scoped and dated. It is not a permanent compliance or quality certificate.

Quality feedback

Ask:

• Does the buyer provide call-level or source-level feedback?
• Can source performance be separated from buyer handling?
• Are answer rate, connected duration, qualification, and conversion distinct?
• How are complaints escalated?
• Can the publisher challenge a classification?
• Does the broker or exchange translate feedback accurately?

Feedback that cannot identify the affected source often creates broad blame rather than improvement.

Disputes

Ask:

• Which calls are disputable?
• Which evidence is required?
• What is the deadline?
• Who decides?
• Is there an appeal or escalation path?
• Can the result be tied to qualification and settlement records?
• Does the intermediary have authority to bind both sides?
• Does a buyer dispute automatically reverse the publisher payout?

The last question is especially important.

Buyer billability and publisher payability may be related, but they are not the same status. Separate contracts can create different obligations.

Invoicing and payouts

Ask:

• Who invoices the buyer?
• Who owes the publisher?
• Are buyer price and publisher payout stored separately?
• Which event creates a buyer charge?
• Which event creates a publisher payable?
• How are credits and adjustments handled?
• Does the publisher wait for downstream collection?
• Are reserves, holdbacks, or delayed payouts allowed?
• Can both parties reconcile totals to call-level records?
• What happens if the intermediary fails?

The number of parties does not determine the answer.

The contracts, records, controls, and financial capacity do.

Buyer and publisher implications

The same structure can look different from each side.

What buyers should prioritize

A buyer should prefer a direct relationship when one strategic publisher matters enough to justify dedicated review, integration, feedback, dispute handling, and payment administration. Direct can create a strong learning loop when the buyer understands the source and can support the relationship properly.

A broker may be the better fit when the buyer needs relationship coverage, organized traffic packages, one commercial contact, and experienced account management. The buyer should verify what the broker actually reviews, which upstream changes it can control, and whether it has authority to resolve disputes.

An exchange may fit when the buyer needs several sources under common routing rules, RTB or centralized target management, source-level enable and disable controls, consistent call records, and one financial-administration path. The buyer should also evaluate platform dependency, data portability, operator responsiveness, and financial strength.

The buyer does not have to choose one permanent model. Direct strategic publishers can coexist with a broker or exchange used for new-source tests, geographic gaps, overflow, specialized supply, or centralized routing. The paths should retain separate source IDs, economics, and performance records.

What publishers should prioritize

A publisher should compare demand paths through access, feedback, payment confidence, source protection, and concentration.

Direct buyers can support deeper collaboration, custom integration, and faster source-specific learning. They can also expose the publisher to one buyer’s capacity changes, disputes, collections behavior, and internal process.

A broker can reduce business-development and administrative work, place sources across several buyers, and translate campaign requirements. The publisher should determine whether the broker is the contractual payor, whether payout depends on downstream collection, and whether the broker can produce usable rejection and dispute evidence.

An exchange can let one integration reach multiple eligible buyers, adapt routing to live capacity, preserve source-level records, and standardize payout reporting. The publisher should verify how buyer access is scoped, whether source identities remain separate, how disputes affect payability, and whether broad buyer access is real or concentrated behind one major counterparty.

For both sides, diversification is useful only when the operation remains explainable. A larger number of relationships does not help when several sources are blended into one label or when all financial exposure still depends on one organization.

Commercial cost should be judged against work and risk

“Cutting out the middleman” is not a complete economic analysis.

An intermediary may perform buyer and publisher sourcing, contracts, source and creative review, integration support, routing, RTB, monitoring, disputes, invoicing, collections, payouts, reconciliation, and technical maintenance. Those jobs still exist in a direct relationship; the buyer and publisher simply perform or purchase them elsewhere.

The useful comparison is total lifecycle value and cost:

• Internal labor and account management.
• Software and telephony.
• Integration and maintenance.
• Source-review and monitoring work.
• Collections and payment exposure.
• Dispute and reconciliation effort.
• Replacement access when a partner closes or fails.

A direct relationship may remove an explicit spread while increasing internal workload and concentration. A broker may retain economics for relationship access and coordination. An exchange may retain economics for routing, records, settlement, and market access while creating shared-platform dependency.

Do not compare buyer price with publisher payout and assume the difference is pure profit. The two amounts are distinct, and the difference may fund real work, losses, support, and infrastructure. It may still be commercially unattractive, but it should be judged against the responsibilities and performance actually delivered.

Failure domains and accountability

Every model should answer the same incident question:

When something fails, who contains it, investigates it, communicates it, corrects it, and bears the applicable cost?

Four failure domains recur.

Accountability should follow control.

A publisher should not be blamed for a buyer queue failure. A buyer should not be expected to investigate an upstream source it cannot identify. A broker should not claim to have reviewed traffic it cannot pause or trace. An exchange should not call a route “controlled” when its settings are not enforced in the live path.

The contract should assign commercial liability, but the operating model also needs practical ownership: who has the records, access, authority, and response duty needed to solve the problem.

Decision criteria for buyers and publishers

A model-selection decision should be documented before volume scales.

Buyer checklist

A buyer should be able to answer:

• Who is the legal counterparty, and who actually controls each source?
• Are sub-publishers allowed, identified internally, and subject to change control?
• Can the source be recognized in call, routing, performance, dispute, and invoice records?
• Who reviews the publisher, source, creative, landing page, transfer process, and caller journey?
• Can caps, schedules, geography, concurrency, destination health, duplicates, and source permissions be enforced live?
• Who maintains the integration and monitors failures?
• Are answer, connection, qualification, conversion, billability, and buyer handling measured separately?
• How quickly does source-level feedback return?
• Which calls can be disputed, what evidence is required, and who decides?
• Can invoice lines be traced to the relevant calls and adjustments?
• How quickly can one source be paused or replaced?
• What concentration remains in the publisher, broker, exchange, or downstream buyer base?

Publisher checklist

A publisher should be able to answer:

• Who owes the publisher payout?
• Is payment contingent on downstream buyer collection?
• Which event makes a call payable, and who can reverse it?
• Is the buyer or intermediary financially and operationally credible?
• Does one integration reach one buyer or several genuinely available buyers?
• What happens when a buyer is capped, closed, unhealthy, or unresponsive?
• Are bids, fixed payouts, reservations, rejection reasons, and failover behavior clear?
• What source information reaches the buyer, and how is circumvention risk managed?
• Can the operator hold the source accountable internally without exposing unrelated confidential relationships?
• Are disputes call-specific, timely, and supported by records?
• Can payout reports and adjustments be reconciled to call-level events?
• Can a successful source scale without being blended with unrelated traffic?
• Does diversification reduce risk, or merely move all exposure to one intermediary?

A critique of broad, weakly governed access appears in Why Open Marketplaces Can Break Down in Call Buying. The separate comparison of curated supply and open supply addresses governance. The decision here is about relationship structure: which party performs the work and carries the dependency for a particular campaign.

Hybrid arrangements are often the strongest answer

A mature buyer may use all three models.

For example:

• Two direct publishers provide strategic core volume.
• A broker provides specialized transfer supply in one vertical.
• An exchange provides incremental inbound sources and RTB routing.
• The buyer preserves separate source IDs, caps, reports, and economics for each path.

A mature publisher may also use several paths:

• One direct buyer for a high-performing owned-and-operated source.
• A broker for relationship access in a new vertical.
• An exchange for overflow, buyer diversification, or real-time demand discovery.

Hybrid design works only when the paths remain explainable.

The operation should be able to answer:

• Which source originated the call?
• Which relationship brought it to the buyer?
• Which platform made the routing decision?
• Which party set the commercial rule?
• Which buyer target received it?
• Which party owes the buyer invoice?
• Which party owes the publisher payout?
• Which record governs a dispute?
• Which failure domain caused the problem?

If those answers disappear after several layers are combined, the hybrid model becomes blended opacity.

How Dependable Calls is approaching the model

Dependable Calls is building a controlled, operator-led exchange rather than an unrestricted directory of buyers and publishers.

The current implementation includes:

• A source registry that separates the source from the broader publisher account.
• An operator-controlled offer gate that determines which sources are available to a buyer.
• Per-target buyer enablement for offered sources.
• Live routing checks that require both the operator offer and buyer enablement in curated mode.
• Buyer-facing source pseudonyms backed by complete internal publisher relationships.
• Buyer-specific source performance views.
• Operator-published benchmark fields.
• Curated sample recordings, creatives, and landing-page assets.
• Source administration, audit records, and scoped buyer access.

That is the technical direction behind curated source enablement: Dependable Calls first decides which reviewed sources are appropriate to offer, and the buyer then decides which offered sources to enable for a target or call path.

It does not make the exchange universally better than a direct relationship or a broker.

A direct strategic publisher may remain the cleanest answer for a buyer. A broker with strong relationships and operating discipline may add substantial value. An exchange is useful only when its routing, records, permissions, and financial administration solve real problems.

The implemented source controls are also not the same as proven operational maturity at scale. Live campaign behavior, buyer usage, source-review consistency, dispute workflows, payment performance, and long-term reliability remain subject to beta validation and continued hardening.

The goal is not to add a layer for its own sake.

The goal is to make each layer’s responsibility visible, controlled, and supportable.

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