Workspace access
Authenticated workspaces and role-based access patterns let owners, admins, managers, reps and client-facing seats receive different levels of control.
Trust + responsible outbound
Enterprise operations need visible controls and visible limits.
Cupids Network separates platform controls, carrier requirements and market rules. The product can help a team operationalise access, suppression, data handling, calling and recording decisions, while customers remain responsible for the campaigns they run and the providers they connect.
Platform controls
Build the safeguards into the workflow.
CRM memory + suppression
Cupid is designed to preserve canonical lead history and workspace-level suppression so a new import or campaign does not silently erase prior DNC or contact context.
Calling + recording controls
Calling and recording settings are configurable because the correct operating rule can differ by market, provider, campaign and use case.
Protected provider connections
Provider credentials are intended to remain in protected server-side integration storage rather than being exposed as ordinary browser data.
Operational safeguards
Cupid can support suppression, permissions, retention, provider setup and recording processes. These are operational controls, not a universal legal-compliance guarantee.
Provider layer
BYO telephony gives control — not permission to ignore carrier policy.
Cupid can technically connect supported customer-controlled Twilio, Telnyx and Plivo accounts. Whether a specific calling method is permitted is a separate provider-policy question. Number ownership, variable usage, verification, traffic quality and acceptable-use requirements remain with the provider account.
Twilio
Twilio remains an independent communications provider. Its current Voice guidance states that unsolicited phone calls and unsolicited marketing are not allowed uses. Customers using a Twilio-connected Cupid workspace should confirm that their traffic and use case fit Twilio's current Acceptable Use Policy, complete applicable business-identity and number-verification steps, and use Twilio Trust Hub / SHAKEN-STIR processes where relevant.
Review provider policyTelnyx
Telnyx remains an independent communications provider. Its current AUP lists auto-dialing/predictive-dialing as an improper or inappropriate use and also addresses unsolicited calls likely to provoke complaints, low answer-seizure rates, call-per-second thresholds and abandoned-call patterns. Do not treat a technical Cupid integration as provider approval for parallel or automated calling; obtain Telnyx confirmation for the intended use case.
Review provider policyPlivo
Plivo remains an independent communications provider. Its current AUP prohibits auto-dialing/predictive-dialing and also prohibits unsolicited or unwanted calls and marketing. A technical Cupid connection does not mean automated or cold-outbound traffic is permitted. Confirm the intended use case with Plivo before production traffic and follow its DNC, identity and traffic-quality requirements.
Review provider policyProvider approval is an independent launch gate: local law, Cupid feature availability and provider permission are three different questions. Twilio's current Voice guidance restricts unsolicited marketing, while the current Telnyx and Plivo AUPs explicitly restrict auto/predictive dialing. Do not enable a calling mode through a provider until the intended traffic is permitted under that provider's current terms or specifically approved for the account.
Market-aware operations
One outbound rule does not fit every country or channel.
These summaries are operating prompts, not legal advice. They are intentionally conservative and should be paired with qualified counsel for the markets, data sources and channels your company actually uses.
United Kingdom
PECR + UK GDPR controls
For live B2B marketing calls, teams should determine whether the number is registered with TPS or CTPS, respect prior objections, identify the caller and make a contact number available. Automated marketing calls generally require specific consent. Where personal data is processed, UK GDPR still applies and the team needs an appropriate lawful basis, transparency and objection handling.
- TPS / CTPS screening
- Previous-objection and suppression checks
- Caller identity and displayed contact number
- Lawful-basis and transparency process
- Separate treatment for live calls, automated calls and electronic mail
United States
TCPA, FCC + DNC controls
US requirements depend heavily on call type, destination, technology, recipient and state law. Artificial or prerecorded voice telemarketing carries stricter consent requirements, and the FCC has confirmed that AI-generated voices fall within artificial/prerecorded voice restrictions. Teams should also maintain company-specific DNC handling and determine whether federal or state telemarketing requirements apply to the campaign.
- Human-live versus artificial/prerecorded voice distinction
- Consent records where required
- Entity-specific DNC suppression
- Federal and state rule review
- Caller identity and provider trust setup
South Africa
POPIA + Section 69 controls
POPIA regulates direct marketing and gives data subjects objection rights. Section 69 is particularly relevant to unsolicited electronic direct marketing, including automatic calling machines, SMS and email, and sets consent/customer conditions plus sender-identity and opt-out requirements. Teams should classify each channel correctly and document the basis on which it is used.
- Consent/customer-condition review for Section 69 channels
- Sender identity
- Simple opt-out handling
- Purpose and retention controls
- Objection and suppression records
What Cupid does not claim
Trust improves when the limits are explicit.
Not legal advice
Cupid can help implement operational processes and controls. Jurisdiction-specific legal interpretation belongs with qualified counsel.
No invented certification
Cupids Network will not state that it holds SOC 2, ISO, GDPR, HIPAA or another certification/status unless that claim is actually held, applicable and current.
No universal compliance guarantee
Campaign legality and provider acceptance depend on market, channel, data source, consent or other lawful basis, recording behaviour, traffic pattern and jurisdiction.
No hidden provider ownership claim
Twilio, Telnyx, Plivo and other third parties remain independent providers. Their terms, charges and enforcement decisions are not controlled by Cupid.
Data handling
Keep operational data tied to the workspace.
Contacts, activity, meetings, campaign context and integration references are organised by workspace. Access and retention settings should be configured around the customer's operating requirements, privacy notices and documented data process.
Before a production campaign
Run the launch checklist, not just the feature checklist.
Confirm provider approval/use-case fit, business identity, number ownership, suppression state, contact basis, calling hours, recording settings, opt-out handling and a controlled test path before turning on live volume.
Need to scope controls for a deployment?