Celigo Support Policies

Celigo is committed to working with its Customers to promptly investigate and resolve tickets reported by its Customers. This Support Policy shall govern Celigo’s provision of support services to the Customer pursuant to the Customer Success Plan level that the Customer has purchased or is otherwise entitled to.

The Customer is entitled to the Essential Customer Success Plan as part of an active product subscription. The Customer may choose to purchase a Preferred or Premier Customer Success Plan for expanded support services as described at www.celigo.com/customer-success-plan/.

1. Obtaining Support

1.1  Celigo will provide the Customer with support services for products for which the Customer has an active and current subscription.

1.2  Support hours are defined as the hours during which support is available during specified channels. Support hours are based on Pacific Standard Time and may be adjusted for Daylight Savings Time. The tables below provide the support hours per Customer Success Plan for four(4) sample time zones. Limited support is available during U.S. holidays.

1.3  Standard Support is defined as the time period where standard support channels (as defined in 1.4) are available for support requests of any severity level. After Hours, Urgent Support is defined as the time period where support is available for urgent, system down issues via the phone support channel only.

 

 

 

1.4  Celigo provides support through multiple channels. The table below describes the support channels available to the Customer per Customer Success Plan.

 

 

2. Urgency Levels

Urgency Levels are specified by the Customer at ticket creation to prioritize the impact to their business processes. Celigo will take Urgency Levels into consideration when assigning a Severity Level to incoming tickets.

 

3. Severity Levels

Severity Levels are assigned to allow prioritization of incoming tickets. Celigo will work with the Customer to assign the appropriate severity level to a ticket according to the Urgency Level specified by the Customer and the Severity Level definitions below. Celigo may reclassify the severity level of a ticket submitted by the Customer.

3.1.  Urgent Priority

• System is down.
• A critical business process is blocked, and there is no reasonable work around.

 

3.2.  High Priority

• System is severely degraded but still operational.
• A critical business process is performing poorly or has a bug, but there exists a reasonable work around.
• A non-critical business process is blocked, and there is no reasonable work around.

 

3.3.  Normal Priority

• System is not performing at peak levels but is still operational.
• A non-critical business process is performing poorly or has a bug, but there exists a reasonable work around.

 

3.4.  Low Priority

• A cosmetic change is needed.
• An enhancement is requested.
• All test, development, beta, sandbox, and other non-production related issues and requests.

 

 

4. Target Response Times
The table below describes the target response time from Celigo to the Customer per severity level and Customer Success Plan during support hours. These response times are calculated based on the applicable support hours associated with the Customer Success Plan.

 

 

5. What is Supported?

5.1.  General Questions & Answers (Q&A)

Examples include (but are not limited to):

• I am exporting Sales Order records to my warehouse, but I keep getting the following error. What does it mean?
• I am importing Customer records, but the first and last name fields are not populating. How do I fix this?
• For my Magento integration, why won’t this item export from NetSuite to my store?

 

5.2.  Software Bugs/Defects

A bug/defect is subject to review and Celigo may not provide a solution for the bug/defect or Celigo may choose to provide a solution for which additional charges may apply. For example,

• The Bug/Defect is the result of a configuration change or enhancement to the application environment
• The Bug/Defect represents a gap in functionality that was not explicitly included in the product or integration sold (as stated in a Quote, Proposal, Requirements Document, or Change Order).
• The Bug/Defect is found in a solution for which the Customer does not have a subscription, such as a Script or Workflow.

 

5.3.  Maintenance

Maintenance is defined as (i) field mapping updates; (ii) changes to integration flow schedules and configuration settings; (iv) updates of connections; (v) resolution of errors.

 

5.4.  Enhancement Requests

An enhancement request is a request by the Customer to add functionality or enhance performance beyond the current specifications of the product. The Customer may submit an enhancement request via a support ticket. All enhancement requests are subject to review and Celigo may not provide a solution for an enhancement request.

Depending upon the nature of the enhancement request, it may be addressed in one of the following ways:

Product Enhancement: The enhancement may require a change to the core product feature set. As such, the product enhancement will be communicated to Celigo’s Product Development department for review and consideration. An enhancement request may or may not be selected as a feature to be built into the product.

Solution Enhancement: The enhancement may require a change to the configuration settings of the product or a custom solution previously implemented by Celigo. As such, the solution enhancement will be communicated to Celigo’s Customer Success department for review and consideration. The work may require a new project and/or sales engagement, or if the request is small enough, it may be implemented from the context of the case and charged on a T&M basis. These classifications will be managed by Celigo and the results of any one request will be communicated back to the Customer. All enhancement requests are subject to additional charges.

 

6. Exceptions to What is Supported

The following custom code that is not written by Celigo will not be supported:

• Non-Celigo SuiteScript hooks
• Code in end point systems used to trigger or extend the integration functionality
• Code residing in non-Celigo tech stacks (Examples: AWS Lambda functions, Express Stacks, any other code called outside of JavaScript hooks that live within integrator.io)

 

At its discretion, Celigo will provide best effort to support issues related to the following custom code not written by Celigo:

• integrator.io JavaScript hooks
• handlebars expressions

 

This may require the Customer to provide additional documentation. Should Celigo choose to support custom code not written by Celigo, the ticket will be excluded from the Service Level Agreement.

 

7. Customer’s Obligations

In order for Celigo to provide effective and timely support services, the Customer must provide Celigo with the following required information:

• Active, working credentials to the Celigo product and, where applicable, the third party applications being integrated – via Celigo’s secure credential management system, LastPass
• Steps to reproduce the problem, expected results and actual results
• Links to records that contain error messages and/or are in an invalid state
• Screenshots and/or video representations of the problem are optional and extremely helpful

 

8. Service Level Agreement

This Services Level Agreement (SLA) is applicable for Preferred and Premier Customer Success plans only. The Essential Customer Success Plan is expressly excluded from this SLA. In order to be eligible for this SLA Warranty, the Customer must have opened the support ticket(s) via a defined support channel.

8.1.  Service Level Agreement Warranty

Celigo warrants that the target response times will be met for Urgent, High, and Normal priority tickets submitted by the Customer to Celigo during the applicable support hours and via the applicable support channels the Customer is entitled to via their Customer Success Plan Level. The Service Level is calculated exclusive of (A) any unavailability that is attributed to (i) Customer’s inability to connect to the Internet; (ii) the actions or failures to act of Customer, or Customer’s third party agents, contractors, suppliers or vendors; or (iii) any factor(s) outside of Celigo’s reasonable control; (B) low priority tickets. No SLA credits will accrue for any violations that are attributable to any of the foregoing causes.

8.2.  Calculation of SLA Credits

In the event that Customer experiences warranty violations as described in the table below in any calendar quarter, then upon Customer’s written request and per the SLA Credit Process described below, Celigo will provide Customer with a credit against Customer’s normal Customer Success plan fees (“Service Credit”). Each Service Credit will be calculated as follows:

• • • Celigo will calculate the % of SLA Violations in the calendar quarter.
      • SLA Violations are defined as a first response or follow up response longer than the target response times listed in Section 4: Target Response Times.
      • The % of SLA Violations is calculated against the total of all SLA events for all tickets opened by the Customer during the calendar quarter.
    • Based on the % of SLA Violations, Celigo will calculate the % Credit for the calendar quarter.
      • The % Credit is calculated against the quarterly Customer Success plan subscription fee.

8.3.  SLA Credit Process

If Customer becomes eligible for a Service Credit, Customer must submit a request in writing to Celigo within five (5) business days following the end of the calendar quarter in which Customer alleges the Service Credit accrued. Customer’s written notice must state, with specificity, the date(s), time(s), and duration(s) of each violation claimed by Customer. If Celigo inspects Customer’s written request for a Service Credit, and agrees with the violation calculation, Celigo will notify Customer that a Service Credit will be applied to Customer’s fees for Services for the next billing cycle. Service Credits cannot be applied retroactively. Customers must be current on all payments to Celigo in order to be eligible for Service Credits. Any Customer that does not timely submit a written request for a Service Credit will forfeit all rights to receive a Service Credit for the quarter in question.

Each Customer shall be eligible for only one (1) Service Credit request in any given calendar quarter. In no event shall the Service Credit available to any Customer for any calendar quarter exceed the quarterly Customer Success Plan subscription fees paid and payable by Customer to Celigo during the quarter. This SLA states Celigo’s sole obligation, and Customer’s sole and exclusive warranty.

 

CloudExtend Support Policies

CloudExtend is a brand of Celigo. Refer to the CloudExtend Support Policies page.