Alerts via Text Message To stop Alerts via text message, text "STOP" to 99785 at anytime. Alerts sent to your primary email address will be unaffected by this action. To restore Alerts on your Mobile Device, just visit the Alerts tab in Online Banking and click the box next to your mobile number for the Alert(s) you would like to receive again. For help with SMS text alerts, text “HELP” to 99785. In case of questions, please contact Customer Care at 0-000-000-0000. Our participating carriers include (but are not limited to) AT&T® Wireless, T-Mobile®, U.S. Cellular®, Verizon Wireless.
TEXT MESSAGING WHILE DRIVING In accordance with Executive Order (EO) 13513, “Federal Leadership on Reducing Text Messaging While Driving,” any and all text messaging by Federal employees is banned: a) while driving a Government owned vehicle (GOV) or driving a privately owned vehicle (POV) while on official Government business; or b) using any electronic equipment supplied by the Government when driving any vehicle at any time. All cooperators, their employees, volunteers, and contractors are encouraged to adopt and enforce policies that ban text messaging when driving company owned, leased or rented vehicles, POVs or GOVs when driving while on official Government business or when performing any work for or on behalf of the Government.
Reducing Text Messaging While Driving Pursuant to Executive Order 13513, 74 FR 51225 (Oct. 6, 2009), Recipient should encourage its employees, subrecipients, and contractors to adopt and enforce policies that ban text messaging while driving, and Recipient should establish workplace safety policies to decrease accidents caused by distracted drivers.
ODUF Message to be Transmitted 6.1.1 The following messages recorded by BellSouth will be transmitted to Quality Telephone: - Message recording for per use/per activation type services (examples: Three Way Calling, Verify, Interrupt, Call Return, etc.) - Measured billable Local - Directory Assistance messages - IntraLATA Toll - WATS and 800 Service - N11 - Information Service Provider Messages - Operator Services Messages - Credit/Cancel Records - Usage for Voice Mail Message Service 6.1.2 Rated Incollects (originated in BellSouth and from other companies) can also be on ODUF. Rated Incollects will be intermingled with BellSouth recorded rated and unrated usage. Rated Incollects will not be packed separately. 6.1.3 BellSouth will perform duplicate record checks on records processed to ODUF. Any duplicate messages detected will be deleted and not sent to Quality Telephone. 6.1.4 In the event that Quality Telephone detects a duplicate on ODUF they receive from BellSouth, Quality Telephone will drop the duplicate message and will not return the duplicate to BellSouth).
Consent to Emails and Automated Text Messages By participating as a Zelle User, you represent that you are the owner of the email address, mobile phone number, and/or other alias you enroll, or that you have the delegated legal authority to act on behalf of the owner of such email address, mobile phone number and/or other alias to send or receive money as described in this Agreement. You consent to the receipt of emails or text messages from us, from Zelle, from other Users that are sending you money or requesting money from you, and from other Network Banks or their agents regarding the Zelle Service or related transfers between Network Banks and you. You agree that we, Zelle, or either of our agents may use automatic telephone dialing systems in connection with text messages sent to any mobile phone number you enroll. You further acknowledge and agree: ▪ You are responsible for any fees or other charges that your wireless carrier may charge for any related data, text or other message services, including without limitation for short message service. Please check your mobile service agreement for details or applicable fees. ▪ You will immediately notify us if any email address or mobile phone number you have enrolled is (i) surrendered by you, or (ii) changed by you. ▪ In the case of any messages that you may send through either us or Zelle or that we may send or Zelle may send on your behalf to an email address or mobile phone number, you represent that you have obtained the consent of the recipient of such emails or automated text messages to send such emails or text messages to the recipient. You understand and agree that any emails or text messages that we send or that Xxxxx sends on your behalf may include your name. ▪ Your wireless carrier is not liable for any delay or failure to deliver any message sent to or from us or Zelle, including messages that you may send through us or through Zelle or that we may send or Zelle may send on your behalf. ▪ To cancel text messaging from us, text STOP to 20736. For help or information regarding text messaging, text HELP to 20736 or contact our customer service at 0.000.000.0000 or 0.000.000.0000. You expressly consent to receipt of a text message to confirm your “STOP” request. ▪ Our Zelle notifications are supported by many carriers, such as AT&T, Verizon Wireless, T- Mobile, and Sprint. Check with your individual carrier to confirm availability. ▪ We or Zelle may use information on file with your wireless operator to further verify your identity and to protect against or prevent actual or potential fraud or unauthorized use of the Zelle Service. By using the Zelle Service, you authorize your wireless operator (AT&T, Sprint, T-Mobile, US Cellular, Verizon, or any other branded wireless operator) to disclose your mobile number, name, address, email, network status, customer type, customer role, billing type, mobile device identifiers (IMSI and IMEI) and other subscriber status and device details, if available, to our third party service provider solely to allow verification of your identity and to compare information you have provided to us or to Zelle with your wireless operator account profile information for the duration of our business relationship. See Xxxxx’x Privacy Policy [xxxxx://xxx.xxxxxxxx.xxx/privacy-policy] for how it treats your data. Please review our Privacy Policy for more information.
Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.
Tandem Transit Traffic 12.1 As used in this Section, Tandem Transit Traffic is Telephone Exchange Service traffic that originates on Onvoy's network, and is transported through Frontier’s Tandem to the subtending End Office or its equivalent of another carrier (CLEC, ILEC other than Frontier, Commercial Mobile Radio Service (CMRS) carrier, or other LEC (“Other Carrier”). Neither the originating nor terminating customer is a Customer of Frontier. Subtending End Offices shall be determined in accordance with and as identified in the Local Exchange Routing Guide (LERG). For the avoidance of any doubt, under no circumstances shall Frontier be required to transit traffic through a Frontier Tandem to a Central Office that the LERG does not identify as subtending that particular Frontier Tandem. Switched Exchange Access Service traffic is not Tandem Transit Traffic. 12.2 Tandem Transit Traffic Service provides Onvoy with the transport of Tandem Transit Traffic as provided below. 12.3 Tandem Transit Traffic may be routed over the Interconnection Trunks described in Sections 2 through 6 of this Attachment. Onvoy shall deliver each Tandem Transit Traffic call to Frontier’s Tandem with CCS and the appropriate Transactional Capabilities Application Part (“TCAP”) message to facilitate full interoperability of CLASS Features and billing functions. 12.4 Onvoy may use Tandem Transit Traffic Service only for traffic that originates on Onvoy’s network and only to send traffic to an Other Carrier with whom Onvoy has a reciprocal traffic exchange arrangement (either via written agreement or mutual tariffs) that provides for the Other Carrier, to terminate or complete traffic originated by Onvoy and to bill Onvoy, and not to bill Frontier, for such traffic. Onvoy agrees not to use Frontier’s Tandem Transit Traffic Service to send traffic to an Other Carrier with whom Onvoy does not have such a reciprocal traffic exchange arrangement or to send traffic that does not originate on Onvoy’s network. 12.5 Onvoy shall pay Frontier for Tandem Transit Traffic Service at the rates specified in the Pricing Attachment. Frontier will not be liable for compensation to any Other Carrier for any traffic that is transported through Frontier’s Tandem and Frontier reserves the right to assess to Onvoy any additional charges or costs any Other Carrier imposes or levies on Frontier for the delivery or termination of such traffic, including any Switched Exchange Access Service charges. If Frontier is billed by any Other Carrier for any traffic originated by Onvoy, Frontier may provide notice to Onvoy of such billing. Upon receipt of such notice, Onvoy shall immediately stop using Frontier’s Tandem Transit Traffic Service to send any traffic to such Other Carrier until it has provided to Frontier certification that the Other Carrier has removed such billed charges from its bill to Frontier and that the Other Carrier will not bill Frontier for any traffic originated by Onvoy. Such certification must be signed by an authorized officer or agent of the Other Carrier and must be in a form acceptable to Frontier. 12.6 If Onvoy uses Tandem Transit Traffic Service for traffic volumes that exceed the Centum Call Seconds (Hundred Call Seconds) busy hour equivalent of 200,000 combined minutes of use per month (a DS1 equivalent) to the subtending End Office of a particular Other Carrier for any month (the “Threshold Level”). Onvoy shall use good faith efforts to establish direct interconnection with such Other Carrier and reduce such traffic volumes below the Threshold Level. If Frontier believes that Xxxxx has not exercised good faith efforts promptly to obtain such direct interconnection, either Party may use the Dispute Resolution processes of this Agreement. 12.7 If Onvoy fails to comply with Section 12 of this Attachment, such failure shall be a material breach of a material provision of this Agreement and Frontier may exercise any and all remedies under this Agreement and Applicable Law for such breach. 12.8 If or when a third party carrier plans to subtend an Onvoy switch, then Onvoy shall provide written notice to Frontier at least ninety (90) days before such subtending service arrangement becomes effective so that Frontier may negotiate and establish direct interconnection with such third party carrier. Upon written request from Frontier, Onvoy shall offer to Frontier a service arrangement equivalent to or the same as Tandem Transit Traffic Service provided by Frontier to Onvoy as defined in this Section such that Frontier may terminate calls to a Central Office or its equivalent of a CLEC, ILEC other than Frontier, CMRS carrier, or other LEC, that subtends an Onvoy Central Office or its equivalent (“Reciprocal Tandem Transit Service”). Onvoy shall offer such Reciprocal Transit Service arrangements under terms and conditions of an amendment to this Agreement or a separate agreement no less favorable than those provided in this Section. 12.9 Neither Party shall take any actions to prevent the other Party from entering into a direct and reciprocal traffic exchange arrangement with any carrier to which it originates, or from which it terminates, traffic.
Minimum Customer Support Requirements for TIPS Sales Vendor shall provide timely and commercially reasonable support for TIPS Sales or as agreed to in the applicable Supplemental Agreement.
Shift Rotation Routine shift rotation is not an approach to staffing endorsed by the Employer. Except for emergency situations where it may be necessary to provide safe patient care, shift rotation will not be utilized without mutual consent. If such an occasion should ever occur, volunteers will be sought first. If no one volunteers, the Employer will rotate shifts on an inverse seniority basis until the staff vacancies are filled.
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
