Bring your own Twilio: what no markup means

WorkDial is a Salesforce-native computer-telephony integration (CTI) platform that runs telephony on your own Twilio account, billed at carrier cost with no markup. You hold two separate bills: WorkDial charges for the software per user, and Twilio charges for the minutes directly. The call data becomes native Salesforce records, and the audio recording stays in your own Twilio.

What does “bring your own Twilio” mean?

Bring your own account (BYOA) means WorkDial places and receives calls using Twilio credentials you own, not a phone network WorkDial resells to you. You sign in to Twilio, you hold the numbers, and Twilio bills you for usage. WorkDial uses that account to dial, connect, and record, then writes the structured result into Salesforce.

This is the opposite of how bolt-on dialers usually price telephony. Many integrated CTI tools fold minutes into the per-seat price and take a margin on every minute you use. The margin is rarely itemized, so you cannot read what the carrier charged versus what the vendor added. BYOA removes that layer: the minutes cost what the carrier charges, and you can see it.

Who bills you, for what

There are two bills, and the separation is the point.

WorkDial earns from the subscription, not from a per-minute margin. That is why telephony is a separate line you read on your own Twilio invoice. Your calling cost tracks the carrier rate, and your software cost is fixed and predictable. Neither one hides inside the other.

Why carrier-cost telephony matters at volume

At low call volume, a per-minute markup is small enough to ignore. At high volume, it becomes the larger half of the conversation. When minutes carry a vendor margin, your telephony cost scales with that margin rather than with the carrier’s rate, so growth in call activity quietly inflates the part of the bill you cannot itemize.

BYOA changes the math. Because Twilio bills your account directly, you can negotiate carrier rates as your volume grows, move traffic on terms you set, and forecast cost from a rate you can read. A Salesforce dialer that runs many outbound calls per rep per day is exactly where this separation pays off, because the minute count is high and a hidden margin compounds across every seat.

Where does the recording live, and where does the call data live?

The audio recording stays in your own Twilio account; the structured call data becomes native Salesforce records. This is the honest version of data residency, and it is worth stating precisely. WorkDial keeps no recording store of its own. The carrier transport and the recording storage live in infrastructure you control through Twilio.

Meanwhile, every call writes to native Salesforce objects: call activity, dispositions, and the AI artifacts (transcripts, sentiment, summaries) land on objects in your org, not synced in from a vendor database. Other tools connect to Salesforce. WorkDial runs inside it. If you want the longer argument for why the structured record belongs on the platform, read why call data belongs in Salesforce.

So the split is clean: the call data is native in Salesforce, and the carrier transport and recording sit in your own Twilio. That is the model WorkDial commits to, and it is the model a Salesforce admin can verify against the objects in the org.

How telephony cost relates to the WorkDial subscription

Telephony cost is separate from the WorkDial subscription, and it does not change with your tier. Whether you are on Core, Professional, or Enterprise, the minutes are billed by Twilio at carrier rate. The tier determines the software capability you get inside Salesforce, including how much of the AI analysis is included. Pricing for those tiers lives on the pricing page rather than being restated here.

This separation also keeps the buying decision honest. You evaluate the Salesforce CTI architecture on its own terms, and you evaluate telephony cost on the carrier’s terms. Neither decision is bundled into the other, and neither hides a margin inside the other.

If the tool is supposed to manage your Salesforce communication, why does your communication data live somewhere else? BYOA is one half of WorkDial’s answer: the structured record is native in Salesforce, the recording stays in your account, and the minutes are billed to you at cost.

Get started

WorkDial connects to your Twilio account during setup and writes every call into Salesforce as native records, with no per-minute margin in between. Start a free trial to connect your account and run real calls, or view a demo if you want to see the native records written first.

Written by Nikhil Palliboina, Content Writer, WorkDial. WorkDial is built by the team behind ValueText, the Salesforce-native messaging platform, rated 4.97 stars across 100+ AppExchange reviews.