Primary Contacts The Parties will keep and maintain current at all times a primary point of contact for this contract. The primary contacts for this this Contract are as follows:
Customer Contacts CLEC, or CLEC's authorized agent, are the single point of contact for its End User Customers' service needs, including without limitation, sales, service design, order taking, Provisioning, change orders, training, maintenance, trouble reports, repair, post-sale servicing, Billing, collection and inquiry. CLEC will inform its End User Customers that they are End User Customers of CLEC. CLEC's End User Customers contacting Qwest will be instructed to contact CLEC, and Qwest's End User Customers contacting CLEC will be instructed to contact Qwest. In responding to calls, neither Party will make disparaging remarks about the other Party. To the extent the correct provider can be determined, misdirected calls received by either Party will be referred to the proper provider of Local Exchange Service; however, nothing in this Agreement shall be deemed to prohibit Qwest or CLEC from discussing its products and services with CLEC's or Qwest's End User Customers who call the other Party. 10.1 In the event Qwest terminates Service to CLEC for any reason, CLEC will provide any and all necessary notice to its End User Customers of the termination. In no case will Qwest be responsible for providing such notice to CLEC's End User Customers.
Customer Contact During the delivery phase of a Project Supplier may have direct communication with a Customer, limited solely to those communications necessary to affect provision of Services and/or Deliverables.
Authorized Contacts LightEdge Solutions provides reliable and secure managed services by requiring technical support and information requests come only from documented, authorized client-organization contacts. Additionally, in compliance with federally regulated CPNI (Customer Proprietary Network Information) rules, a customer contacting LightEdge Solutions to request an add, move, or change and/or to request information on their account, must provide LightEdge representative with customer’s Code Word. Code Word is not required or verified to open trouble tickets related to service issues, however, any subsequent information/updates or authorization of intrusive testing related to the trouble ticket will require the Code Word. Customer shall provide a “contact list” which will contain one (“1”) Administrative contact and may contain up to three (“3”) Technical contacts per service. Administrative and Technical contacts are authorized to request service changes or information, including the contact name, contact e-mail address and contact phone number for each contact but must provide customer Code Word for any CPNI related requests. Requests to change a contact on the list or to change the Code Word must be submitted by the Administrative contact. Requests to replace the Administrative contact shall be submitted via fax to LightEdge on customer company letterhead. All requests are verified per procedure below. Requests for CPNI, configuration information or changes are accepted only from documented, authorized client-organization contacts via e-mail, fax or phone and will require Customer’s Code Word. E-mail and fax requests must be submitted without the Code Word. Customer contact will be called to verify Code Word. E- mail requests that include the Code Word will be denied and the client Administrative Contact will be notified and required to change the Code Word. E-mail and fax requests are verified with a phone call to the documented client contact. Phone call requests must be validated with an e-mail request from a documented client contact.
Operational Contacts Each Interconnection Party shall designate, and provide to each other Interconnection Party contact information concerning, a representative to be responsible for addressing and resolving operational issues as they arise during the term of the Interconnection Service Agreement.
PRINCIPAL CONTACTS Individuals listed below are authorized to act in their respective areas for matters related to this instrument.
Communications and Contacts The Institution: [NAME AND TITLE OF INSTITUTION CONTACT PERSON] [INSTITUTION NAME] [ADDRESS] [TELEPHONE NUMBER] [FACSIMILE NUMBER] The Contractor: [NAME AND TITLE OF CONTRACTOR CONTACT PERSON] [CONTRACTOR NAME] [ADDRESS] [TELEPHONE NUMBER] [FACSIMILE NUMBER] All instructions, notices, consents, demands, or other communications shall be sent in a manner that verifies proof of delivery. Any communication by facsimile transmission shall also be sent by United States mail on the same date as the facsimile transmission. All communications which relate to any changes to the Contract shall not be considered effective until agreed to, in writing, by both parties.
Abuse Contact Registry Operator shall provide to ICANN and publish on its website its accurate contact details including a valid email and mailing address as well as a primary contact for handling inquiries related to malicious conduct in the TLD, and will provide ICANN with prompt notice of any changes to such contact details.
Security Contact Operator shall provide the name and contact information of Operator's Security Contact on Exhibit F. The LEA may direct security concerns or questions to the Security Contact.
Contacts 1. Florida Housing’s contract administrator for this Agreement is: Contract Administrator Florida Housing Finance Corporation 000 Xxxxx Xxxxxxxx Xx., Xxxxx 0000 Xxxxxxxxxxx, Xxxxxxx 00000-0000 Phone: 000.000.0000 E-mail: Xxxxxxxx.Xxxxx@xxxxxxxxxxxxxx.xxx 2. The Florida Housing program contact for this Agreement is: Xxxxx X. Xxx, Director of Asset Management & Guarantee Program Florida Housing Finance Corporation 000 Xxxxx Xxxxxxxx Xx., Xxxxx 0000 Xxxxxxxxxxx, Xxxxxxx 00000-0000 Phone: 000.000.0000 E-mail: Xxxxx.Xxx@xxxxxxxxxxxxxx.xxx or the designated successor. 3. The Grantee’s contract administrator for this Agreement is: Xxxxx Xxxxx, Manager 0000 Xxxxxxxx Xxxxxx Xxxxxxx, Xxx. X Xxxxxxxx, XX 00000 Phone: (000) 000-0000 E-mail: Xxxxx.xxxxx@xxxxxxxxxx.xxx or the designated successor. 4. All written approvals referenced in this Agreement shall be obtained from the parties’ contract administrator or their respective designees. 5. All notices shall be given to the parties’ contract administrator.
