Buyers who want deep channel coverage and operators planning larger ingests.
Whole-channel pricing, queueing, and manual review
Whole-channel requests are intentionally stricter than small recent packs because they touch indexing capacity, backlog admission, and higher delivery cost.
Key facts
- Whole-channel pricing is more likely to move into quote-only or manual-review modes.
- Transcript probing can queue work up to a cap and defer overflow as awaiting_queue_slot.
- Large channel scopes should be treated as operational work, not a guaranteed one-click checkout.
Why whole-channel is different
A whole-channel request is not just a bigger shopping cart. It can require transcript discovery across many videos, backlog coordination, and a materially larger export set.
Because of that, whole-channel pricing is governed more conservatively than small recent packs. The service keeps that distinction visible in purchase-mode labels so buyers are not surprised later.
How queueing affects the experience
The backend can queue transcript probes to prepare pricing and readiness. That queue has an admission cap so that one large request does not starve the rest of the system.
When the cap is exceeded, the request can be marked as awaiting_queue_slot. That is not a failure. It means the service is preserving operational truth instead of pretending the work already exists.
When manual review is the right answer
Manual review is the correct state when the scope is too large, too operationally uncertain, or not yet covered by a production rail. It is better to tell the buyer that explicitly than to overpromise an instant purchase path.
- Very large channels.
- Scopes that exceed automatic pricing bounds.
- Requests that require fresh indexing work before export can be trusted.
FAQ
Does a drained queue mean every historical transcript is already indexed?
Not necessarily. A queue can be drained while a more expensive full-corpus truth refresh is still pending. Queue health and full historical completeness are related but distinct questions.
Why would a whole-channel quote say manual review?
Because the service is explicitly protecting delivery truth. Large scopes can exceed automatic pricing or readiness bounds even when smaller packs are self-serve.
Should I expect the service to scrape a channel on demand?
Yes, the indexing path can accept on-demand channel work, but admission still depends on queue and pricing policy. On-demand does not guarantee immediate self-serve settlement.
Next steps
Related guides
How to buy transcript packs from the channel knowledge service
A factual guide to instant-buy offers, quote-only scopes, manual review, checkout, and transcript pack delivery.
Current payment rail status: what is live now vs planned
A truthful summary of the service payment rails, including the current live path and the difference between supported code and public production readiness.
Developer integration guide for transcript packs and paid delivery
A concise guide to the public service routes, ACP job flow, manifests, exports, and readiness checks.