We Let an AI Phone Call Decide Who Gets Paid. Here's What That Taught Us About Trust.

Amir Faysal — Thu, 09 Jul 2026 08:59:05 +0000

Imagine this system:

A business locks money into escrow.
A creator shares a link; a stranger fills out a form.
An AI voice agent calls that stranger within minutes, asks a few qualifying questions, and scores the conversation.
If the AI says "hot lead" — money moves automatically. If not, nobody gets paid.

That's the core loop of the product I work on. And building it taught me more about trust in software than anything else I've shipped. Here are the five lessons — none of which are about AI models, and all of which are about humans.

1. When automation gates money, accuracy is a fairness metric, not a quality metric

A misclassified support ticket annoys someone. A misclassified qualification call takes money away from two people at once — the creator loses a payout for real work, and the business loses a real prospect.

The fix wasn't a better model. It was architecture that assumes the model is sometimes wrong:

Ambiguous outcomes never auto-reject — they route to a human review queue.
Every call is recorded and transcribed, so disputes are settled by evidence, not by whoever complains loudest.
Businesses choose their own trust level: Auto-Advance (AI decision pays instantly) or Manual Review (a human listens first).

If your automation touches money, budget as much engineering for the "what if it's wrong" path as for the happy path.

2. The most valuable feature we planned isn't a feature — it's a reason

Our top user friction, by a huge margin, wasn't bugs. It was silence. A lead rejected at 71% quality score with no explanation. A payout held with no visible cause. The system was right almost every time — and still felt unfair, because "no" without "why" reads as arbitrary.

So the biggest item on our roadmap is embarrassingly simple: reason codes on every automated adverse decision — cause, plain-language text, next step, appeal path. Support ticket categories map 1:1 to reason codes so we can measure whether explanations actually reduce confusion.

Lesson: users forgive wrong answers faster than unexplained ones.

3. Escrow is a UX feature wearing an accounting costume

Two-sided marketplaces die when one side stops believing they'll get paid. Our answer is boring and old: money is locked in before any work happens, and an append-only ledger draws it down per verified event.

The subtle part is what this does to interfaces. Because the ledger is append-only, we can show a brand three honest numbers at all times — used, reserved (for leads mid-pipeline), available — and show a creator that the campaign they're about to promote is actually funded. The trust isn't in a badge or a testimonial. It's in the data structure.

4. Fraud filtering is a negotiation with adversaries, not a checkbox

Click fraud adapts. Our validation runs five layers (IP dedup per ad per 24h, bot heuristics, velocity caps, device fingerprinting, engagement checks) and the honest engineering truth is: you never "solve" it, you instrument it. The metric we watch isn't "fraud blocked" going up or down — it's the ratio moving suddenly in either direction. Up means an attack; sharply down means our filters are decaying.

And one product decision mattered more than any detection technique: we show the fraud-blocked counter to users. Nothing builds confidence like a system that admits what it filtered out.

5. Compliance is the moat nobody wants to build (which is why it's a moat)

US telemarketing law now requires "one-to-one consent" — a consumer must agree to be contacted by a specific named company, not "marketing partners." So consent in our system isn't a checkbox boolean; it's an immutable record (brand name, timestamp, survey snapshot) created in the same transaction as the lead itself, exportable as an audit bundle with the call recording attached.

Encoding law into data models is tedious, unglamorous, and takes forever. That's precisely why competitors don't rush to copy it. If you're picking a differentiator as a small team: pick the boring one with legal gravity.

The one-sentence version

In systems that move money on automated decisions, trust isn't a marketing claim — it's a set of data structures: append-only ledgers, immutable consent records, recorded evidence, and a reason attached to every "no."

Disclosure: I work on ShareViral, the marketplace described above — brands buy AI-verified, consent-documented leads; creators of any size earn per verified result. Happy to go deeper on any of these five in the comments: the review-queue design, the ledger model, or how we're structuring reason codes.

What's your experience gating real money on automated decisions? I'd genuinely like to hear where it broke.

DEV Community: Amir Faysal

We Let an AI Phone Call Decide Who Gets Paid. Here's What That Taught Us About Trust.