Call Blocking Feature Sample Clauses

Call Blocking Feature. Application and Ability to Opt-Out: Effective June 30, 2021, on all WOW! Phone services, WOW! uses a call blocking feature (the “Blocking Feature”), which automatically blocks certain calls that are determined by WOW! in its sole discretion to be likely spam, robocalls or other unwanted calls. You understand and agree that WOW! may use unaffiliated third party databases and directories, as well as other information sources, in implementing the Blocking Feature. Although the features of this Blocking Feature are subject to change at any time by WOW!, calls blocked by WOW! generally fall into these categories (the “Blocked Calls”): (i) Calls from telephone numbers identified by industry sources to be fraudulent, solicitous, or SPAM; (ii) Calls from telephone numbers that have made an abnormal number of attempts to reach WOW! Customers (a.k.a fishing attempts); and (iii) Calls from telephone numbers that are identified in government databases as fraudulent or suspicious. You agree and understand that:
AutoNDA by SimpleDocs

Related to Call Blocking Feature

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • Technical Feasibility of String While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level domain strings across the Internet, certain top-­‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

  • Vendor Logo (Supplemental Vendor Information Only) No response Optional. If Vendor desires that their logo be displayed on their public TIPS profile for TIPS and TIPS Member viewing, Vendor may upload that logo at this location. These supplemental documents shall not be considered part of the TIPS Contract. Rather, they are Vendor Supplemental Information for marketing and informational purposes only. Bid Attributes Disadvantaged/Minority/Women Business & Federal HUBZone Some participating public entities are required to seek Disadvantaged/Minority/Women Business & Federal HUBZone ("D/M/WBE/Federal HUBZone") vendors. Does Vendor certify that their entity is a D/M/WBE/Federal HUBZone vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. NO Historically Underutilized Business (HUB) Some participating public entities are required to seek Historically Underutilized Business (HUB) vendors as defined by the Texas Comptroller of Public Accounts Statewide HUB Program. Does Vendor certify that their entity is a HUB vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. No National Coverage Can the Vendor provide its proposed goods and services to all 50 US States? Yes

  • Distribution of UDP and TCP queries DNS probes will send UDP or TCP “DNS test” approximating the distribution of these queries.

Time is Money Join Law Insider Premium to draft better contracts faster.