> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/support/support-processes/transition-from-implementation-to-limio-support.md).

# Transition from Implementation to Limio Support

Now that the implementation phase is complete, you can make use of Limio Support for help troubleshooting issues and answering questions.

Please see the articles and links below to familiarise yourself with Limio Support and get set up.

[How Limio Support Works](/support/support-processes/how-limio-support-works.md)

This is an overall guide on how to use Limio Support and includes details of the types of query that fall under support and those that fall outside of support.

**Handover of custom components**

For customers that require advanced customisation, Limio can provide a Limio Components Repository. This repository provides a library of open-source Limio Shop Components and a Component Playground to edit these components and build new Custom Components with a set of tools to access Limio Subscription and User data. To gain access to the features outlined in this document please contact [Limio Support](https://limio.zendesk.com/hc/en-gb).

This is a guide for developers who will be creating custom components.

[https://docs.limio.com/developers/custom-components/custom-components](https://docs.limio.com/developers/custom-components/custom-components "mention")


---

# 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.limio.com/support/support-processes/transition-from-implementation-to-limio-support.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.