CourtMesh

Section 8: Change of Preference of Subscribers

The Telecom Commercial Communications Customer Preference Regulations, 2010Central Regulations · 1997

(1) Any subscriber may, at any time after expiry of three months from the date of registration or three months from the date of last change of his request, made under regulation 7, change his preference in accordance with the procedure specified under Schedule-I to these regulations.

(2) Every Access Provider shall, on receipt of a request under sub-regulation

(1), verify the correctness of the request so received and if the request is found to be correct record details of such request in the Provider Customer Preference Register and confirm the same, within twenty four hours, to the subscriber through SMS:

Provided that if the request is not found to be correct, the Access Provider shall inform the subscriber, through SMS, within twenty four hours, the details of errors noted by the Access Provider and advise the subscriber to make a fresh request.

Where this provision sits

ActThe Telecom Commercial Communications Customer Preference Regulations, 2010
Section8
Marginal noteChange of Preference of Subscribers
JurisdictionCentral
StatusIn force as published by the source

Find the provision, not just read it

The full text above is free, and it stays free. What a free CourtMesh account adds is everything you cannot do by reading one page at a time:

  • Search 49,000+ Central and State enactments by what a provision says, not by its number
  • Jump from any section to every judgment that has applied it
  • Search 300 million+ Indian court records alongside the statute
  • Ask a research agent to find and read the case law on a provision for you

Free account. No card. About a minute to create.

Create a free account

Need this as data, not as a page? The Telecom Commercial Communications Customer Preference Regulations, 2010 is one of 49,000+ enactments on CourtMesh. The Indian court cases API serves the case law that cites these provisions over JSON, with API documentation and plans and pricing. See also the judgment library.