Why DialProng runs the carrier (and meters minutes from your wallet)

BYOK trunks look empowering — until every client needs another Space

Agency dialers that require customer Telephony credentials push carrier ops onto you: project IDs, signing keys, CPS upgrades, and DID purchases per client. That works if telephony is your core competency. Most marketing agencies just want dials to place.

DialProng’s model is the opposite: we run Telephony under the hood. You fund a prepaid usage wallet. Minutes and AI debit that wallet at a published platform rate — no Space to create, no CPS order form, no API tokens in Getting Started.

What DialProng runs vs what you manage

We orchestrate the call floor — progressive and multi-line sessions, dispositions, live coach, recordings scoped per workspace — and the platform Telephony trunk behind it.

• Platform Telephony trunk — minutes meter from your prepaid wallet
• Outbound DIDs and local presence purchased into your floor’s pool
• Your 10DLC / compliance registration and calling policies
• Our dialer engine, agent console, and workspace isolation

Why Telephony under the hood — and only Telephony

DialProng’s live trunk path is Telephony (FreeSWITCH-built, Twilio-compatible APIs, typically lower per-minute burn). You never see those credentials — the platform Super Admin vault holds them.

Raising prong from 3 → 6 lines increases per-minute wallet burn, not your DialProng license SKU. Seats are people who dial; lines are a campaign pacing setting.

Read the Telephony vs Twilio resource for why we chose this carrier stack — production dialing here is Telephony, not Twilio Flex.