> For the complete documentation index, see [llms.txt](https://docs.owkin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.owkin.com/terms-and-support/support/support-and-sla.md). # Standard support & availability This page describes the **standard support** available to all K Pro users. Specific commitments. Availability targets, formal priority levels, and response times are defined separately under the applicable **commercial agreement** and take precedence where one is in place. ### 1. Overview & Availability K Pro is supported during standard business hours. * **Support Hours:** 9:00 AM to 6:00 PM (Paris Time) Availability targets and uptime commitments are defined as part of the applicable commercial agreement rather than as a general public commitment. ### 2. Contacting Support For any questions or issues, please submit a request through our [support form](https://owkinkhelp.zendesk.com/hc/en-us/requests/new). This is the fastest way to reach our team. Your request is routed to the right contact, and updates are shared by email. ### 3. Submitting a Request To help us investigate quickly, include: * **Contact Information:** Your email address (and a phone number if you'd like us to be able to reach you directly). * **Issue Description:** A detailed explanation of the problem. * **Reproduction Steps:** Step-by-step instructions to reproduce the error (if applicable). * **Timestamp:** The date and time the incident occurred. * **Attachments:** You can attach files directly to the request. If direct upload fails, email files to with your Service Request Number in the subject line. ### 4. Issue prioritization We review each request based on impact, scope, and whether a workaround exists. This helps us prioritize critical incidents first, especially issues affecting platform access or core workflows. Formal priority levels and service level commitments are defined separately as part of enterprise agreements. ### 5. Communication & Updates We keep you informed throughout the lifecycle of your request. For critical incidents affecting platform availability: * **Initial Alert:** We notify affected customers as soon as an outage is confirmed. * **Updates:** We share progress updates until the issue is resolved. * **Resolution:** We send a confirmation once service is restored. * **Post-incident Follow-up:** We may share a summary with key contacts for major incidents. For general support requests: * **Confirmation:** You receive a Service Request reference number by email. * **Updates:** We share progress as the request moves forward. * **Closure:** We close the request once the issue is resolved or the question is answered. ### **6. Maintenance Policy** When K Pro is hosted by Owkin, we handle all infrastructure and software updates. * **Planned Maintenance:** Scheduled to minimize impact. Enterprise customers are notified in advance in accordance with their commercial agreement. * **Unplanned Maintenance:** Reserved for urgent issues. We notify affected enterprise customers as soon as possible when it is required, and again once it is completed. --- # 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.owkin.com/terms-and-support/support/support-and-sla.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.