Sales Engineering Platform · 2026

Custom Cold-Calling Dialer

A full outbound-calling product: browser-based WebRTC calling and phone-bridge calling side by side, Telnyx-verified webhooks, call recording to Supabase Storage, CSV/XLS/XLSX lead ingestion, dispositions, callback scheduling, and a role-gated admin dashboard.

GitHub

Lead list (CSV / XLS / XLSX)
  |
Lead queue -- dispositions -- callback scheduling
  |
Phone bridge   /   Browser WebRTC
        \           /
     Telnyx (server-issued call credentials)
           |
  Call recording -> Supabase Storage
           |
  Admin dashboard (Postgres RLS-scoped)

Problem

Outbound sales teams needed one tool that could place calls either through a physical phone bridge or straight from the browser, without exposing calling credentials to client-side JavaScript, while tracking every lead through to a disposition.

Architecture

Google OAuth gates access; an authenticated API route issues short-lived WebRTC credentials so the browser dialer never holds a long-lived secret. Lead files (CSV/XLS/XLSX) are ingested and paginated server-side to work around Supabase’s row cap on large lists. Calls route through Telnyx with server-side webhook signature verification, recordings land in Supabase Storage, and Postgres row-level security scopes every table to the owning user.

My Contribution

Built the calling core (Telnyx bridge + WebRTC), the credential-issuing endpoint, the paginated lead importer, and the admin dashboard with recordings, dispositions, and callback scheduling.

Outcome

In active use for real outbound calling workflows, replacing a manual phone-and-spreadsheet process.

Next.jsTypeScriptTelnyxWebRTCSupabasePostgres RLS