> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/transaction30api/contacts.md).

# Contacts

#### **Technical Assistance** <a href="#mtscontacts-technicalassistance" id="mtscontacts-technicalassistance"></a>

The MTS CI team is supporting the client throughout the entire MTS integration period and for the first 48 hours directly after the launch. The MTS CI team is available during the integration period via a dedicated Skype/Slack chat room or by email at: <client-integration-team@sportradar.com>.

#### **Support for Production Issues** <a href="#mtscontacts-supportforproductionissues" id="mtscontacts-supportforproductionissues"></a>

After launch support period of 48 hours has passed, support is then handed over to our standard 24/7 Sportradar Support Team (by email at: <support@sportradar.com> or live chat on Ctrl Portal) who will ensure support availability and issue management.

For all enquiries relating to the usage of the Sportradar feeds and other Services, it is recommended to contact Sportradar Support directly.

#### **UOF Sportsbook Testing** <a href="#mtscontacts-uofsportsbooktesting" id="mtscontacts-uofsportsbooktesting"></a>

The UOF Sportsbook Testing process will start immediately after the UOF integration. The relevant Sportradar team will automatically contact you.

#### **Operational** <a href="#mtscontacts-operational" id="mtscontacts-operational"></a>

In the case of any operational issues, please contact the MTS Operational Account Manager (OAM): [mts-client-management@sportradar.com](mailto:MTS-Client-Management@sportradar.com).

#### **MTS Sales** <a href="#mtscontacts-mtssales" id="mtscontacts-mtssales"></a>

In case of contractual or commercial topics please email your assigned sales representative.

#### **MTS Service Delivery** <a href="#mtscontacts-mtsservicedelivery" id="mtscontacts-mtsservicedelivery"></a>

The Service Delivery team should be contacted if there is a need for additional technical activity on MTS, such as: adding new bet types, features, producers, etc. The team can be reached by email at: <mts-servicedelivery@sportradar.com>.


---

# 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://docs.sportradar.com/transaction30api/contacts.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.
