Acceptable Use and Voice Compliance

1. Required calling basis

Only contact people where the partner or end customer has an applicable legal basis, permission or other documented authority. Purchased lists or scraped personal data are not automatically lawful.

2. Identity and AI disclosure

Calls must accurately identify the responsible business. Where required or appropriate, the workflow must disclose that the caller is interacting with an AI system and provide a human route.

3. Recording and transcription

Partners must configure recording and transcription notices based on all applicable participants’ locations. Do not enable recording by default where notice or consent is unresolved.

4. Do-not-call, opt-out and suppression

Partners must screen required registries, honor opt-outs promptly, preserve suppression records and avoid re-uploading suppressed recipients. Singapore campaigns must account for the national DNC Registry and applicable exemptions.

5. Hours, frequency and caller identity

Use local quiet hours, reasonable frequency caps and valid caller identity. Do not spoof numbers, conceal the responsible party or use misleading urgency.

6. Prohibited and high-risk use

7. Human escalation and testing

Every production workflow needs a defined exception path, test cases, authorized data fields, maximum retry behavior, owner and stop mechanism. Pilot success does not remove the need for ongoing monitoring.

8. Enforcement

Ring2 may investigate complaints, require evidence of consent or authority, throttle or suspend traffic, preserve relevant records and terminate serious or repeated violations under the signed agreement.

9. Country review

Before launch, the partner must complete a country-specific review covering telemarketing, AI disclosure, recording, privacy, data transfer, carrier and number requirements.