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

# Dialog Insight

## **Supported Destination Services**

DinMo supports the following destination service:

* [Synchronise contacts](/integrations/destination-platforms/dialog-insight/synchronise-contacts.md)

Please refer to the dedicated documentation page for more information.

## **Authentication to Dialog Insight**

Regardless of the selected destination service, DinMo will always connect to Dialog Insight via an SFTP repository.

You will need this Dialog Insight information to log in:

* Authentication Key Identifier
* Authentication Key

{% hint style="info" %}
If you haven’t configured Web Services Access yet, you can consult the [official documentation](https://support.dialoginsight.com/en/support/solutions/articles/1000256347-configuring-web-services-access?utm_source=chatgpt.com) to learn more about Authentication Key Identifier and Key.
{% endhint %}

You will also need some information directly related to your SFTP repository

* SFTP user
* SFTP password
* SFTP host
* SFTP port *(usually 22, which is filled by default)*

Please make sure the user who connects Dialog Insight on DinMo has **the right permissions to create new imports** directly in the destination.


---

# 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.dinmo.io/integrations/destination-platforms/dialog-insight.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.