> For the complete documentation index, see [llms.txt](https://docs.immedio.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.immedio.io/readme.md).

# immedioへようこそ

immedioを使って、ターゲット顧客との商談自動化を始めましょう

## immedioとは

### 商談自動獲得

WEB上で自動で商談獲得。休日・夜間も商談設定可能に。顧客情報に応じて商談担当を最適に自動割り振りができます。

### WEB接客で更なる商談創出

WEB上の事例・価格ページなどにてWEB自動接客・追客で商談創出。A/Bテストで商談獲得を最大化。

### インサイドセールスの工数大幅削減

商談の自動獲得、AIによるリード情報の自動リサーチ、CRMへの1クリック商談作成で、工数を約70%削減。


---

# 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.immedio.io/readme.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.