> For the complete documentation index, see [llms.txt](https://docs.medcrypt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.medcrypt.com/ko/helm/get-started-with-helm/dont-have-an-sbom/get-expert-services-help.md).

# 전문 서비스 지원 받기

전 FDA 심사관과 분석가로 구성된 당사의 전문 Services 팀은 제품 개발 수명 주기에 사이버 보안과 지속적 개선을 반영하는 일부터 PKI 암호화, FDA 서신 작성 및 그 사이의 다양한 업무까지 전문가 평가와 지침, 설계 지원을 제공할 수 있습니다. [문의해 주세요](mailto:support@medcrypt.com) 어떻게 도와드릴 수 있는지 확인해 보세요!


---

# 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.medcrypt.com/ko/helm/get-started-with-helm/dont-have-an-sbom/get-expert-services-help.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.