Support Policy and Service Level Agreement

This Support Policy and Service Level Agreement (”Policy“) is subject to the agreement between you (“Customer“) and Pricefx (“Provider“) under which Provider provides its subscription services (the ”Subscription Services“) that reference this Policy (the  “Subscription Agreement“). Capitalized terms not defined in this Policy shall have the meaning given to them in the Subscription Agreement. This Policy describes Provider’s support offering provided by Provider’s technical support team (“Provider Support“) in connection with support requests related to bugs, defects, or errors in the Subscription Services causing them to fail to perform in material conformance with the Documentation (“Errors“).

I. GENERAL SUPPORT / TICKETING

  1. General Support Offering. Customer shall designate one (1) primary contact who has Provider administrator privileges and up to ten (10) additional user contacts (collectively, the ”Customer Contacts“). All Customer Contacts must be reasonably trained in the use and functionality of the Subscription Services and the Documentation and shall use reasonable diligence to ensure a perceived Error is not an issue with Customer Systems or internet connectivity. Provider shall provide English-speaking remote assistance to Customer Contacts for questions or issues arising from any Errors, as further described in this Policy, including troubleshooting, diagnosis, and recommendations for potential workarounds for the duration of Customer’s subscription to the applicable Service. Additionally, if Customer desires technical or professional services from Provider, including but not limited to services related to data modeling, code development, migration, or product training, then Customer and Provider must enter into a mutually executed for-fee Statement of Work for such services.
  2. Contacting Provider Support. Customer Contacts may contact Provider Support by:
    • Submitting a support request to the Provider Help Desk application (the ”Provider Hub”) and designating the appropriate severity level according to Table 1 below (the ”Severity Level(s)”; or
    • If Customer Contacts cannot access the Provider Hub, by submitting the support request to Support@pricefx.com (each of 2.a. and/or 2.b being, a ”Support Case”); or
    • Only in the case of a Severity Level 1 (defined below) issue, Customer Contacts may call the Help Desk at either +49-1805-7393696 (Germany based fixed line) or +1-855-739-3696 (USA).
  3. Submission of Support Cases. Each Support Case shall:
    1. Designate the Severity Level of the Error in accordance with the definitions in Table 1 (below);
    2. Identify the Customer’s user account that experienced the error;
    3. Include information sufficiently detailed to allow Provider Support to attempt to duplicate the Error (including any relevant error messages); and
    4. Provide contact information for the Customer Contact most familiar with the issue.
      Unless Customer expressly designates the Severity Level, the Support Case will default to the lowest Severity Level. If Customer Contacts submit Support Cases related to enhancement or feature requests, Provider shall treat those tickets as closed once the request has been forwarded internally. Provider may also offer various support and training resources such as documentation, community forums, FAQs and user guides available from time-to-time. Additionally, Provider offers for-fee consultation and training services via Statements of Work.
  4. Error Response. Upon receipt of a Support Case, Provider Support will attempt to determine the Error and assign the applicable Severity Level based on descriptions in Table 1 (below). Provider shall use commercially reasonable efforts to meet the Initial Response Time Target for the applicable Severity Level, as measured during in-region Provider Support hours set forth in Table 1 (such hour(s), ”Business Hour(s)” with the total Business Hours in an in-region support day being ”Business Day(s)”). If the Customer Contact that submitted the Support Case is unresponsive or unreachable, Provider may downgrade the Severity Level by one level. If Provider’s Severity Level designation is different from that assigned by Customer, Provider will promptly notify Customer in advance of such designation. If Customer notifies Provider of a reasonable basis for disagreeing with Provider’s designated Severity Level, the parties will discuss in an effort to come to mutual agreement. If disagreement remains after discussion, each party will escalate within its organization and use good faith efforts to mutually agree on the appropriate Severity Level.

Table 1: Error Severity Level Definitions / Response Times

Error Severity LevelDescriptionStandard Support – Initial Response Time Target
Severity Level 1 (Critical Severity)An Error that (a) renders the Subscription Services completely inoperative or (b) makes Customer’s use of material features of the Subscription Services impossible, with no alternative available.Two (2) Hours
Severity Level 2 (High Severity)An Error that (a) has a high impact to key portions of the Subscription Services or (b) seriously impairs Customer’s use of material function(s) of the Subscription Services and Customer cannot reasonably circumvent or avoid the Error on a temporary basis without significant time or effort.Four (4) Hours
Severity Level 3 (Normal Severity)An Error that has a medium-to-low impact on the Subscription Services, but Customer can still access and use some functionality of the Subscription Services.Twenty-four (24) Hours
Severity Level 4 (Low Severity)An Error that has low-to-no impact on Customer’s access to and use of the Subscription Services.Seventy-two (72) Hours

Table 2: Global Provider Support Hours

Provider Service RegionStandard Support Hours for Severity Level 1Standard Support Hours for Severity Levels 2-4
Americas24 x 7 x 365Monday – Friday, 8 am – 6 pm CST, excluding recognized US Federal holidays
EMEA24 x 7 x 365Monday – Friday, 8 am – 6 pm CEST, excluding recognized EU holidays
APAC24 x 7 x 365Monday – Friday, 8 am – 6 pm AEST, excluding recognized Australia holidays

II. SERVICE LEVEL AGREEMENT

  1. Uptime Generally.  “Monthly Uptime” is the percentage of time in a calendar month during which the Subscription Services were actually available as measured by Provider’s monitoring system, calculated as follows:Monthly Uptime % = [(Total Time – Unavailable Time) / Total Time] x 100Total Time” is the total number of minutes in an applicable calendar month.“Unavailable Time” is the total number of minutes within a given calendar month during which the Subscription Services fail to respond to Provider’s monitoring systems; provided, however minutes during which the Subscription Services fail to respond to Provider’s monitoring systems will not count as Unavailable Time if arising or resulting from: (a) use of the Subscription Services by Customer other than as authorized under the Subscription Agreement or Documentation; (b) failure of or by Customer Systems; (c) Force Majeure Events; (d) Cloud Maintenance by Provider of up to twelve (12) hours per month; (e) general Internet problems or other factors outside of Provider’s reasonable control; and/or (f) beta, pre-release version or functionality provided to Customer or which Customer is not paying any Fees. ”Cloud Maintenance” means (i) routine cloud or software maintenance that is scheduled at least 72 hours in advance, or (ii) emergency maintenance that is necessary to address a critical issue or failure of an essential infrastructure by which Provider will provide notice to extent reasonably practical.
  2. Uptime Target. Target availability for the Subscription Services is ninety-nine and nine tenths percent (99.9%) during supported hours per month (the ”Monthly Uptime Target“).
  3. Service Credit Calculation. If in any calendar month during the Term of the applicable Subscription Services the actual Monthly Uptime is less than the Monthly Uptime Target, Provider will issue Customer a Service Credit against any subsequently accrued Fees for the Subscription Services at issue, calculated as follows (each, a ”Service Credit“):Service Credit = Monthly Subscription Services Fees x [1 – (Monthly Uptime / Monthly Uptime Target)]For clarity, if any Fees are not calculated on a monthly basis (i.e. quarterly or annually), ”Monthly Subscription Services Fees” will be calculated by dividing the total applicable annual or quarterly Fees by the number of months within such billing period.
  4. Service Credit Requirements. The aggregate monthly Service Credits in a given month during the Term of the applicable Subscription Services will not exceed 5.0% of the monthly Fees payable by Customer for the Subscription Services at issue. Service Credit claims must be made within the calendar month immediately following that in which the Monthly Uptime Target is not met. Service Credits are Customer’s sole and exclusive remedy for any failure by Provider to meet its obligations under this Policy. Service Credits will not accrue during any period in which Customer is in undisputed breach of its payment obligations under the Subscription Agreement.

This Support Policy and Service Level Agreement (this “Policy”) is subject to the agreement between
you (“Customer”) and Pricefx (“Provider”) under which Provider provides its
subscription services (the “Subscription Services”) that reference this Policy (the
Subscription Agreement”). Capitalized terms not defined in this Policy shall have the meaning given
to them in the Subscription Agreement.  This Policy describes Provider’s support offering provided by Provider’s
technical support team (“Provider Support”) in connection with support requests related to bugs,
defects, or errors in the Subscription Services causing them to fail to perform in material conformance with the
Documentation (“Errors”).

    1. GENERAL SUPPORT / TICKETING
      1. General Support Offering. Customer shall designate one (1) primary contact who has Provider administrator privileges and up to ten (10) additional user contacts (collectively, the “Customer Contacts”). All Customer Contacts must be reasonably trained in the use and functionality of the Subscription Services and the Documentation and shall use reasonable diligence to ensure a perceived Error is not an issue with Customer equipment, software, or internet connectivity. Provider shall provide English-speaking remote assistance to Customer Contacts for questions or issues arising from any Errors, as further described in this Policy, including troubleshooting, diagnosis, and recommendations for potential workarounds for the duration of Customer’s subscription to the applicable Service. Additionally, if Customer desires technical or professional services from Provider, including but not limited to services related to data modeling, code development, migration, or product training, then Customer and Provider must enter into a mutually executed for-fee Statement of Work for such services.
      2. Contacting Provider Support. Customer Contacts may contact Provider Support by:
        1. Submitting a support request to the Provider Help Desk application (the “Provider Hub”) and designating the appropriate Severity Level according to Table 1 below; or
        2. If Customer Contacts cannot access the Provider Hub, by submitting the support request to Support@pricefx.com (each of 2.a. and/or 2.b being, a “Support Case”); or
        3. Only in the case of a Severity Level 1 (defined below) issue, Customer Contacts may call the Help Desk at either +49-1805-7393696 (Germany based fixed line) or +1-855-739-3696 (USA).
      3. Submission of Support Cases. Each Support Case shall:
        1. Designate the Severity Level of the Error in accordance with the definitions in Table 1 (below);
        2. Identify the Customer’s user account that experienced the error;
        3. Include information sufficiently detailed to allow Provider Support to attempt to duplicate the Error (including any relevant error messages); and
        4. Provide contact information for the Customer Contact most familiar with the issue.


        Unless Customer expressly designates the Severity Level, the Support Case will default to Severity Level 4.  If Customer Contacts submit Support Cases related to enhancement or feature requests, Provider shall treat those tickets as closed once the request has been forwarded internally.  Provider may also offer various support and training resources such as documentation, community forums, FAQs and user guides available from time-to-time. Additionally, Provider offers for-fee consultation and training services via Statements of Work.

      4. Error Response. Upon receipt of a Support Case, Provider Support will attempt to determine the Error and assign the applicable Severity Level based on descriptions in Table 1 (below). Provider shall use commercially reasonable efforts to meet the Initial Response Time Target for the applicable Severity Level, as measured during in-region Provider Support hours set forth in Table 1 (such hour(s), “Business Hour(s)” with the total Business Hours in an in-region support day being “Business Day(s)”). If the Customer Contact that submitted the Support Case is unresponsive or unreachable, Provider may downgrade the Severity Level by one level. If Provider’s Severity Level designation is different from that assigned by Customer, Provider will promptly notify Customer in advance of such designation. If Customer notifies Provider of a reasonable basis for disagreeing with Provider's designated Severity Level, the parties will discuss in an effort to come to mutual agreement. If disagreement remains after discussion, each party will escalate within its organization and use good faith efforts to mutually agree on the appropriate Severity Level.

Table 1: Error Severity Level Definitions / Response Times

Error Severity LevelDescriptionStandard Support - Initial Response Time Target
Severity Level 1 (Critical Severity)An Error that (a) renders the Subscription Services completely inoperative or (b) makes Customer’s use of material features of the Subscription Services impossible, with no alternative available.Two (2) Hours
Severity Level 2 (High Severity)An Error that (a) has a high impact to key portions of the Subscription Services or (b) seriously impairs Customer’s use of material function(s) of the Subscription Services and Customer cannot reasonably circumvent or avoid the Error on a temporary basis without significant time or effort.Four (4) Hours
Severity Level 3 (Medium Severity)An Error that has a medium-to-low impact on the Subscription Services, but Customer can still access and use some functionality of the Subscription Services.Twenty-four (24) Hours
Severity Level 4 (Low Severity)An Error that has low-to-no impact on Customer’s access to and use of the Subscription Services.Seventy-two (72) Hours

Table 2: Global Provider Support Hours

Provider Service RegionStandard Support Business Hours for Level 1 (Critical Severity) Standard Support Business Hours for Levels 2-4
Americas24 x 7 x 365Monday – Friday, 8 am - 6 pm local hours, excluding recognized US Federal holidays
EMEA24 x 7 x 365Monday – Friday, 8 am - 6 pm local hours, excluding recognized EU holidays
APAC24 x 7 x 365Monday – Friday, 8 am - 6 pm local hours, excluding recognized Australia holidays
    1. SERVICE LEVEL AGREEMENT
        1. Uptime Generally. “Monthly Uptime” is the percentage of time in a calendar month during which the Subscription Services were actually available as measured by Provider’s monitoring system, calculated as follows:


          Monthly Uptime % = [(Total Time – Unavailable Time) / Total Time] x 100


          Total Time” is the total number of minutes in an applicable calendar month.


          Unavailable Time” is the total number of minutes within a given calendar month during which the Subscription Services fail to respond to Provider’s monitoring systems; provided, however minutes during which the Subscription Services fail to respond to Provider’s monitoring systems will not count as Unavailable Time if arising or resulting from: (a) use of the Subscription Services by Customer other than as authorized under the Subscription Agreement or Documentation; (b) failure of or by Customer Systems; (c) Force Majeure events; (d) Cloud Maintenance by Provider of up to twelve (12) hours per month; (e) general Internet problems or other factors outside of Provider’s reasonable control; and/or (f) beta, pre-release version or functionality provided to Customer or which Customer is not paying any Fees. “Cloud Maintenance” means (1) routine cloud or software maintenance that is scheduled at least 72 hours in advance, or (2) emergency maintenance that is necessary to address a critical issue or failure of an essential infrastructure by which Provider will provide notice to extent reasonably practical.

      1. Uptime Target. Target availability for the Subscription Services is ninety-nine and nine tenths percent (99.9%) during standard business hours per month (the “Monthly Uptime Target”).
      2. Service Credit Calculation. If in any calendar month during the Term of the applicable Subscription Services the actual Monthly Uptime is less than the Monthly Uptime Target, Provider will issue Customer a Service Credit against any subsequently accrued Fees for the Subscription Services at issue, calculated as follows (each, a “Service Credit”):

        Service Credit = Monthly Subscription Services Fees x [1 – (Monthly Uptime / Monthly Uptime Target)]


        For clarity, if any Fees are not calculated on a monthly basis (i.e. quarterly or annually), “Monthly Subscription Fees” will be calculated by dividing the total applicable annual or quarterly Fees by the number of months within such billing period.

      3. Service Credit Requirements. The aggregate monthly Service Credits in a given month during the Term of the applicable Subscription Services will not exceed 5% of the monthly Fees payable by Customer for the Subscription Services at issue. Service Credit claims must be made within the calendar month immediately following that in which the Monthly Uptime Target is not met.  Service Credits are Customer’s sole and exclusive remedy for any failure by Provider to meet its obligations under this Policy.  Service Credits will not accrue during any period in which Customer is in undisputed breach of its payment obligations under the Subscription Agreement.

Connect with someone at PriceFX today

We love talking about two things - your business, and how our software can help it grow! Give us a bit of info below, and we'll get right back to you.

Watch a Demo

See It In Action

Talk to an Expert

Let's Chat!