Telnyx-connected calling

Use Telnyx for approved telephony workflows. Use Cupid for the CRM and outbound operating layer.

Cupid supports a customer-connected Telnyx path so teams can keep the carrier relationship visible while using Cupid for CRM, campaign context, enrichment, follow-up and booking. Calling modes must still fit the customer's Telnyx agreement and current acceptable-use policy.

Customer-controlled provider

Keep the Telnyx account, numbers and provider usage visible while Cupid manages the sales workflow around the connection.

Provider approval before automation

Telnyx's published AUP currently lists auto-dialing and predictive-dialing as improper or inappropriate uses. Do not enable a Cupid automated or parallel calling mode through Telnyx unless Telnyx has confirmed that the specific use case and account are permitted.

Data and follow-up in one place

Magic Enrich, contact history, outcomes, callbacks, meetings and multichannel follow-up stay around the same lead.

Provider choice

Cupid keeps the sales operating layer separate from the carrier so teams can choose a provider whose terms and coverage fit the intended traffic.

Provider setup

Treat provider approval as a launch gate

Configure the Telnyx account, numbers, identity and calling profile for the intended traffic, then confirm that the planned calling method is permitted before production launch.

  • Provider account and credentials
  • Number ownership and caller identity
  • Calling profile and routing
  • Written provider confirmation where the use case is ambiguous

Traffic quality

Low answer rates and abandoned calls matter

Telnyx's AUP addresses unsolicited calling likely to cause complaints, low answer-seizure rates, call-per-second thresholds and abandoned-call patterns. Those are operating constraints, not settings Cupid can waive.

  • Acceptable-use review
  • Traffic-quality monitoring
  • Caller identity controls
  • Abandoned-call and answer-rate monitoring

Cupid layer

Keep the sales operation above the carrier

Cupid turns an approved provider connection into a broader rep and manager workflow.

  • CRM and lead history
  • Campaign and callback workflows
  • Magic Enrich
  • One-click meeting booking and follow-up

Buyer value

Why teams consolidate this into Cupid

Compare providers

Select the carrier path whose current terms, coverage and commercial model fit the traffic you actually intend to run.

Review provider guardrails

Sales dialer

See Cupid's complete calling, CRM and meeting workflow. Calling-mode availability remains subject to the selected provider.

Explore sales dialer

Migration help

Move CRM and campaign data in stages before switching your team.

See migration

Responsible outbound

Telnyx is an independent provider. Its current AUP lists auto-dialing/predictive-dialing as an improper or inappropriate use and also regulates unsolicited calls, low answer rates and abandoned calls. A technical Cupid integration does not mean Telnyx has approved every Cupid calling mode. Obtain provider confirmation for the intended use case before production traffic.

Review trust controls

Questions

Make the buying decision with the operating model clear.

Is Cupid a Telnyx product?

No. Cupid is an independent outbound sales platform that can use a supported customer-controlled Telnyx account as the telephony layer.

Can I use Cupid parallel dialing with Telnyx?

Do not assume so. Telnyx's current published AUP lists auto-dialing and predictive-dialing as improper or inappropriate uses. Use parallel or other automated calling modes through Telnyx only if Telnyx has explicitly confirmed that your account and specific use case are permitted.

Can I switch carriers later?

Yes. Cupid is designed to keep the sales operating layer separate from the telephony provider, subject to the integrations and provider terms available at the time.

People. Data. Technology. Infrastructure.

Build the outbound operation you actually need.

Request access
Book a call