Locale Summary |
|
---|---|
Locale name |
India |
ISO code |
IN |
Region |
Asia |
Dialing code |
+91 |
Reachability |
Inbound |
Outbound |
---|---|---|
Domestic |
N/A |
N/A |
International |
N/A |
Yes |
Toll-Free |
Yes |
No |
Outbound restrictions |
Outbound calls to India can only be made from international (non-Indian) numbers. |
|
Outbound requirements |
N/A |
|
Best practices |
Twilio recommends that customers review their proposed use-cases with qualified legal counsel to make sure that they comply with all applicable laws, in accordance with Twilio's Terms of Service (ToS). The best-practice guidance below is of a general nature, and is not to be taken as legal advice.
Customers must gain consent from the call recipient to receive commercial communications related to the customer’s specific purpose, product or service. If consent is not obtained, the Telecommunications Regulatory Authority of India (TRAI) will consider such calls Unsolicited Commercial Communications (UCC), which is subject to blocking or account termination action for local law compliance purposes.
The Department of Telecommunications (DoT) and TRAI manage a consumer portal for the recipients of UCC (and/or communications of a generally suspicious/fraudulent nature) to report voice calls that they did not consent to receive. This means the local authorities actively monitor for, and enforce, account blockings of non-compliant use-cases.
|
|
Caller ID |
Inbound |
Outbound |
---|---|---|
Domestic |
N/A |
N/A |
International |
N/A |
+E.164 |
Toll-Free |
+E.164 |
N/A |
DTMF |
Inbound |
Outbound |
---|---|---|
RFC.2833 format |
N/A |
Yes (Not guaranteed) |
Emergency Calling |
Outbound |
---|---|
Emergency services |
No |
For the benefit of all our customers, these guidelines are provided to help you comply with applicable requirements and to help ensure Twilio's platform remains compliant with global telecommunications ecosystem requirements. These guidelines represent our current understanding of common compliance requirements generally applicable to Twilio and its customers, and do not constitute legal advice. By posting these guidelines, Twilio makes no assurances regarding the legal compliance of your application built using our APIs. You are expected to understand and abide by all compliance obligations applicable to your specific application. You should check these pages regularly for updates as telecommunications ecosystem requirements continue to evolve and change, and the information below may be updated or changed without notice.