AI engineering · Product
TwoRing & Switchboard.
An AI receptionist that answers within two rings — and the self-hosted voice engine we are building so the whole stack runs on our own terms.
The product
A receptionist that never lets a call go to voicemail.
tworing.ai is a 24/7 AI receptionist service for trade businesses — HVAC, plumbing, electrical, lawn care, real estate. A missed call in the trades is usually a lost job: the caller simply dials the next company on the list. TwoRing answers forwarded calls within two rings, books appointments into the customer's calendar mid-call, and emails a summary of every lead.
Each month, customers get a “Found Money Report”: the calls that would have gone to voicemail, what they were worth, and what got booked instead. Canadian-built, CASL-compliant, and month-to-month — the product has to earn its keep every thirty days.
The engine
Why we are replacing the hosted stack.
TwoRing launched on a hosted voice-AI orchestrator. It worked, but it owned the most important minutes of every customer relationship. Switchboard is our replacement: an internal voice platform designed as if it were a public product — API-first and multi-tenant — but consumed by our own projects first.
Self-hosted media stack
LiveKit for real-time media and SIP telephony, running on infrastructure we operate. The hosted orchestration layer it replaces was joined to our platform by exactly two HTTP contracts — get those right and nothing else has to change.
Every provider has an exit
Speech-to-text, the LLM, and text-to-speech each sit behind an adapter with mid-call failover. Cloud primaries (Deepgram, Claude, ElevenLabs, Cartesia) are backed by local options like Whisper and Ollama, so no single vendor outage can take the phones down.
Calls leave a paper trail
Every call is recorded, transcribed, and summarized into the lead record automatically. The same instinct as our consulting work: if it is not written down, it did not happen.
Compliance is a gate, not a memo
Outbound dialing passes through an enforced compliance check before a call is ever placed — CASL-compliant by construction, not by policy document.
What it proves
Integration work under the harshest conditions.
Building a telephony platform is integration work at its least forgiving: real-time audio, third-party APIs that must fail over mid-call, and customers who judge you one ring at a time. The patterns Switchboard forces us to get right — provider abstractions, durable webhooks, recording and reconciliation — are the same ones we apply to payroll integrations and HRIS rescues, where the tolerance for dropped messages is exactly as low.