> For the complete documentation index, see [llms.txt](https://partner-docs.covergenius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://partner-docs.covergenius.com/offers/services/xcover/claim.md). # Claims How are users able to view and understand policy details, and initiate claims? ## Claims Handling Due to their regulated nature, claims are solely handled by Cover Genius.\ Cover Genius is responsible for all communications with users, claims assessment and claims payments.\ Users can lodge the claim on [XCover.com/claims](https://xcover.com/en/account/claims/) by completing an online, pre-filled form, provide a description of the situation/event and provide any supporting information or documents required.\ Generally, in situations where customers contact your platform in regards to claims, they should be redirected to [XCover.com](https://xcover.com). ## First Notice of Loss (FNOL) Users will need to submit a first notice of loss form (FNOL) in order for claims to be assessed.\ Generally, this is completed by a logged in user at [XCover.com/claims](https://www.xcover.com/en/account/claims/). ## Claim Assessment Claims will be assessed by Cover Genius via our in-house claims assessment system.\ We leverage our technology and existing policy data to provide efficient and automated approval process, and fast electronic claims payment. ## Medical and Emergency Claims Medical assistance and medical-related claims may be handled by our underwriting partners directly.\ Cover Genius works with our underwriters to create a user-centric workflow to ensure a smooth process relevant to your use case. ## Can we integrate claims submission ourselves? Generally, claims are solely managed by Cover Genius.\ If you wish to discuss integrating claims submission into your experience, please contact your partnership manager. --- # 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://partner-docs.covergenius.com/offers/services/xcover/claim.md?ask=&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.