> ## Documentation Index
> Fetch the complete documentation index at: https://www.vobiz.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Global Compliance Overview — Voice & SMS Regulations by Country

> Vobiz compliance by market — India (TRAI, DLT, NDNC), US (TCPA, STIR/SHAKEN, 10DLC), EU (GDPR, ePrivacy), and global principles for AI voice agent and SMS deployments across 130+ countries.

Vobiz operates in 130+ countries. Each market has its own regulatory framework governing automated voice calls, AI-generated speech, and commercial SMS. This page summarises the frameworks that matter most for voice AI and business messaging deployments.

> [!NOTE]
>
> For country-specific deep dives, use the links in each section. For compliance questions specific to your deployment, contact [support@vobiz.ai](mailto:support@vobiz.ai).

## India

India has one of the world's most structured telecom compliance frameworks, administered by TRAI (Telecom Regulatory Authority of India) and DoT.

| Area | Framework | Key requirement |
| - | - | - |
| **Outbound voice — B2C** | TRAI TCCCPR | 140-series caller ID mandatory for all commercial outbound calls |
| **Outbound voice — financial/govt** | TRAI TCCCPR | 1600-series for RBI/SEBI/IRDAI regulated entities |
| **AI voice calls** | TCCCPR Third Amendment (Sep 2026) | Declaration of AI-initiated calls to originating provider required |
| **SMS — commercial** | TRAI DLT | Entity, sender ID, and every template must be pre-registered |
| **SMS — DND** | NDNC registry | Promotional SMS to DND-registered numbers is blocked |
| **Caller identity** | CNAP | Calling Name Presentation via telecom operator database |
| **Business verification** | KYC | Required to provision Indian numbers on Vobiz |

**Quiet hours**: Promotional calls and SMS — 9am to 9pm only. Transactional — any time.

**Violations**: First instance — outgoing services barred 15 days. Repeat — all SIP/PRI resources disconnected across all providers for 1 year, with blacklisting.

Detailed guides: [India Calling Regulations](https://www.vobiz.ai/docs/compliance/india/calling-regulations.md) · [KYC](https://www.vobiz.ai/docs/compliance/india/kyc.md) · [UCC / NDNC](https://www.vobiz.ai/docs/compliance/india/ucc.md) · [DLT Registration](https://www.vobiz.ai/docs/best-practices/dlt-registration.md) · [140-series acquisition](https://www.vobiz.ai/docs/best-practices/140-160-acquisition.md)

***

## United States

US compliance is governed by the FCC under the TCPA and the FTC for Do Not Call enforcement.

| Area | Framework | Key requirement |
| - | - | - |
| **Automated voice calls — marketing** | TCPA | Prior express **written** consent required |
| **AI voice calls** | TCPA + 2024 FCC ruling | AI-generated voice requires written consent — same as pre-recorded robocall |
| **Caller ID authentication** | STIR/SHAKEN (TRACED Act) | All US carriers must sign and verify caller ID cryptographically |
| **DNC compliance** | FTC National DNC Registry | Scrub all contacts before outbound campaigns |
| **SMS — A2P** | A2P 10DLC | Brand + campaign registration with The Campaign Registry required |
| **SMS — consent** | TCPA | Written consent for marketing SMS; express consent for transactional |
| **SMS — opt-out** | CTIA guidelines + TCPA | STOP keywords must be honoured immediately |

**Quiet hours**: 8am to 9pm in the recipient's local time zone — voice and SMS.

**Penalties**: $500–$1,500 per violation (per call or text). Private right of action — class actions common. No de minimis threshold.

**TCPA applies to any sender calling US numbers** — location of the business is irrelevant.

Detailed guides: [US Calling Regulations](https://www.vobiz.ai/docs/compliance/us/calling-regulations.md) · [US SMS Regulations](https://www.vobiz.ai/docs/compliance/us/sms-regulations.md) · [What is TCPA?](https://www.vobiz.ai/docs/blogs/what-is-tcpa.md) · [What is STIR/SHAKEN?](https://www.vobiz.ai/docs/blogs/what-is-stir-shaken.md) · [A2P 10DLC](https://www.vobiz.ai/docs/blogs/what-is-a2p-10dlc.md)

***

## European Union

The EU's voice and SMS compliance landscape is shaped by GDPR and the ePrivacy Directive.

| Area | Framework | Key requirement |
| - | - | - |
| **Marketing calls** | ePrivacy Directive | Explicit consent or legitimate interest (varies by member state) |
| **Automated calls / robocalls** | National implementations | Most EU member states prohibit automated marketing calls without prior consent |
| **SMS marketing** | ePrivacy Directive + national law | Opt-in consent required in most member states |
| **Data handling** | GDPR | Contact data processing requires a lawful basis; right to erasure applies to suppression lists |
| **Caller ID** | National regulation | Most EU states require accurate CLI presentation; anonymised calling is restricted |
| **AI-generated voice** | EU AI Act (2024) | High-risk AI systems must be disclosed; synthetic voice must be labelled in certain contexts |

**Key variation**: ePrivacy rules are implemented differently by each member state. Germany, France, and Spain have stricter rules than the baseline Directive. Always confirm the specific rules for each country you call.

**Quiet hours**: Vary by member state — typically no calls before 9am or after 8pm on weekdays; more restrictive on weekends.

***

## United Kingdom

Post-Brexit, the UK operates its own framework based on the Privacy and Electronic Communications Regulations (PECR) and UK GDPR.

| Area | Framework | Key requirement |
| - | - | - |
| **Marketing calls** | PECR | Soft opt-in for existing customers; explicit consent for new contacts |
| **Automated calls** | PECR | Prior explicit consent required for all automated marketing calls |
| **SMS marketing** | PECR | Prior explicit consent required |
| **Caller ID** | Ofcom rules | CLI must be presented accurately; withheld number restrictions |
| **DNC** | TPS / CTPS | Telephone Preference Service — equivalent to US DNC Registry |
| **Data handling** | UK GDPR | Equivalent to EU GDPR post-Brexit |

***

## Australia

| Area | Framework | Key requirement |
| - | - | - |
| **Marketing calls** | Spam Act 2003 + Do Not Call Register Act | Consent required; DNC Register scrubbing mandatory |
| **SMS marketing** | Spam Act 2003 | Commercial messages require consent and unsubscribe mechanism |
| **Automated calls** | ACMA rules | Pre-recorded marketing calls require consent and DNC scrubbing |
| **Quiet hours** | ACMA | 9am–8pm weekdays, 9am–5pm Saturdays; no calls on Sundays or public holidays |

***

## Middle East (UAE, Saudi Arabia, Bahrain)

| Area | Framework | Key requirement |
| - | - | - |
| **Marketing calls — UAE** | TRA regulations | Registered caller ID required for commercial outbound |
| **SMS — UAE** | TRA | Sender ID registration with UAE operators required |
| **Marketing calls — KSA** | CITC regulations | Commercial calling requires licensed provider; DND registry exists |
| **SMS — KSA** | CITC | Arabic sender IDs for Saudi recipients; template pre-registration required |

***

## Global principles for AI voice agent compliance

Across all markets, AI voice agent deployments that make outbound calls to consumers must address:

**1. Consent**: Most jurisdictions require some form of consent before automated or AI-generated calls. The standard ranges from implied consent (some EU markets for existing customers) to written consent (US, for all AI calls).

**2. Identification**: The AI must not impersonate a human in jurisdictions with disclosure requirements. The EU AI Act and emerging US state laws (California, Colorado) require disclosure that the caller is an AI in certain contexts.

**3. Opt-out**: Every market requires a mechanism to opt out of further contact. Honour opt-outs immediately and maintain suppression lists indefinitely.

**4. Record-keeping**: Maintain records of consent, campaign parameters, and delivery outcomes. These are your defence in a regulatory dispute.

**5. Data residency**: Recorded calls and transcripts may be subject to data residency requirements in India (must stay in India), EU (GDPR transfer rules), and other markets.

***

## Compliance by Vobiz feature

| Vobiz feature | Compliance considerations |
| - | - |
| **Outbound calling API** | TCPA consent (US), 140-series (India), DNC scrubbing (all markets) |
| **Campaign Manager** | AMD to filter humans from machines; DND/NDNC integration; calling hours enforcement |
| **AI voice agent (SIP + WebSocket)** | TCPA written consent (US); TCCCPR declaration (India); EU AI Act disclosure |
| **SMS API** | 10DLC registration (US); DLT template registration (India); PECR consent (EU) |
| **Call recording** | Consent to record varies by jurisdiction — two-party states (US), India, EU all differ |
| **Number provisioning** | KYC required for India numbers; legal entity verification for US toll-free |

***

## Related

* [India Calling Regulations](https://www.vobiz.ai/docs/compliance/india/calling-regulations.md)
* [US Calling Regulations](https://www.vobiz.ai/docs/compliance/us/calling-regulations.md)
* [US SMS Regulations](https://www.vobiz.ai/docs/compliance/us/sms-regulations.md)
* [What is TCPA?](https://www.vobiz.ai/docs/blogs/what-is-tcpa.md)
* [What is STIR/SHAKEN?](https://www.vobiz.ai/docs/blogs/what-is-stir-shaken.md)
* [What is A2P 10DLC?](https://www.vobiz.ai/docs/blogs/what-is-a2p-10dlc.md)
* [DLT Registration Guide](https://www.vobiz.ai/docs/best-practices/dlt-registration.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.