Twilio-connected dialer

Keep Twilio as the carrier layer. Add Cupid as the outbound operating layer.

Cupid is designed to connect supported customer-controlled Twilio accounts so teams can keep telephony ownership and provider visibility while using Cupid for CRM, campaigns, power and parallel dialing, follow-up and booking.

Request access See pricing

Provider ownership stays visible

Twilio remains the communications provider; Cupid supplies the outbound workflow around the account you connect.

No hidden minute bundle

Carrier rates, number rental, taxes and provider-specific charges remain subject to the Twilio account instead of being disguised as an unlimited calling promise.

CRM around the call

Contacts, companies, outcomes, callbacks, meetings and campaign history stay inside Cupid.

One provider is not a lock-in

Cupid's supported architecture also includes Telnyx and Plivo paths so the outbound operating model is not tied to a single carrier forever.

Setup

Connect the provider, then configure the workflow

The carrier connection is one layer of launch readiness. Business identity, numbers, routing, permissions and calling settings still need to be configured for the intended use case.

Customer-controlled provider credentials
Number and caller-ID setup
Workspace phone-line configuration
Controlled test calls before campaign launch

Trusted calling

Use Twilio's own trust and identity programs where applicable

Twilio documents SHAKEN/STIR onboarding and Trust Hub workflows for eligible outbound calling. Those provider steps remain separate from Cupid and should be completed in the Twilio account when relevant.

Business identity verification
Number ownership and authorization
SHAKEN/STIR setup where applicable
Provider policy and traffic-quality requirements

Cupid layer

Turn carrier connectivity into a sales workflow

Cupid adds the operating context that a raw communications API does not provide by itself.

Power and parallel dialing
Built-in CRM
Magic Enrich and data memory
One-click meeting booking and follow-up

Buyer value

Why teams consolidate this into Cupid

Compare Telnyx

Cupid also supports a Telnyx-connected path for teams that prefer that provider relationship.

See Telnyx path

See the sales dialer

Understand the full calling, CRM and follow-up workflow around the carrier connection.

Explore sales dialer

Review trust controls

See how Cupid separates platform controls, provider responsibilities and customer market requirements.

Open trust center

Responsible outbound

Twilio is an independent provider with its own acceptable-use, identity, traffic, number and regional requirements. Connecting Twilio to Cupid does not replace those obligations or the customer's responsibility to operate each campaign appropriately. Twilio and its marks are the property of their respective owner; no endorsement is implied.

Review trust controls

Questions

Make the buying decision with the operating model clear.

Is Cupid a Twilio product?

No. Cupid is an independent outbound sales platform. It can connect supported customer-controlled Twilio accounts as the telephony layer.

Does Cupid replace my Twilio account?

No. The BYO-provider model is designed so the customer keeps the provider account while Cupid manages the sales workflow around it.

Can I use another carrier later?

Cupid's current supported provider architecture includes Twilio, Telnyx and Plivo paths, subject to integration availability and configuration.

Who handles SHAKEN/STIR?

Twilio provides its own SHAKEN/STIR and Trust Hub onboarding. Cupid can surface operational guidance, but provider verification and attestation are handled through the carrier's processes.

People. Data. Technology. Infrastructure.

Build the outbound operation you actually need.

Request access