> For the complete documentation index, see [llms.txt](https://wiki.delos.financial/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.delos.financial/additional-information/our-team.md).

# Our team

Egor (@egor\_delos) - Head of Onboarding (CET timezone), feel free to tag him personally for any questions related to KYB/KYC procedure, applications approval, required documents.
\
Mario (@mario\_delos) - Onboarding manager (CET timezone), feel free to tag him personally for any questions related to KYB/KYC procedure, applications approval, required documents.
\
Yazan (@yazasalem) – Head of Customer Success (CET timezone), he will help you with all the issues concerning accounts creation, payment details, counterparty approval, transaction statuses, etc.
\
George (@george\_delos) - Customer Success Specialist (CET timezone), he will help you with statements, as well as counterparty approval, transaction statuses.
\
Eugene (@eugene\_gx) – Technical support specialist (CET timezone), please tag him for any cases that involve providing/revoking accesses, password/2fa issues, deleting counterparties, any technical issues with the product, BaaS testing procedure and more.
\
Frederick (@Frederick\_delos) – Partnerships Manager (CET timezone), in charge of questions related to invoices, commissions or any other fees related questions.


---

# 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://wiki.delos.financial/additional-information/our-team.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.