MCTMarketing Cloud Translator
Support & SLA

Who you call, and how fast we answer.

Target response times, not resolution guarantees dressed up as ones. Enterprise agreements can tighten every number on this page.

Channels

How to reach us, by edition.

Starter
Channel
Email
Hours
Mon to Fri, 09:00 to 18:00 CET
Also included
Documentation, install guide, FAQ
Growth
Channel
Email + shared Slack Connect channel
Hours
Mon to Fri, 08:00 to 20:00 CET
Also included
Priority queue, quarterly check-in call
Enterprise
Channel
Email, Slack Connect, scheduled calls
Hours
Agreed in your order form, extended coverage available
Also included
Named contact, onboarding and rollout support

One address for everything: support@genetrix.tech. Security issues go to security@genetrix.tech instead.

Severity & response

What counts as urgent.

Target first response, measured from when your ticket arrives during covered hours.

P1
Compile blocked in production
No one can translate or compile, and a live campaign is at risk.
1 business day
4 business hours
Per contract, typically 2 hours
P2
Major function broken
One language, one template pattern, or write-back fails, workaround exists.
2 business days
1 business day
4 business hours
P3
Minor issue or question
Cosmetic issue, configuration question, or a how-to.
3 business days
2 business days
1 business day
P4
Feature request
Something MCT does not do yet.
Logged, reviewed monthly
Logged, reviewed monthly
Roadmap discussion
Availability

What an outage actually affects.

The honest scope matters more than a number on a slide.

Your sends never depend on MCT

Compiled content lives in your Content Builder and Marketing Cloud renders it at send time. If the MCT backend is down, scheduled campaigns still go out normally.

An outage affects new compiles

The impact of downtime is that a marketer cannot translate or recompile until service resumes. That is a workflow delay, not a send failure.

You own the uptime of your host

Because the backend runs in your Azure subscription, CloudPages tenant or PHP host, availability is a shared responsibility. We publish target availability for our hosted option in the order form.

Releases

Maintenance, versioning and deprecation.

Versioning

Semantic versioning on the package and the backend. Patch releases are backwards compatible, minor releases add capability, major releases are announced with an upgrade note.

Maintenance windows

Backend updates are deployed by you, on your schedule. We do not push changes into your environment.

Deprecation

Anything we remove gets at least 90 days notice by email, with a migration path documented before the clock starts.

Marketing Cloud changes

When Salesforce changes the Content Builder or REST API surface, we ship a compatible release and email licensed customers with the required action.

Escalation

If a ticket stalls.

  1. 1. Reply on the ticket with "escalate" and the business impact. That moves it up a severity band for review.
  2. 2. If there is no movement within one covered business day, email escalations@genetrix.tech.
  3. 3. Enterprise customers can call their named contact directly using the number in the order form.

Response targets on this page apply to licensed customers and are superseded by the terms in a signed order form.

Support you can name in a procurement doc.

Ask us for the SLA in writing and we will send it before you sign anything.

Seehow MCT integrates with your Marketing Cloud environment.

Get a demo
MCTMarketing Cloud Translator
SFBuilt for Salesforce Marketing Cloud
IDOAuth 2.0, no subscriber data sent
24Install and first send in under a day