> For the complete documentation index, see [llms.txt](https://connect-docs-uk.locoia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://connect-docs-uk.locoia.com/faq/partner-faqs.md).

# Partner FAQs

<details>

<summary>As a partner, how can I propose a customer for Aareon Connect (AC) and what is the process?</summary>

1. Partner explains to the client that AC is Aareon's integration product. For more information, please feel free to contact Aareon or the account manager responsible for you.
2. Aareon then contacts the customer about AC.
3. The customer decides in favour of AC. Aareon and the Locoia team activate AC for the customer's ERP and approach the customer.
4. The customer then needs the partner's API key (or login details to the API) and may need to request this from the partner's account management or find it in the partner user interface.
5. AC-Team puts the integration live with the client in a partner test account.
6. The customer is asked to check the data in the test account using a standardised list of questions for each use case.
7. After confirmation that all data is as expected, the integration goes live in the partner production account.

</details>


---

# 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://connect-docs-uk.locoia.com/faq/partner-faqs.md?ask=<question>&goal=<endgoal>
```

`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.