How is data security handled?
Tokens and credentials live inside a hardware-backed secret store with audit logging on every read. The Twilio adapter runs on isolated workers with deny-by-default egress, and every message is replayable from a tamper-evident journal for downstream forensics.
What does pricing look like?
Implementation is fixed-fee with a $0-until-live guarantee for Fresno, California. After go-live, the Twilio adapter runs on a flat monthly run-rate sized to message volume — no per-API-call gotchas, no per-seat surcharges, and a one-page exit clause.
Can the Twilio adapter handle our custom fields?
On first connection the adapter discovers every custom field, custom object and custom workflow inside your Twilio tenant and presents them as first-class mappings — you decide which to mirror, which to ignore, and which to enrich.
How long does the Twilio integration take to ship?
Our standard window is thirty days from signed scope to live Twilio adapter in production, plus a one-week monitored stabilization phase. For Fresno, California, that includes a sandbox loop with your team, parallel-run reconciliation, and a documented runbook handed to your operations lead.
Does it work with our existing Twilio licenses?
Yes — the adapter rides on top of your existing Twilio subscription. We use service-principal or OAuth M2M credentials so the integration never burns a named-user seat and never pushes you into a higher tier.
Is this a packaged Twilio connector or a custom build?
It is a Connectify-owned adapter, not a third-party packaged connector. We maintain the code, we monitor the runtime, and the fields, hooks, and reconciliation rules are shaped to your exact data model — not a generic schema we hope matches.