10Reference Customer Sample Clauses

10Reference Customer. You agree that the Company may identify you as a user of the Cloud Connected Services and use your trademark and/or logo (i) in sales presentations, promotional/marketing materials, and press releases, and (ii) in order to develop a brief customer profile for use by the Company on the Company's Website for promotional purposes.
AutoNDA by SimpleDocs

Related to 10Reference Customer

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Return of Customer Data Okta shall return Customer Data to Customer and, to the extent allowed by applicable law, delete Customer Data in accordance with the procedures and time periods specified in the Trust & Compliance Documentation, unless the retention of the data is requested from Okta according to mandatory statutory laws.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

  • Billing and Collection Customers BellSouth currently has in effect numerous billing and collection agreements with various interexchange carriers and billing clearing houses and as such these billing and collection customers (“B&C Customers”) query BellSouth’s LIDB to determine whether to accept various billing options from End Users. Until such time as BellSouth implements in its LIDB and its supporting systems the means to differentiate Lightyear’s data from BellSouth’s data, the following shall apply: (1) Lightyear will accept responsibility for telecommunications services billed by BellSouth for its B&C Customers for Lightyear’s End User accounts which are resident in LIDB pursuant to this Agreement. Lightyear authorizes BellSouth to place such charges on Lightyear’s xxxx from BellSouth and shall pay all such charges, including, but are not limited to, collect and third number calls. (2) Charges for such services shall appear on a separate BellSouth xxxx xxxx identified with the name of the B&C Customers for which BellSouth is billing the charge. (3) Lightyear shall have the responsibility to render a billing statement to its End Users for these charges, but Lightyear shall pay BellSouth for the charges billed regardless of whether Lightyear collects from Lightyear’s End Users. (4) BellSouth shall have no obligation to become involved in any disputes between Lightyear and B&C Customers. BellSouth will not issue adjustments for charges billed on behalf of any B&C Customer to Lightyear. It shall be the responsibility of Lightyear and the B&C Customers to negotiate and arrange for any appropriate adjustments.

  • Contractor Personnel – Reference Checks The Contractor warrants that all persons employed to provide service under this Contract have satisfactory past work records indicating their ability to adequately perform the work under this Contract. Contractor’s employees assigned to this project must meet character standards as demonstrated by background investigation and reference checks, coordinated by the agency/department issuing this Contract.

  • 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).

  • Unbundled Voice Loops (UVLs) 2.2.1 BellSouth shall make available the following UVLs:

  • Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Recovery Month, Assuming Bank shall provide Receiver:

  • Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, ONS must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • RDDS query RTT Refers to the collective of “WHOIS query RTT” and “Web-­‐based-­‐ WHOIS query RTT”.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!