Twilio
Teams with an existing Twilio relationship can plug it in as the carrier behind Strkr Messaging instead of using Strkr's default. SMS, MMS, voice, and compliance flows run the same, billed through your Twilio account instead of Strkr Messaging seat pricing.
Everything Twilio does inside Strkr.
- BYO Twilio account connection
- Use existing numbers and compliance records
- Same SMS/MMS surface in Strkr
- Voice bridging through Twilio Voice
- Independent billing per Twilio account
Native code, not a shim.
OAuth where available
Twilio will ship with a native OAuth flow when it lands. No pasted credentials for admins to rotate manually.
KMS-encrypted tokens
Access and refresh tokens are envelope-encrypted at rest using a dedicated customer-managed KMS key. Decryption only happens in Lambda memory during an active API call; plaintext tokens never land in a log.
Shared by the workspace
A workspace admin connects Twilio once; every teammate uses the shared connection without re-authenticating.
Disconnect at any time
Admins or users can disconnect Twilio from inside Strkr. Stored tokens are deleted and the provider's revocation endpoint is called within 24 hours.
Twilio is on the roadmap.
We ship integrations as first-class native code, which takes a little longer than a Zapier shim. If Twilio is a dealbreaker for your evaluation, reply to the welcome email after you start a trial and we'll flag it to the roadmap.