> For the complete documentation index, see [llms.txt](https://cmp.docs.sirdata.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cmp.docs.sirdata.net/en/faq/pricing/support-response-times-by-plan.md).

# Support: response times by plan

How to reach support, first response times by plan, and the service level commitments of the paid plans.

## Reaching support

From ABconsent, menu **Support > Contact support**, or by email. Support answers **Monday to Friday, 9 a.m. to 6 p.m.**, excluding public holidays in metropolitan France.

## First response time

Sirdata provides a **first technical response**, that is, a response on the substance and not a mere acknowledgement of receipt, within these periods, in business days:

| Plan                                         | First response                                    |
| -------------------------------------------- | ------------------------------------------------- |
| Essentials                                   | 4 business days                                   |
| Starter                                      | 3 business days                                   |
| Pro                                          | 3 business days                                   |
| Business                                     | 2 business days, with a dedicated support contact |
| Association offer                            | 4 business days                                   |
| Request about Google Consent Mode, all plans | 1 business day                                    |

**Google Consent Mode.** The one-business-day period applies when you report using Google advertising or measurement services. In the support form, answer **Yes** to the question "Are you a Google customer (Ads, Analytics, Tag Manager, …)?".

**Several sites.** If your sites are on different plans, the period is that of the plan of the site concerned: name that site in your request.

## What support covers

Support covers the operation of the Service. It does not cover the editorial configuration of your sites, nor trackers deployed by third parties, for which you remain solely responsible.

## Service level commitments of the paid plans

On **Starter, Pro and Business**, Sirdata commits to the service levels of [Annex 5 of the Terms](https://www.abconsent.com/terms-and-conditions#annex-5). They are the same for these three plans:

* **Availability** of the Service and of its interface: 99% on a monthly basis. Scheduled maintenance, notified at least 7 days in advance and carried out between 11 p.m. and 6 a.m., does not count, nor do the other exclusions of Annex 5.
* **Handling of anomalies**: timeframes in working hours and working days, running from Sirdata's classification of the anomaly. They are best-efforts commitments.

| Anomaly                                                                                       | Acknowledgement | Workaround | Correction   |
| --------------------------------------------------------------------------------------------- | --------------- | ---------- | ------------ |
| Blocking: the service is interrupted for all (all requests fail, or take more than 5 seconds) | 2 hours         | 8 hours    | 5 days       |
| Major: more than 5% of requests fail, or take more than 5 seconds                             | 4 hours         | 2 days     | 15 days      |
| Minor: no significant impact                                                                  | 2 days          | —          | Next release |

* **Service credits**: if availability for the month falls below 99%, a credit of 10%, 25% or 50% of the monthly invoice, depending on the availability recorded, set off against the following invoice. To be eligible, you must in particular notify the incident within 24 hours of detecting it.

The **Essentials** plan and the **Association offer** are provided without any service level commitment: only the first response times and the support hours apply to them.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cmp.docs.sirdata.net/en/faq/pricing/support-response-times-by-plan.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
