2015 ORS 759.705¹
Program message preamble
  • information to be included

(1) An information provider that does business in this state shall include a preamble in its program messages.

(2) The preamble must:

(a) Describe the service that the program provides.

(b) Advise the caller of the price per call, including:

(A) Any per minute charge;

(B) Any flat rate charge;

(C) Any minimum charge;

(D) The maximum charge possible for the service as determined from multiplying maximum duration in minutes by the cost per minute, unless the call has a possible indefinite duration, in which case the charge for one hour of use shall be stated;

(E) Whether calls that may last more than 20 minutes are interactive or have a possible indefinite duration; and

(F) The maximum possible charges for any pay-per-call numbers to which the caller may be referred by the information provider.

(c) Advise that the billing will begin shortly after the end of the preamble. A reasonable length of time shall be allotted after the preamble to give consumers an opportunity to disconnect before the program message starts.

(3) All preambles must be clearly articulated in the language used in advertisements for the telephone number and the language used within the body of the program. The language in the preamble shall be spoken in a normal cadence and at a volume equal to that of the program message.

(4) When an information provider’s program message consists only of a polling application that permits the caller to register an opinion or to vote on a matter by completing a call, or results in a flat charge of $2 or less, this section does not apply. [1991 c.672 §2]


1 Legislative Counsel Committee, CHAPTER 759—Telecommunications Utility Regulation, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­ors759.­html (2015) (last ac­cessed Jul. 16, 2016).
 
2 OregonLaws.org contains the con­tents of Volume 21 of the ORS, inserted along­side the per­tin­ent statutes. See the preface to the ORS An­no­ta­tions for more information.
 
3 OregonLaws.org assembles these lists by analyzing references between Sections. Each listed item refers back to the current Section in its own text. The result reveals relationships in the code that may not have otherwise been apparent.