saascode
marketing & growth·run 160 · Jun 2026

Channelvoice

An agency analytics layer that distinguishes source-supported inbound AI referrals and probabilistic call-endpoint classifications, preserves consent and disclosure, and measures connection and outcome states without optimizing deceptive voices or bypassing consumer agents.

Genesis score6.27/10
Make Channelvoice real.0/500
500 more votes and Channelvoice is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
ConfirmedInbound AI referral product
UnverifiedCall-shield adoption at scale
The case

Agencies are beginning to see two different AI-mediated channels: visitors referred by AI assistants and outbound voice systems that may encounter automated consumer or business endpoints. The supplied research confirms a live inbound AI-referral attribution product with an entry tier and a reported conversion observation. It also corrects the original outbound premise: the cited consumer product delegates calls from users to companies; it is not currently an inbound call shield blocking business-to-consumer AI calls. Therefore the AI-versus-AI direction is plausible, but call-shield penetration at scale is unverified. Channelvoice must keep the halves separate. For inbound web visits, it records referral and landing evidence, identity and consent limits, downstream events, and attribution uncertainty. For outbound calls already lawful and authorized, it classifies endpoint behavior as human, voicemail, automated attendant, consumer agent, unknown, or mixed using disclosed evidence and confidence. It never attempts to bypass a screener, disguise automation, imitate a human, vary persona to exploit protected or sensitive traits, or infer that an automated endpoint caused a lost sale. Call authority, attempt, connection, endpoint classification, disclosure, conversation, human-reviewed qualification, transfer, appointment, sale, refund, and causal outcome remain distinct. One of two referenced API capabilities remains unverified. The moat is a timing bet and must not be presented as established consumer adoption.

Who pays — and why

The performance-marketing, analytics, growth, or revenue-operations lead at an agency managing permitted voice outreach and web attribution for several clients.

Market signalValidate by isolated client workspaces, authorized web sources, lawful call attempts, minutes, destinations, attribution windows, reviewer seats, and retained evidenceThe supplied $29 monthly inbound-attribution tier and adjacent infrastructure costs are observed market references, not fixed product pricing
What it unlocks
A tenant-isolated channel record separating source evidence, referral class, landing session, consent state, downstream events, attribution window, alternatives, confidence, and correction.
A lawful call ledger preserving contact authority, caller and AI disclosure, voice rights, attempt, endpoint evidence, probabilistic classification, conversation state, suppression, review, and correction.
An outcome model distinguishing referral or call, engagement, qualified handoff, appointment, opportunity, sale, payment, refund, model credit, and incrementality evidence.
How Genesis scored it
6.27across seven criteria
tension 6temporal 7blindspot 5buyer 8leverage 6convergence 5why-not 6
8
Buyer persona

Agency performance and revenue-operations teams are actionable, though client volume and budget need validation.

7
Temporal window

Confirmed inbound referral growth and consumer-delegated calls support a directional window, not a hard adoption fact.

5
Convergence

One cross-reference and three inbound links support moderate convergence.

Why it scored well

A clear agency buyer and confirmed inbound referral product support one half of the opportunity, while endpoint classification is a plausible emerging measurement gap.

What's holding it back

The call-shield premise is unverified at scale, one capability remains unverified, outbound calls carry major consent risk, managed integration weakens leverage, and incumbents can add similar analytics.

Signals detected3 sources crossed
SignalCompetitor research

SignalMarket research

SignalOriginal premise

Direction briefchannelvoice.md
channelvoice.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.