Customer Integrations Clause Samples

The Customer Integrations clause defines the responsibilities and procedures for connecting the customer's systems or software with the provider's products or services. Typically, it outlines the technical requirements, data exchange protocols, and support obligations involved in establishing and maintaining these integrations. This clause ensures that both parties understand their roles in achieving seamless interoperability, thereby minimizing technical issues and clarifying accountability for integration-related tasks.
Customer Integrations. The Services may provide Customer with the ability to integrate certain functionalities of the Platform with applications or services separately provided to Customer by third parties (“Third Party Services”) via API integrations (“Third Party Integrations”); examples include ticketing and messaging applications, SIEM or SOAR tools, and security data management tools). Customer’s use of such Third Party Integrations is optional and Customer shall be required to take the steps set forth in the Documentation to enable a Third Party Integration. Customer acknowledges and agrees that: (a) the use of Third Party Services are subject to the terms and conditions agreed between Customer and each such Third Party Service provider; (b) Customer may be required to grant Wiz access to its Third Party Service account and/or to grant the Third Party Service provider access to its Wiz account; and (c) Customer Data may be transferred between Wiz and the Third Party Service provider as required and authorized by Customer for the interoperation with the Services. Since Wiz does not provide such third party applications or services, Wiz cannot guarantee the continued availability of such Third Party Integration and may cease supporting them at any time, including if the relevant third party ceases to make its application or service available for integration with the Services or changes the way it does so in a way that is not reasonably acceptable to Wiz. To the maximum extent permitted by law but without derogating from Wiz’s obligations under this Agreement, Wiz shall not bear and expressly disclaims all responsibility or liability of any kind relating to such Third Party Integrations, including, without limitation, for any disclosure of, access to or other processing of Customer Data by Third Party Service providers.
View SourceView Similar (13)
Customer Integrations. The Services may provide Customer with the ability to integrate certain functionalities of the Services with applications or services separately provided to Customer by third parties (“Third Party Services”) via API integrations built by either Island or the Third Party Service provider (“Third Party Integrations”). Customer’s use of such Third Party Integrations is optional and Customer shall be required to take the steps set forth in the Documentation to enable a Third Party Integration. Customer acknowledges and agrees that: (a) the use of Third Party Services are subject to the terms and conditions agreed between Customer and each such Third Party Service provider; (b) Customer may be required to grant Island access to its Third Party Service account and/or to grant the Third Party Service provider access to its Island account; and (c) Customer Data may be transferred between Island and the Third Party Service provider as required and authorized by Customer for the interoperation with the Services. Since Island does not provide such Third Party Services, Island cannot guarantee the continued availability of such Third Party Integration and may cease supporting them at any time, including if the relevant Third Party Service provider ceases to make its application or service available for integration with the Services or changes the way it does so in a way that is not reasonably acceptable to Island. To the maximum extent permitted by law but without derogating from Island’s obligations under this Agreement, Island shall not bear and expressly disclaims all responsibility or liability of any kind relating to such Third Party Integrations, including, without limitation, for any disclosure of, access to or other processing of Customer Data by Third Party Service providers.
View SourceView Similar (2)
Customer Integrations a) Notwithstanding any provision to the contrary in any agreement between the Parties, this BAA applies only to Services offered by RingCentral as described in Annex A. b) Pursuant to the limitations contained in the Agreement between the Parties and applicable RingCentral policies, Customer may choose to, at its own risk, use third party or Customer’s own applications, services, devices, APIs, or any other technology (whether utilized by Customer or a third party on behalf of Customer and whether implemented by RingCentral or not) which integrate with the Services or that transfer data to or from the Services (“Customer Integrations”). c) Customer understands and agrees that Customer Integrations are outside the scope of the Parties’ primary agreement and of this Business Associate Agreement. d) Notwithstanding any provision to the contrary in any agreement between the Parties, RingCentral has no responsibility or liability for, and disclaims any warranties or representations relating to, any Customer Integrations. e) For the avoidance of doubt, RingCentral will have no obligations or liability for the privacy, security, confidentiality, availability, or integrity of any Customer Integrations, or any PHI or other data processed, handled, sent, stored, created, received, maintained, or transmitted in connection with any Customer Integrations or through any applications, services, devices, APIs, or any other technology not provided within RingCentral Services.
View SourceView Similar (2)
Customer Integrations. Notwithstanding any provision to the contrary in any agreement between the Parties, this BAA applies only to the Services. Notwithstanding any provision to the contrary in any agreement between the Parties, RingCentral has no responsibility or liability for, and disclaims any warranties or representations relating to, any Customer applications, services, devices, APIs, or any other technology (whether utilized by Customer or a third party on behalf of Customer) that are not managed by RingCentral. Any such technology which integrate with the Services or that transfer data to or from the Services (“Customer Integrations”). For the avoidance of doubt, RingCentral will have no obligations or liability for the privacy, security, confidentiality, availability, or integrity of any Customer Integrations, or any PHI or other data processed, handled, sent, stored, created, received, maintained, or transmitted in connection with any Customer Integrations or through any applications, services, devices, APIs, or any other technology not provided within RingCentral Services.
View Source
Customer Integrations. Customer acknowledges that the Services may link to third party websites, applications or services that can be integrated with or connected to the Services (“Third Party Integrations”). To use such features, Customer must either obtain access to the Third- Party Integrations via the third party provider or authorize the Company to obtain access on Customer’s behalf. If Customer uses such Third Party Integrations, it acknowledges and agrees that: (a) any link from the Service does not imply any Company endorsement of, or responsibility for, those Third Party Integrations and the use of such Third Party Integrations are subject to the terms and conditions of the Third Party Integration provider; (b) Customer may be required to grant the Company access to its Third Party Integration account and/or to grant the Third Party Integration provider access to its Company account; (c) Customer Data may be transferred between Dazz and the Third Party Integration provider as required for the interoperation with the Services; and (d) Dazz will use its best commercial efforts to support the Third-Party Integrations that are currently integrated with the Service however, Dazz does not guarantee the continued availability of such Third Party Integrations, and may cease supporting them without liability to Customer. To the maximum extent permitted by law but without derogating from Dazz’s obligations under this Agreement, Dazz shall not bear and expressly disclaims all responsibility or liability of any kind relating to such Third Party Integrations, including, without limitation, for any disclosure of, access to or other processing of Customer Data by Third Party Integration providers.
View Source

Related to Customer Integrations

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

  • Access Toll Connecting Trunk Group Architecture 8.2.1 If Reconex chooses to subtend a Verizon access Tandem, Reconex’s NPA/NXX must be assigned by Reconex to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center subtends as identified in the LERG. 8.2.2 Reconex shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from Reconex’s Customers. 8.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office Reconex utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the Tandem Verizon utilizes to provide Exchange Access in such LATA. 8.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow Reconex’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access tandem.

  • Traffic Measurement and Billing over Interconnection Trunks 6.1 For billing purposes, each Party shall pass Calling Party Number (CPN) information on at least ninety-five percent (95%) of calls carried over the Interconnection Trunks. 6.1.1 As used in this Section 6, “Traffic Rate” means the applicable Reciprocal Compensation Traffic rate, Measured Internet Traffic rate, intrastate Switched Exchange Access Service rate, interstate Switched Exchange Access Service rate, or intrastate/interstate Tandem Transit Traffic rate, as provided in the Pricing Attachment, an applicable Tariff, or, for Measured Internet Traffic, the FCC Internet Order. 6.1.2 If the originating Party passes CPN on ninety-five percent (95%) or more of its calls, the receiving Party shall ▇▇▇▇ the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. For any remaining (up to 5%) calls without CPN information, the receiving Party shall ▇▇▇▇ the originating Party for such traffic at the Traffic Rate applicable to each relevant minute of traffic, in direct proportion to the minutes of use of calls passed with CPN information. 6.1.3 If the originating Party passes CPN on less than ninety-five percent (95%) of its calls and the originating Party chooses to combine Reciprocal Compensation Traffic and Toll Traffic on the same trunk group, the receiving Party shall ▇▇▇▇ the higher of its interstate Switched Exchange Access Service rates or its intrastate Switched Exchange Access Services rates for all traffic that is passed without CPN, unless the Parties agree that other rates should apply to such traffic. 6.2 At such time as a receiving Party has the capability, on an automated basis, to use such CPN to classify traffic delivered over Interconnection Trunks by the other Party by Traffic Rate type (e.g., Reciprocal Compensation Traffic/Measured Internet Traffic, intrastate Switched Exchange Access Service, interstate Switched Exchange Access Service, or intrastate/interstate Tandem Transit Traffic), such receiving Party shall ▇▇▇▇ the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. If the receiving Party lacks the capability, on an automated basis, to use CPN information on an automated basis to classify traffic delivered by the other Party by Traffic Rate type, the originating Party will supply Traffic Factor 1 and Traffic Factor