Robocall Mitigation Program

1. Provider and brand

MyProCaller is a service of CloudLink Solutions LLC. Traceback responses, mitigation actions, and compliance contacts under this program are handled by CloudLink Solutions LLC as the provider of the Service.

2. Regulatory filings

CloudLink Solutions LLC maintains robocall-mitigation related filings as required for its role in the call path, including registration in the FCC Robocall Mitigation Database (RMD) where applicable to our service posture. Authorized carriers and traceback partners may request current RMD registration identifiers and filing status by contacting the compliance channel below. Public marketing pages intentionally omit raw registration IDs to reduce spoofing of compliance contacts.

3. Compliance contact

Compliance / traceback contact: CloudLink Solutions LLC, Compliance Desk — email info@cloudlinksolutions.com with subject “Abuse / Traceback,” or use the Contact form topic Abuse / Traceback on myprocaller.com. Phone: +1 (774) 674-1597. Mailing address: 30 N Gould St #39151, Sheridan, WY 82801, USA.

Include E.164 calling and called numbers, UTC start/end times, and any industry case ID. See the Report Submission Policy for required fields and process.

4. Program goals

• Prevent customers from placing calls with Caller ID they do not own
• Keep toll-free numbers inbound-only (never outbound Caller ID)
• Require business verification before number purchase and outbound
• Detect abusive traffic quickly and pause outbound before carrier escalation
• Respond to traceback requests with customer identity and traffic evidence

5. Know-your-customer controls

New workspaces submit business identity and use-case information. Outbound voice/SMS and number purchasing stay locked until approval. We may reject or re-review accounts that present elevated risk or inconsistent use-case claims.

6. Technical call authentication posture

Voice and messaging delivery traverse third-party carrier platforms. On supported US routes, those upstream carriers implement network-level attestation such as STIR/SHAKEN. Our public posture is that attestation is performed by the carrier platforms that terminate traffic to the PSTN; MyProCaller enforces application-level policy so From identities map only to numbers assigned to the authenticated customer, and toll-free types cannot originate outbound calls as Caller ID. Customers and partners should treat our attestation level as dependent on the upstream carrier’s certificate and routing for each call.

7. Monitoring and mitigation

• Rate limits per customer (minute / hour / day) and concurrent-call caps (see Fair Use Policy)
• Warm-up limits for new accounts
• Alerts for short-call floods, single-destination floods, and error spikes
• Authority to auto-pause outbound and notify operations staff
• Privilege actions (pause, suspend, disable number) recorded in an audit log

8. Traceback readiness

When we receive a traceback or abuse case (calling number, called number, UTC window, case ID), we query call detail records, map traffic to the customer and KYC packet, pause outbound if needed, and reply with identity, traffic summary, and action taken. Our internal target is a first substantive response within approximately 30–60 minutes during staffing hours.

9. Customer responsibilities

Customers must not enable robocalling, spoofing, or unlawful telemarketing; must keep KYC information accurate; and must cooperate promptly with abuse investigations. Failure to cooperate is grounds for suspension.

10. Updates

We review this program as regulations, carrier requirements, and product controls evolve. Material public changes will be reflected on this page with an updated effective date.