Skip to content
Loquent Loquent Dev Docs

Custom Twilio Account

Loquent supports two Twilio operating modes: a shared account managed by Loquent, and a Bring Your Own (BYO) mode where your organization connects its own Twilio credentials. This section covers the BYO mode in full.

Shared vs. BYO

Section titled “Shared vs. BYO”
Shared (Default)BYO
CredentialsLoquent’s Twilio accountYour Twilio account SID + Auth Token
Phone number ownershipLoquentYour account
BillingThrough LoquentDirectly from Twilio to you
Setup requiredNoneConnect credentials in Settings

When organization.byo_twilio = true, every Twilio API call — sending SMS, buying numbers, configuring webhooks — uses your account’s credentials. The shared account is never used as a fallback once BYO is enabled.

What Loquent Can and Cannot Do to Your Account

Section titled “What Loquent Can and Cannot Do to Your Account”

This is the most important thing to understand before connecting your account.

ActionDoes it change your Twilio account?
Saving your credentials❌ No — stored in Loquent’s DB only
Viewing settings / listing numbers❌ No — read-only API calls
Searching available phone numbers❌ No — read-only
Importing existing phone numbers❌ No — only copies metadata to Loquent
Syncing message history❌ No — read-only fetch
Setting up SMS event sink✅ Yes — creates an Event Sink + Subscription in your account
Buying a phone number✅ Yes — purchases number + sets its Voice URL
Configuring voice URL on an imported number✅ Yes — updates the number’s VoiceUrl in Twilio

Impact on Other Platforms

Section titled “Impact on Other Platforms”

If you’re using your Twilio phone numbers with another platform (e.g. a CRM, a PBX, or another messaging tool), here’s what you need to know:

Saving credentials — no impact. Nothing in Twilio changes.

Importing numbers — no impact. Loquent reads your number list but does not modify it.

Syncing message history — no impact. Read-only.

Setting up the SMS event sink — adds a new Event Sink and Subscription to your Twilio account. This routes SMS delivery status events to Loquent. It does not remove or modify any existing webhooks on your individual phone numbers.

Configuring the voice URL — this is the one operation that can affect your existing setup. When you set a phone number’s voice URL to point at Loquent, Twilio will route inbound calls on that number to Loquent instead of your previous handler. Loquent saves the previous VoiceUrl value (phone_number.previous_voice_url) before overwriting it.

Database Fields

Section titled “Database Fields”
-- On the organization table
twilio_account_sid  TEXT         -- Your BYO Account SID (e.g. ACxxx...)
twilio_auth_token   TEXT         -- Your BYO Auth Token
byo_twilio          BOOLEAN      -- true = BYO mode enabled


-- On the phone_number table
previous_voice_url  TEXT         -- Saved before Loquent sets its own Voice URL

Next Steps

Section titled “Next Steps”