RexaJump to a category
Telephony
The carriers calls run over. Rexa provisions a Telnyx number by default; connecting your own Telnyx, Twilio or Plivo account is the option, and you can run more than one at a time.
Telnyx
Telnyx is the carrier Rexa provisions numbers on by default, and one of three carriers you can connect your own account to instead.
Twilio
Twilio is one of three carriers you can bring your own account to instead of calling from the number Rexa provisions.
Plivo
Plivo is one of three carriers you can bring your own account to, with an optional Application ID that scopes which of your numbers Rexa can see.
Multi-carrier failover
Carrier failover is running more than one telecom provider on the same account so a call can be retried through a different carrier when the first one is unhealthy.
Messaging
Channels a campaign can use alongside the call. Both are bring-your-own by design: the provider bills you directly and Rexa never debits credits for a message.
Compliance data
Vendors the platform queries before a number is dialled. You do not connect these — the credentials are platform-level, so screening is standard rather than an add-on.
Automation
Connections to your own stack. These are built on signed webhooks and mid-call function calling rather than pre-built vendor connectors, and each page says exactly what that does and does not give you.
CRM
A CRM integration on Rexa is an HTTPS endpoint of yours that receives signed webhook events when a call reaches an outcome, plus optional functions the agent can call mid-conversation to read your records.
Calendar booking
Calendar booking on Rexa is a function the agent calls mid-conversation against your own scheduling endpoint, so slots are read and held while the caller is still on the line.
Automation platforms
An automation-platform integration means pointing a Rexa webhook endpoint at a Zapier, Make or n8n webhook trigger so call events start a no-code workflow.
Building the connection yourself
Anything not listed above connects the same way the Automation pages describe: subscribe an endpoint to the events you need, verify the signature, and write the outcome wherever it belongs. The reference material lives in the docs.