Twilio and Conduyt
Twilio is the telephony layer behind Conduyt's browser softphone, power dialer and SMS. You connect your own Twilio account, so your numbers stay yours and usage is billed transparently by Twilio, while Conduyt handles the dialing, the compliance guards and the conversation history.
What makes it different
A dialer in the browser
Agents call from Smart Views through a WebRTC softphone. No desk phones, no separate dialer app; the call, the notes and the disposition live on the contact record.
SMS and drip campaigns
Outbound texts, templates and drip automations send through your Twilio numbers, and inbound replies route back to the right contact and can trigger automations.
Compliance guards on every auto-dial
Before smart dialing places a call it checks DNC status, litigator lists, opt-outs, cooldowns, attempt caps and calling windows, per contact, every time.
What you need in place first
What moves, and which way
| Direction | What moves | Notes |
|---|---|---|
| Conduyt to Twilio | Outbound messages and call requests: the To and From numbers, the message body, and the dialing instructions behind manual, power and smart dialing. | Before smart dialing places a call, Conduyt checks DNC status, litigator lists, opt-outs, cooldowns, attempt caps and calling windows on that contact. |
| Twilio to Conduyt | Inbound SMS. Twilio posts a form-encoded request carrying MessageSid, From, To, Body, NumMedia and NumSegments to the webhook URL configured for the number or Messaging Service. | Vendor source: Twilio incoming message webhook request. Conduyt matches the From number to a contact so the reply lands on the right timeline. |
| Twilio to Conduyt | Outbound delivery status. Twilio raises status callbacks across the lifecycle of an outgoing message, which is what turns a sent text into a delivered or failed one on the record. | Same source. Inbound webhooks are signature-verified before Conduyt accepts them. |
| Twilio console only | Buying numbers, porting numbers and regulatory registration. | None of this passes through Conduyt. Your carrier relationship and your number inventory stay under your control. |
3 steps, about ten minutes
Connect your Twilio account
Settings, then Twilio. Paste your Account SID and Auth Token, then run the connection test.
Add the voice credentials
TwiML App SID, API Key SID and API Secret. All three are required for the softphone, even though SMS works without them.
Point your TwiML App at Conduyt
In the Twilio console, set the TwiML App's Voice Request URL to your Conduyt dialer endpoint, then place a test call.
Twilio usage, numbers and carrier fees are billed by Twilio. The Conduyt side of the connection adds no cost on any plan.
What it does not do
The details
Common questions
Do I need my own Twilio account?
Yes. Twilio is a connected app: you create or reuse your own Twilio account and connect it to Conduyt. That keeps your phone numbers portable, your telephony bill transparent, and your carrier relationship under your control.
What does the Twilio integration power inside Conduyt?
The browser softphone, manual and smart dialing from Smart Views, outbound SMS and drip campaigns, and inbound replies routed to the contact record. Calls and texts land on the same timeline as email, so the history stays in one place.
Why does SMS work but the dialer says it is not configured?
Because voice needs three more credentials than SMS: the TwiML App SID, API Key SID and API Secret, plus the Voice URL set in your Twilio console. If any of those are missing the softphone cannot register, even while texting works fine.
Does smart dialing respect do-not-call rules?
Yes. Every automated dial passes a per-contact eligibility check first: DNC status, litigator lists, opt-outs, cooldown periods, maximum attempts and calling windows. Admins also control which views are enabled for auto-dialing at all.
Ready to try Conduyt?
20-day free trial. No credit card required.
