Inspiration

Founder matching often ends at a score or chat introduction. The harder step is confirming whether both people want to collaborate, what to test, and when to begin. VibeHub existed before the hackathon as an explainable matching product. During the submission period, I added Founder Relay: a consent-first CALL-E workflow that turns a promising match into one concrete next step.

What it does

A user enters an explicitly authorized E.164 number, selects a region, and reviews a masked, no-call preview with the exact agent instructions. A live call stays disabled until the user confirms consent, types CALL ONCE, and provides the private demo access code.

The agent identifies itself as automated, checks that it is a good time, and ends immediately if the recipient declines. If they agree, it confirms collaboration interest, focus, and start timing, then returns a small structured result. VibeHub does not store the number or expose a raw transcript.

How I built it

Founder Relay uses Next.js 14, TypeScript, Prisma, PostgreSQL, and @call-e/calle. The server creates one CALL-E task and the authenticated client polls a separate status route.

Because calls are real-world side effects, the implementation restricts credentials to CALL-E's official HTTPS origin, validates destination and region, binds all call-defining fields into a stable idempotency fingerprint, reconciles ambiguous creates with the same key, verifies ownership, and applies a cooldown. Results appear only after terminal success, task completion, sufficient confidence, and strict schema validation; provider text is never returned raw.

Results and learning

I completed a real, consented Malaysia test call: 44 seconds for $0.05. The deployed app passed lint, TypeScript, production build, six no-call tests, and upstream validation. I also submitted a reusable TypeScript app in CALL-E's official repository PR #46 and resolved all reviewer security blockers.

The key lesson is that voice agents need stronger safeguards than text agents. Preview, consent, idempotency, destination controls, validation, masking, and redaction must operate as one system.

What's next

Next I would connect Founder Relay directly to VibeHub match context, add scheduled windows and more CALL-E-supported languages, and provide privacy-preserving workflow analytics for accelerators and founder networks.

Built With

Share this project:

Updates

posted an update

Founder Relay has been merged into CALL-E's official awesome-phone-call-agents repository through PR #46.

The final update adds complete handling for acceptance-ambiguous call creation outcomes, same-key reconciliation, and an explicit unresolved-state safeguard.

Log in or sign up for Devpost to join the conversation.