SLA - Service Level Agreement - Email Marketing - SMTP services - Mailjet

Service Level Agreement (SLA)

January 2019 – (V2.1)


1.1 Object

The object of the Mailjet Service Level Agreement (SLA) is to define the scope and level of quality of the emailing Service as well as the maintenance and support commitments that are applicable.

1.2 Definitions

Client Administrator”: Administrator within the Client’s organization whose responsibility it will be to receive requests for information and assistance from the Client and to try to respond to them and be authorized to open and respond to Tickets.

Handling time”: time elapsing between the positive response of the Service Provider’s SMTP server or Send API and the time when the message is processed and ready to be added to the delivery queue, before the first attempt.

Service Level Agreement” or “SLA”: the present document that defines the scope and level of the quality of the emailing Service as well as the maintenance and support commitments that are applicable for all self-service clients (with the exception of those clients on a Free Plan).

System uptime“: the total amount of time over a calendar month during which Clients are able to access the IT systems necessary for operation of the platform.

SLA Premium Enterprise Clients”: Custom enterprise clients having subscribed to SLA Premium features with corresponding costs. SLA Premium is available to any custom entreprise client, upon request.

Support”: as defined in Article 2.

Fault”: any repetitive and reproducible problem with the functioning of the Service, always excluding cases in which interruption or degradation to the Service is caused by a deliberate decision by the Service Provider made following behavior of the Client deemed to be abnormal or incorrect. All Faults may be classified into three distinct categories, depending on their criticality:

  • Critical Fault”: any Fault causing (i) inaccessibility of the Client admin, or of the API, or of the SMTP-IN, or (ii) inability of the Client to send emails (absence of email handling).
  • Medium Fault”: any minor fault in the functioning, enabling of access and use of the Service, with all its applications and/or features, even if they (access and use of the Service) have to be carried out via a bypass procedure and/or with a degraded sending rate (extreme slowness, random errors) and/or causing partial interruption to the email sending function or blockage of a significant percentage of emails (over 10% of emails are systematically delayed, defined as over 12 consecutive hours for emailing campaigns and over 30 minutes for transactional emails).
  • Low Fault”: any Fault not being that does not belong in the above Critical or Semi-critical categories (for example, lack of sending of automatic start of the week reports, unavailability or temporary lack of content updates of a ‘read only’ nature, such as statistics).

Service”: means the Mailjet solution that is hosted on the servers and/or cloud that Service Provider designates and that Client may execute remotely; Service offers various features, including, but not limited to, management of emailing campaigns with real-time monitoring of sent email deliverability, newsletter creation and sending, sending and managing transactional emails.

Ticket”: the folder, indexed by a unique identification number, created by the Helpdesk management tool when the Client indicates the existence of a Fault to Support, and in which each intervention by Support is recorded until the Fault is fixed and/or the folder is closed.

2. Client Support

The Service Provider offers client Support for the Service, by (i) responding to requests for information and assistance from the Client Administrator in relation to the use of the Service, it being understood that the Client Administrator alone may contact Support, and (ii) fixing Faults in relation to use of the Service that could not be solved by the Client Administrator, in spite of their best efforts.

The Service Provider reserves the right to invoice the Client for any request for intervention by Support relating to basic level support (such as a fault linked to bad configuration by the Client or the Client’s technical environment, for example) that the Client Administrator did not seek to resolve on his own before contacting Support.

2.1 Access to Support

The Client Administrator may access Support by creating a Ticket, accessible from the Mailjet platform as follows:

Tickets are then available and managed in our internal ticketing tool.

Before opening any Ticket or contacting Customer Success, an initial stage of diagnostics and analysis is to be carried out by the Client Administrator, particularly including:

  • Obtaining all useful information from users concerned about the incident encountered and its reproducibility,
  • Searching the FAQ database to check that the solution is not already available,
  • An attempt to reproduce the incident,
  • Checking the local network (firewall, proxy, etc.), – which the Service Provider has no means of control.

2.2 Opening Hours

Opening Hours
Support Level 1
English language : 24/7
French language : 8am to 5:30pm (GMT +1)

2.3 How Support Works

Each time that a Ticket is opened, a folder is immediately created with a specific ticket number and information provided by the Client Administrator about the incident. As such, the Client Administrator is to communicate all information in their possession, such as system messages, copies of error messages, and documentation linked to the Fault in question.

Support’s objective is to restore a normal service operation as quickly as possible and to minimize the impact on business operations, thus ensuring that the best possible levels of service quality and availability are maintained.

Classification of Faults into one or other of the three categories above (Critical, Medium and Low Faults) will be definitive after qualification by Support.

If a solution to a Critical or Medium Fault is implemented by Support, the Fault will be downgraded to a Fault of the next critical category and the time limit for fixing the Fault will be that associated with the new classification.

A ticket will be closed and the Client is informed when: (a) the Fault is resolved; (b) no response is received from the Client Administrator to a request from Support for additional information required in order to fix the Fault; or, (c) written confirmation from Client regarding closure of an unresolved ticket.

Notice will be sent to the Client Administrator via the Ticket, or by contact through the Customer Success Team, if applicable.

2.4 Support Teams

Mailjet Support level 1: first level of support when creating a Ticket via the website.

The Support level 1 team is based in 3 countries, in 3 different time zones.

Support level 2: Enhanced technical skills and technical rights on Mailjet platform.

The Support level 2 team is not directly contactable by customers, but instead only by Mailjet Support level 1 and Customer Success teams. The scope of the requests managed by Support level 2 may be as wide as requests reported to Mailjet Support level 1 and to Customer Success team (i.e. technical questions, technical incidents, etc.).

Compliance and Deliverability team: in charge of ensuring that Mailjet is compliant and aligned with leading deliverability industry-wide standards and that Clients are aligned with Mailjet’s Sending Policy.

The team is not directly contactable by Clients but instead only by Mailjet Support level 1 and are involved in the Support process when there is an issue or a question regarding email deliverability (authentication issues, ISP blocks, emails in junk/spam folder) or regarding compliance with Mailjet rules (akid in quarantine…).

Technical Teams: Operational (Ops) and Development teams

Technical teams are exclusively contacted by Mailjet Support level 2 teams and Compliance & Deliverability team.

The Ops team is in charge of the Mailjet hosting platform and are involved in the Support process when there is an issue with Mailjet hosting platform (server issue, database issue, network issue…).

Development teams are in charge of the development of the Mailjet applications and services running on Mailjet hosting platform and are involved in the Support process when there is an issue with Mailjet applications.

2.5 Support Process

The following describes how a Client can contact Mailjet, and how the Mailjet teams interact to treat Client requests.

3. Service Performance

3.1 Service Availability

The Service Provider will make every effort to enable access and use of the Service under the best possible technical conditions. However, the correct functioning of the internet in its entirety cannot be guaranteed and that losses of connection may be due to failures by technical intermediaries (i.e. all third party service providers beyond the control of the Service Provider, but whose service contributes, directly or indirectly, to delivery of the Service).

In the event of an unexpected interruption to the Service, the Service Provider will take every possible measure to discover the cause and restore the Service in the shortest possible time.

All unexpected interruptions of service will be notified via our status page <>.

The Service availability rate is calculated as follows, and excludes planned maintenance periods, external network or technical intermediaries failures, or the case of force majeure:

Application Availability [%] = (Application Uptime) / (System Uptime) × 100

3.2 Planned maintenance periods

Technical maintenance is defined as maintenance relating to the technical environment (hardware, operating systems, and networks) hosting the Service.

The Service Provider agrees to take all possible measures in order to limit any inconvenience to the Client. In general, during maintenance periods, access and use of the Service may be temporarily suspended or degraded, but reception of emails via SMTP-IN will still be possible.


The Service Provider agrees to make every commercially reasonable effort to ensure that processing of Client’s data from their reception by the Service Provider to sending of emails by the Service (leaving the platform) should be carried out in the shortest possible time.

The response time following the opening of a ticket corresponds to the time elapsed between opening of the ticket on the Helpdesk and its handling by Support Level 1.

With regard solely to transactional emails, the Service provider will make every effort to respect the time limits set out in the table below.

Indicator Measurement period Target values Tolerance or reliability index
Maximum handling time for transactional emails Monthly 1 minute 98%
Availability of the platform Monthly App access 98%
API 98%
SMTP-IN (providing that the SMTP protocol and the MX norm are followed) 98%
Response time Critical Fault Monthly 4 hours 98%
Response time Medium Fault Monthly 6 hours 98%
Response time Low Fault Monthly 10 hours 98%

This time limit is only guaranteed under the following cumulative conditions:

  • Account without any ‘rate limit’ (with no restriction on use),
  • Excluding Client error (i.e. incorrect delivery address, incorrect configuration, incorrect source file),
  • Excluding Client deliverability negligence (i.e. non respect of Sending Policy terms by End user or Client),
  • Excluding thirty (30) day introductory period from the first sending of emails,
  • Excluding significant alteration in the volume of email sent, the sending rate, and the quality of the Client’s own statistics,
  • Excluding attribution by the Client of a low priority,
  • Excluding planned maintenance periods.