Voice platform
Carrier-grade calling with bring-your-own providers — all under one login.
- ·Bring multiple providers for each channel — switch carriers per DID
- ·Native browser softphone via WebRTC (Telnyx) and SIP (DIDLogic)
- ·Per-DID assignment to agents with sticky routing
- ·Cooldown enforcement + DNC pre-flight before every dial
- ·Recordings + transcripts attached to the lead timeline
- ·Cross-tenant isolation enforced down to the SQL layer
Why most call centers stitch 4 vendors together
A typical outbound team uses Aircall (or JustCall) for clicks, Twilio Studio for IVR, an external CRM for notes, and a separate analytics tool for the leaderboard. Each vendor has a different pricing model, a different login, and zero cross-data — agents can't see which DID a lead was last called from, which kills connect rates.
- Agents dial from one tool, take notes in another, see analytics in a third
- Per-DID routing is impossible — every call goes through the same number
- Recordings live in the carrier's portal, not next to the lead
- Compliance lives in spreadsheets, not in the dial gate
The detail.
One platform, three carriers
Telnyx for the cleanest US/EU coverage, DIDLogic for cost-effective international, FreJun for India-native operations. Each DID is tagged with its provider and routes through the right SDK automatically — your agents never see the difference. Mix providers per workspace; pricing flows through verbatim with no Autocloz markup.
Compliance baked in, not bolted on
Every outbound dial passes through the same gate: workspace DNC, lead-level DNC, country-specific quiet hours, per-lead cooldown, and (for India) DLT registration lookup. Agents see the policy decision before the dial fires; compliance officers see the audit trail in /call/cdr.
Carrier-credential honesty
When carrier credentials are missing, Autocloz refuses to dial with a clear error code (TELNYX_NOT_CONFIGURED, FREJUN_NOT_CONNECTED, DIDLOGIC_NOT_CONFIGURED) — never fabricates a fake successful call row. That same discipline runs across webhook ingestion: signature verification is mandatory in production, opt-in in dev.
vs. Aircall + Twilio Studio + external CRM stack
The honest comparison — what changes when you switch.
Four things you won’t find elsewhere.
Bring-your-own providers
Pick the right carrier per geography and per use case — pricing flows through with no Autocloz markup. Your carrier bill is your carrier bill.
DID-aware everything
Per-DID assignment, sticky-agent routing, country-match caller-ID. Agents see which DID a lead was last called from — connect rate climbs the moment that's visible.
Carrier-credential honesty
Missing credentials → 409 with explicit code (TELNYX_NOT_CONFIGURED, FREJUN_NOT_CONNECTED). Never a fabricated success row. The compliance officer can audit, not guess.
One audit log, every action
Click-to-call · cooldown override · DNC bypass · IVR change · DID re-assignment — all written to audit:voice with operator + reason. Full forensic trail for the compliance review.
Bring your own — or pick from the supported set.
A real sequence using this channel — day by day.
- SetupConnect carrierAdd API key (Telnyx) or OAuth (FreJun) — done in 60s
- SetupAdd DIDsBulk-import via CSV or one-at-a-time; assign agents
- DailyClick-to-callLead drawer → green dial button → softphone rings
- DailyInbound IVRCaller hits your IVR menu, routes to agent, recording starts
- WeeklyVoice reportsConnect-rate / cost / quality buckets; CSV-export to your BI
How teams actually use this.
12-agent outbound team migrating from Aircall + spreadsheet CRM
Operations imports DIDs across multiple carriers, assigns per-agent. Agents dial from the lead drawer in /leads instead of the Aircall app. Country-match caller-ID strategy means an Indian lead hears an Indian DID; an APAC lead hears the APAC DID. Connect rate doubles in two weeks because the displayed number matches the recipient's region.
Inbound IVR replacing Twilio Studio
The visual IVR builder maps node-for-node from the Studio flow — menu → dtmf_route → transfer_to_did → voicemail. The simulator validates the flow offline (no carrier minutes) before the IVR goes live. The Studio subscription gets cancelled the same week.
Compliance officer auditing 6 months of dials
Filter /call/cdr by date range and outcome. Each row shows the lead, DID, agent, outcome (connected · voicemail_drop · dnc_blocked · cooldown_blocked), and any force-flag overrides. Recording URL and transcript link from the same row. Export to CSV, send to the regulator — done.
“We dropped Aircall + Twilio Studio + a separate CRM and put everything on Autocloz voice. Connect rate went from 9% to 18% because agents finally saw which DID was burned.”
Specific to this channel.
Do I need to bring my own phone numbers?+
Yes — Autocloz is a 'bring your own carrier' platform. Buy DIDs on Telnyx or DIDLogic or FreJun, paste credentials into Voice Settings, and assign DIDs to agents. We never resell carrier minutes.
Can I record calls?+
Yes, where legal. Two-party-consent jurisdictions (CA, FL, IL, etc.) get an auto-prepended consent line; one-party consent jurisdictions skip it. Recordings stream from the carrier directly — Autocloz stores only the URL + transcript metadata.
What about TCPA / DLT compliance?+
Per-workspace DNC + lead-level DNC checked before every dial; country-specific quiet hours enforced; India DLT registration is mandatory before we accept Indian numbers. The /call/cdr surface keeps the full audit trail.
Can my agents use the browser softphone?+
Yes — Telnyx WebRTC and DIDLogic SIP are both wired into the in-page softphone. FreJun uses per-agent OAuth and routes through the FreJun softphone; agents click Connect once and are reachable.
The full story.
Voice infrastructure for outbound is the surface most SaaS sales platforms duck. Building it well requires WebRTC for the browser softphone, SIP integration for hardphones, TeXML or equivalent for IVR runtime, recording pipelines that tie back to leads, and per-country compliance handling (TCPA in the US, DLT in India, GDPR in the EU). Most platforms outsource voice to Aircall or JustCall and bolt the rest together with Zapier. Autocloz built voice native — all 17 voice routes run on the main FastAPI, share the same auth, the same DNC list, and the same audit log as the rest of the platform.
Bring-your-own carrier is non-negotiable for serious outbound teams. Carrier markups (especially on per-minute rates) destroy unit economics at scale; geographic coverage is uneven (a US-only carrier is useless for a team selling into India); compliance regimes differ per country. Autocloz's voice stack is provider-agnostic — Telnyx for clean US/EU coverage with WebRTC softphone, DIDLogic for cost-effective international SIP, FreJun for India-native operations with per-agent OAuth. Each DID is tagged with its provider and the dispatcher routes through the right SDK automatically. Mix and match per workspace; the agent never sees the difference.
DID-aware routing is the connect-rate lever most teams miss. When a lead in Mumbai sees an Indian DID ring, they pick up. When the same lead sees a +1-415 number, they reject the call. Autocloz's country-match strategy picks an org-owned DID with the same country code as the lead automatically. agent_did sticks the same agent's primary DID to a known lead so the recipient recognises the number; campaign_did honours per-campaign overrides; sticky-agent routing pairs repeat calls to the same agent so prior context is preserved. The connect-rate uplift across our beta cohort averaged +7-9 percentage points after enabling country-match.
Carrier-credential honesty is the discipline that separates Autocloz from most call platforms. When carrier credentials are missing or invalid, every Autocloz endpoint returns 409 with an explicit error code — TELNYX_NOT_CONFIGURED, FREJUN_NOT_CONNECTED, DIDLOGIC_NOT_CONFIGURED. We never fabricate a successful call row to make the dashboard look healthy. The same discipline runs across webhook ingestion: signature verification is mandatory in production, opt-in in dev. The result is an operator surface that tells the truth about what's wired and what isn't — which is the only way a compliance officer can audit, not guess.