> 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/uof/introduction/integration-process/kickoff-call.md).
# Kickoff Call
The whole process is well planned and organized to facilitate seamless integration of Unified Odds Feed. Every thing in this documentation is a standard process that we follow but can be customized to suit your environment and time constraints.
#### Non-Technical Kickoff Call
The process starts with an introduction call with the client or the client team. In this call, our Account Activation team will present an overview of our UOF. We make sure to accommodate your requirements and answer any questions you may have regarding the integration process and the Unified Odds Feed. We also explain how we can assist you during the process taking into account the client plans and availability for the integration.
This call is also important to avoid the test account expiration and also explains our Integration Program for fast and robust completion of the process.
During the integration of both pre-match and live odds services, you are welcome to schedule recurring follow-up calls or training sessions on the CTRL interface & technical specifics of UOF.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.sportradar.com/uof/introduction/integration-process/kickoff-call.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.